Traceo MCP

AI agents

API

AI agents

Traceo MCP

Connect Traceo to Claude, Cursor, Codex, VS Code or any MCP client. Paste a Traceo link and your agent reads the console logs, network requests and clicks behind the bug.

A Traceo recording captures what happened in a browser tab: the video, every click, the console and the network, plus the browser and window size. Traceo MCP gives your agent all of it from the share link, so no one has to retype what they saw or copy logs by hand.

Server URL

https://www.traceo.dev/mcp

Streamable HTTPNo sign-inRead-only

Connect your client

Pick your client. Every option points at the same server.

Add the server

Install the Traceo plugin. It connects the MCP server and adds the Traceo skills:

claude code

/plugin marketplace add muhamad-0/traceo-skills
/plugin install traceo@traceo-plugins

Or add the server on its own:

shell

claude mcp add --transport http traceo https://www.traceo.dev/mcp

Check it
Start a new session and run /mcp. Traceo shows as connected with seven tools. No sign-in is needed.

The skills and plugins are open source at github.com/muhamad-0/traceo-skills. To add the skills to any agent without a plugin, run npx skills add muhamad-0/traceo-skills.

Use it

1. Copy a Traceo link

Share a recording from the extension, or open one on traceo.dev. It looks like traceo.dev/82efc2….

2. Say what you want

One sentence is enough. The agent picks the tools, reads the recording and reports back.

3. Approve the tool calls

Your client asks once to allow the Traceo tools. After that the agent keeps going on its own.

What to say

Paste a link and say what you want. These are the prompts the MCP tab on every recording page gives you. Each one names the skill that does the job best.

prompt · traceo-fix

Fix the bug in this Traceo recording:
- https://www.traceo.dev/82efc229a22f4ffd81

Use the console logs, network requests and user actions to find the root cause.
Explain the cause in one line, then make the fix.

If the traceo-fix skill is available, use it.

Tools

Your agent chooses among these. You only need the list to know what is possible, or to name a tool in a prompt. Every tool takes the share link or the recording id.

Tool	What it returns
`get_recording`	Start here. The page, browser, OS and window size, event counts, the first errors and failed requests, the clicks before the first problem, and a `Next:` hint for the agent.
`get_timeline`	Console, network and user actions merged in time order (`+12.4s`). Narrow it with `from_s`, `to_s` and `types`.
`get_console_logs`	Console output, one line per entry. Filter with `level` and `search`.
`get_network_requests`	Every request: method, status, URL, duration, type and size. Filter with `status` (`failed`, `4xx`, `500`…), `method`, `domain`, `type`. Add `include_headers` for headers.
`get_user_actions`	Clicks, inputs and navigations in order, with the target element and page path.
`get_comments`	Comments the reporter attached when sharing the recording.
`get_frames`	Stills from the video, saved after each click, error and failed request. Pass `at_s` to see the screen at a moment, or `from_s` and `to_s` for a range. Up to 6 images per call.
`get_thumbnail`	A still image of the recorded page.

Results are plain text lines with times from the start of the recording, for example +3.1s POST 500 api.example.com/v1/cart 812ms. That keeps them short enough for an agent to read in one go.

Your recordings (sign in)

Want your agent to find recordings without a link, or to comment on them? Connect the account address instead. Your client opens a Traceo sign-in page the first time; approve it and you get every tool above plus these.

shell

claude mcp add --transport http traceo https://www.traceo.dev/mcp/me

Tool	What it does
`list_my_recordings`	Your recordings, newest first, with title, date, duration and share link.
`search_recordings`	Your recordings whose title, source or creator matches every word of a query.
`add_comment`	Posts a comment as you on a recording's share page, for example the root cause the agent found.

Sign-in uses OAuth, so Traceo never sees a password or API key in your client. The agent can read your recordings and post comments; it cannot delete recordings or change your account. Access ends after 30 days without use, or when you disconnect the agent in Settings → Apps.

Skills

Skills teach your agent the best way to use the tools. You don't need to remember their names: paste a link, say what you want, and the agent picks one.

shell

npx skills add muhamad-0/traceo-skills

traceo

“Take a look at this recording.”

Reads the link and picks the right skill below.

traceo-fix

“Fix this.”

Root cause from the errors, failed requests and steps, with evidence. Edits code only when you ask.

traceo-summarize

“What's in this?”

What the user did, what broke and where, in a few lines.

traceo-to-e2e

“Write a test for this.”

An end-to-end test with your project's own setup that fails until the bug is fixed.

traceo-to-ticket

“Make a ticket for this.”

Steps, expected vs actual, environment and evidence, filed in Linear, GitHub or Jira.

traceo-setup

“Set up Traceo.”

Connects Traceo MCP, installs these skills and checks the connection.

Privacy and security

Same access as the link. The public address returns only what the share link already shows. The signed-in address adds listing and commenting on your own recordings, and nothing can delete them.
Secrets are redacted. Tokens, API keys and JWTs in console messages are replaced with [redacted], along with authorization and cookie headers. URLs are stored without query strings.
Expiry is respected. Expired or deleted recordings return nothing.

A recording comes from a third-party web page, so its console messages and labels could contain text aimed at your agent. Every Traceo tool result is marked as untrusted data, and the Traceo skills tell the agent never to follow instructions found inside a recording.

FAQ

Do I need a Traceo account or an API key?

Not to read a recording: the public address works from its share link alone. Sign in only if you want your agent to list, search or comment on your own recordings (see Your recordings). There is never an API key.

Which recordings work?

Recordings shared from the Traceo Chrome extension with a share link. Console and network data are there when those capture options were on. Recordings shared before trace sharing existed return their title and thumbnail only.

How long does a link work?

Free share links last 3 days. Pro links do not expire. An expired link returns a clear message instead of data.

Can the agent see request and response bodies?

No. Traceo does not capture bodies, strips query strings from URLs, and redacts sensitive headers such as authorization and cookies.

Can my agent watch the video?

It sees stills. Recordings shared from the latest extension save frames after each click, error and failed request, and get_frames returns the ones nearest any moment. Older recordings have the thumbnail only.