Your coding agent can now inspect eve Agent Runs via the Vercel MCP and CLI.
The new Vercel MCP tools and Vercel CLI commands let you find projects with Agent Runs activity, list recent runs, and retrieve full traces, including reasoning, tool calls, and token usage.
Vercel MCP tools:
Vercel CLI commands:
Every CLI subcommand supports
Ask your coding agent questions like "Show me the latest production Agent Runs for my project" or "Inspect Agent Run
Get started by installing the Vercel MCP:
Or upgrade to the latest version of the Vercel CLI:
Read more
Continue reading...
The new Vercel MCP tools and Vercel CLI commands let you find projects with Agent Runs activity, list recent runs, and retrieve full traces, including reasoning, tool calls, and token usage.
Vercel MCP tools:
list_agent_run_projects: Find projects in a team with Agent Runs activity.
list_agent_runs: List recent runs for a project.
get_agent_run: Inspect metadata, lifecycle events, usage, and subagent data.
get_agent_run_trace: Retrieve trace data for a run, including turns, messages, reasoning, tool calls, token usage, and tool input/output.
Vercel CLI commands:
vercel agent-runs projects
vercel agent-runs list
vercel agent-runs inspect <runId>
vercel agent-runs trace <runId>
Every CLI subcommand supports
--json for machine-readable output, and traces render as markdown when piped, so coding agents without MCP access can call the CLI directly to debug their own runs.Ask your coding agent questions like "Show me the latest production Agent Runs for my project" or "Inspect Agent Run
wrun_123 for my project".Get started by installing the Vercel MCP:
Or upgrade to the latest version of the Vercel CLI:
Read more
Continue reading...