agent-observability vercel-mcp debugging eve-framework cli-tools

Vercel MCP exposes Agent Runs via CLI tools

Query, inspect, and trace eve agent executions directly from CLI or MCP interface—reasoning, tool calls, and token usage included.

Summary

Debugging agent behavior moves from logs to structured trace inspection. Agents can now self-inspect their own runs programmatically, enabling automated skill updates and post-execution analysis without leaving your workflow.

Why it matters

Implementation verdict

Replaces manual log inspection with query-driven trace access. Requires Vercel deployment for automatic trace ingestion; supports both MCP client integration and CLI-only workflows. Ready now—install via `npx add-mcp https://mcp.vercel.com` or upgrade CLI. The `--json` output and markdown rendering make this immediately useful for agent-driven debugging loops.

Sources

1.eve traces are automatically ingested when deployed to Vercel and available as Agent Runs
2.Retrieve trace data for a run, including turns, messages, reasoning, tool calls, token usage, and tool input/output
3.traces render as markdown when piped, so coding agents without MCP access can call the CLI directly to debug their own runs

Dev Signal

Get briefs like this in your inbox — free, every weekday.

100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.

Read the full issue →All briefs