Reconstructing from raw material
- Scrolling back through logs and terminal output
- Re-reading long conversation histories
- Re-walking code paths a previous session already traced
- Re-trying approaches nobody recorded as failed
Model Context Protocol
MCP is the open standard that lets AI agents use external tools. Mike Trace speaks MCP, so your agents can investigate through it without custom plugins or glue code.
Context
Raw logs and conversation history tell an agent what happened somewhere. A case tells it where the investigation stands. Structured evidence, case state and investigation history can reduce repeated discovery work compared with reconstructing context from scratch every session.
Reconstructing from raw material
Starting from the case
What agents get
Once connected, an agent works with Mike Trace the same way a careful engineer would: read the case, gather evidence, record what was learned and hand off cleanly.
Agents can open a case and understand where the investigation stands before touching any code.
Evidence, explanations, attempts and findings are written back to the case as the agent investigates.
Agents can ask Mike Trace what is known, what is still open and what a sensible next step looks like.
When a session ends, the agent leaves a handoff so the next agent or teammate continues from where it stopped.
Agents help confirm the fix with fresh evidence and bring the investigation to a complete close.
Connecting
Agents connect using standard OAuth sign-in or browser approval. You approve each agent for a specific project, and its access is scoped and expiring.
Add Mike Trace as an MCP server in your agent or MCP-compatible client.
Sign in to your Mike Trace account in the browser and approve the agent for a specific project.
Your agent can now investigate cases in that project, with access that is scoped and expires.
Connection details and the exact endpoint for your account are shown in the Mike Trace Console.
Security