Claude Code
Add VNTR OS as an MCP server in your config.
The agents you already run — Claude Code, Codex, any MCP client — can source, screen, and coordinate through VNTR OS. MCP, CLI, REST.
01 — Works with your stack
Add VNTR OS as an MCP server in your config.
Call VNTR OS tools from OpenAI’s coding agent.
Connect VNTR OS in Cursor’s MCP settings.
Wire VNTR OS into Windsurf over MCP.
Expose VNTR OS tools to Gemini’s tool calls.
Use VNTR OS tools inside Cline.
Connect over MCP from OpenCode.
If it speaks MCP, it can call VNTR OS.
02 — Connect through MCP
Everything the platform does — source, screen, fetch a memo, check a thesis, send a private deck — is exposed as MCP tools. Add the server, authenticate, and the brain becomes part of your own stack.
# claude_desktop_config.json
{
"mcpServers": {
"vntr-os": {
"command": "npx",
"args": ["-y", "@vntr/mcp"],
"env": { "VNTR_TOKEN": "•••" }
}
}
}03 — The tools
Read-only
Side-effectful · human-approved
Anything that sends, schedules, or shares is gated on explicit human approval. Decks are untrusted input and never drive a side-effectful call on their own.
04 — Built for how agents work
One server exposes the brain’s capabilities as tools and resources — discoverable by any MCP client, no glue code.
Every connection runs under a scoped token bound to your access levels, and every call is written to the append-only audit log.
Agents prepare and surface. Decisions, signatures, and the movement of money stay with a human — by design, not by policy.
05 — Where it goes
The same primitives are the substrate for an agent-to-agent network — your brain and another investor’s or founder’s brain sourcing, matching, and coordinating without a human pasting a link. The tools you connect today are the on-ramp.