Let an agent search its past runs
Agents are first-class users of Recurz. Give one the Tracez MCP server and it can answer “how did we fix this last time?” from your own transcripts instead of guessing.
actor you: You
actor agent: Your agent
actor mcp: Tracez MCP
you -> agent: How did we fix the flaky auth test?
agent -> mcp: initialize
mcp --> agent: tools capability, server info
agent -> mcp: tools/list
mcp --> agent: Tracez's tools with input schemas
agent -> mcp: tools/call list_sessions {q: "flaky auth"}
mcp --> agent: data, next_cursor, has_more
loop until it has enough
agent -> mcp: tools/call list_turns {session_id, cursor}
mcp --> agent: a page of turns
end
agent --> you: The answer, citing the session
Steps
-
Add the server to your client
Any MCP client that supports remote HTTP servers needs two things: the URL and an
Authorizationheader with your account token. In a project's.mcp.jsonfor Claude Code that looks like this:{ "mcpServers": { "tracez": { "type": "http", "url": "https://api.recurz.ai/tracez/v1/mcp", "headers": { "Authorization": "Bearer ${RECURZ_TOKEN}" } } } } -
Search
list_sessionsmatchesqagainst session titles, native session ids and turn text, 50 sessions a page.{"jsonrpc":"2.0","id":3,"method":"tools/call", "params":{"name":"list_sessions","arguments":{"q":"flaky auth"}}} -
Read
Page through a session's turns with the
next_cursoryou got back. Long strings are cut atmax_charsand pages stop nearmax_bytes;get_turnreads one turn whole.{"jsonrpc":"2.0","id":4,"method":"tools/call", "params":{"name":"list_turns","arguments":{"session_id":"SESSION_ID"}}} -
Read the result
Every tool returns its result in
structuredContent, plus a JSON copy as text for clients that only read text. Lists page the same way everywhere. A refusal setsisErrorand carries the platform's error shape.{"data":[…], "next_cursor":"1873", "has_more":true}
An account token can call every tool, including delete_session and redact_session. If your client can allow-list tools, give the agent only the read tools it needs.