Gadoes turns on the lights for outside tool calls

When the AI reaches out to external sources, every call now gets logged - and there's an admin page to see it all.

analyticsintegration

When a legal-AI assistant calls out to external tools or data sources, things can go wrong quietly - a source might throttle requests, return junk, or just fail with no one noticing. Gadoes' fork now records every one of those calls into a dedicated log, and surfaces the aggregated picture through an admin-only dashboard.

It's a small, contained piece of work - one new table, one backend endpoint, one admin page - but it hands whoever is running the system a way to actually watch what's happening when the AI is talking to the outside world. The dashboard rides on an existing admin flag, so anyone copying this in will want to think about who counts as an administrator before flipping it on.

So what Anyone running a legal-AI product that leans on outside data should be watching the same numbers; this is the cheap version.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

4 commits from Gadoes/dispumike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
f7cb5d92 feat(chunk19): migration 005 - mcp_events telemetry table Gadoes 2026-05-02 ↗ GitHub
aabc7e28 feat(chunk19): telemetry logging in McpClientManager.callTool Gadoes 2026-05-02 ↗ GitHub
e37d7572 feat(chunk19): GET /admin/mcp-telemetry route with unit tests Gadoes 2026-05-02 ↗ GitHub
89fbb081 feat(chunk19): /admin/mcp-telemetry dashboard page with tests Gadoes 2026-05-02 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-27.md from inside the repo you want the changes in.

⬇ Download capture-thread-27.md