Traces
TeamsDiscoverBlogDocsHelp
Sign in
All posts

Introducing Traces MCP

Aug 21, 2026

Introducing Traces MCP

Some AI agents remember you. None of them remember your team. The shared fix your teammate's agent already found is stuck in a session only they ever say. Yours has to start from scratch.

Traces fixes the first half of this problem. Every session your team runs can be stored in one shared history. The Traces MCP fixes the other half. It puts that history directly in reach of your agent.

Traces MCP

Traces MCP is a Model Context Protocol server. Point any of our supported agents at it and your agents get read-only access to everything you've traced.

There are three tools available

  • traces_lookup: resolves people and workspaces to canonical IDs
  • traces_search: finds relevant traces by project, creator, agent, status, or timeframe
  • traces_read: pulls a bounded window of events from one specific trace

By splitting search from read, trace context loads efficiently and cheaply. It's OAuth-authenticated and read-only by default. Hosted at mcp.traces.com, or self-hosted via stdio if you'd rather work locally.

More From Us Soon

The Traces team has been working with the Traces MCP internally. We've queried our own session history as we're building. We'll be sharing more of what we've learned in a follow up post.

Stay tuned!