Agent Runs now available in the Vercel MCP and CLI
Agents can now inspect Agent Runs via the Vercel MCP and CLI, with automatic trace ingestion when deployed to Vercel. New tools and commands let you find projects with runs, list recent runs, and retrieve full traces including reasoning, tool calls, and token usage.
Your agent can now inspect via the Vercel MCP and CLI for , the open-source agent framework.Agent Runseve
eve traces are automatically ingested when deployed to Vercel and available as Agent Runs. The new and let you find projects with runs, list recent runs, and retrieve full traces, including reasoning, tool calls, and token usage.Vercel MCP toolsVercel CLI commands
Vercel MCP tools:
Vercel CLI commands:
Every CLI subcommand supports 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.--json
Ask your coding agent questions like "Show me the latest production Agent Runs for my project" or "Update skills based on recent runs".
Get started by installing the Vercel MCP:
Or upgrade to the latest version of the Vercel CLI:
: Find projects in a team with Agent Runs activity.
list_agent_run_projects: List recent runs for a project.
list_agent_runs: Inspect metadata, lifecycle events, usage, and subagent data.
get_agent_run: Retrieve trace data for a run, including turns, messages, reasoning, tool calls, token usage, and tool input/output.
get_agent_run_trace
vercel agent-runs projectsvercel agent-runs listvercel agent-runs inspect <runId>vercel agent-runs trace <runId>
Source: original entry ↗