vruum-gtm/mcp

Official MCP access to **Vruum**, the AI revenue platform. Give your agent the whole revenue motion — research prospects, build pipeline, run email and LinkedIn outreach, triage replies, manage deals through close, and read Stripe-backed revenue truth — through **35 compound tools** rather than a sprawl of endpoints. Outreach runs inside **objectives**: a goal, the people it targets, and the policy for reaching them.
This package is a **stdio bridge**: it serves the tool surface locally (no credentials needed to introspect) and proxies execution to https://api.vruum.ai/mcp under your token. Every call is authorized server-side — the bridge grants no authority your Vruum account doesn't already have.
> [!TIP]
> **Using a client that supports remote MCP? Connect directly instead.**
> Claude Code, Claude Desktop, Cursor, Codex and friends should point straight at https://api.vruum.ai/mcp (OAuth 2.1). Fewer moving parts and no token in an env var. This bridge exists for **stdio-only clients** and for **credential-free tool introspection**. See vruum.ai/docs/mcp.
Quickstart
You need Node 20+ and a Vruum account. Create a personal access token in the web app under **Settings → API tokens** (vk_live_…).
Claude Desktop / Claude Code — claude_desktop_config.json or .mcp.json
Cursor — ~/.cursor/mcp.json
Codex CLI — ~/.codex/config.toml
Already use the Vruum CLI? — no token needed here
The CLI needs Node 22+. Credentials land in ~/.vruum/credentials and the bridge picks them up automatically — omit the env block entirely.
Verify it works without configuring anything:
What you can ask for
Once connected, these are ordinary requests to your agent:
| You say | What happens |
| --- | --- |
| *"What should I work on today?"* | get_daily_briefing — pending approvals, new replies, stalled deals, warm paths, one recommended next action |
| *"Review my outreach drafts"* | get_outreach_review → you approve, edit, or reject each one |
| *"Research Acme Corp and tell me if they fit"* | research — website, funding, careers signals, ICP match with reasoning |
| *"Find a warm intro to this person"* | find_warm_path — separates verified paths from unverified connector candidates |
| *"Which objectives are actually working?"* | get_objective_outcomes — contacted, replied, and meetings booked, compared across objectives |
| *"What's at risk in my pipeline?"* | inspect_pipeline — the 5 most at-risk deals, risk-first |
| *"Draft a LinkedIn post about X"* | manage_content — your agent writes it, you approve, Vruum schedules and publishes |
Your harness authors outreach copy, replies, LinkedIn posts, and comments through
their review surfaces. It can also chat with Vruum through manage_assistant
(start_conversation, append_message): the same chat as the app's floating
panel, which reads your records and applies reversible record changes with Undo.
The chat does not draft or send messages.
Tool surface
35 compound tools. Read operations inspect saved data; write operations mutate it.
Some writes buy provider work or produce external effects. Each tool describes
its own authorization and retry contract.
| Area | Tools |
| --- | --- |
| **Daily operating** | get_daily_briefing · get_next_actions · inspect_pipeline |
| **Search & research** | search · fetch · research · research_lookup · import_prospects · find_warm_path |
| **People** | get_person_360 · manage_person |
| **Relationship identity** | get_network_identity_review · manage_network_identity_resolution |
| **Objectives & outreach** | inspect_objective · get_outreach_review · manage_messages · manage_outreach · manage_relationship_action |
| **Engagement & content** | get_engagement_review · manage_engagements · get_content_review · manage_content |