Docs · Integrations
Plans where the work already lives.
Route Corvi to your own tools behind the egress gate, then hand a finished plan straight to the agent you already use.
MCP servers & agent skills
Discover and route to MCP servers and agent skills per run — your own tools, behind the egress gate so nothing leaks without your say. Pass --mcp <server> or --skill <id> to a run; each call is opt-in and audited (see Egress & trust).
Hand off to your agent
Export a plan, or write it into the repo as .corvi/<slug>/ for Claude Code, Codex, or Cursor to pick up. Corvi also runs as an MCP server so your agent can pull plans directly. For Claude Code, the one-command plugin drops your whole library in — reads local, every tool gated by your approval.