VruumVruum

MCP

Connect the Vruum MCP server — the curated default-loaded tool set, Tool Search for the deferred tail, and the vruum_exec escape hatch.

The Vruum MCP server at https://api.vruum.ai/mcp is the hosted surface for operating Vruum from any MCP client (Claude, ChatGPT, Cursor, …). It hits the same authorized backend endpoints as the CLI, under your own token — every call is authorized server-side exactly as a normal user's would be.

Connecting

The simplest path is vruum init: it registers the MCP (Bearer-authed against https://api.vruum.ai/mcp) into every detected harness, reusing the token from vruum login. init writes a static Authorization: Bearer MCP config — it avoids interactive-OAuth re-auth that drops hosted MCP connections mid-session. Restart your harness afterwards, then verify with a real tool call.

Default-loaded tools

The server advertises the full operation set (~139 tools) but default-loads a curated set to keep tool selection accurate and context small. The curated default covers the full daily loop — briefing → review → message/plan management → deal updates → core CRM writes:

AreaTools
Daily-loop dashboardsget_daily_briefing, get_next_actions, get_outreach_review, get_engagement_review, get_content_review, get_deal_360, get_person_360, inspect_pipeline, get_operator_dashboard, get_performance_metrics
Outreach actionsstart_outreach, manage_message, bulk_manage_messages, manage_outreach_plan, generate_reply_draft
Deal actionscreate_deal, update_deal, qualify_deal, record_deal_outcome, manage_deal_stakeholders
Marketing & engagementmanage_engagement, manage_content_post, manage_ad_campaign
Core CRM & researchcreate_manual_person, add_person_note, search_knowledge_base

Tool Search — the deferred tail

Tools outside the default set are deferred, not removed — they stay advertised and callable. A Tool-Search-capable client (Anthropic Tool Search) registers the tool_search_tool_bm25_20251119 server-tool and BM25-searches the deferred tail at runtime instead of loading all ~139 tools into context. Where a client ignores the defer hint, nothing regresses — every tool stays loaded and callable.

vruum_exec — the full surface through one tool

vruum_exec is the escape hatch: it runs the bundled vruum CLI server-side under your own auth, giving any MCP client the entire Vruum surface through a single tenant-scoped tool — including operations not in the default set.

  • Pass args as the CLI argv array, never a shell string: ["deal", "list", "--json"], ["whoami", "--json"].
  • Use --json inside args for machine-stable stdout. A non-zero CLI exit surfaces as a tool error carrying the CLI's stderr.
  • for_company mirrors the operator multi-tenant UX (falls back to the request's X-Company-Id header when omitted).

Blocked by design

vruum_exec runs under the token the server injects, so a few operations are blocked and must be run from the local CLI instead:

  • Credential/host commands (login, logout, init, the auth commands) — the server injects your token; the CLI must not manage creds.
  • Local-file ingestion (people import csv, ad creative upload, --content-file, @file args, host paths) — these read files off the server's filesystem.
  • The --api-url host-override flag (and VRUUM_API_URL) — it would redirect the authenticated call to an arbitrary host and exfiltrate your token, so the server resolves the API URL itself.

See also

  • Auth — the Bearer token model and --for-company.
  • vruum init — wire the MCP into your harness.
  • Operate Vruum — the full agent operator's guide.