Vruum Gtm MCP

What Vruum Gtm MCP MCP server does

Vruum Gtm MCP MCP server connects an MCP-compatible agent to Vruum, an AI revenue platform. Its tools cover prospect and company research, pipeline inspection, outreach workflows, engagement review, deal management, revenue data, workspace settings, and knowledge management.

The package groups related operations into 35 compound tools rather than exposing each action as a separate endpoint. Read tools inspect saved information, while write tools change records or may trigger provider work and other external effects. Outreach is organized around objectives that define a goal, target people, and contact policy.

Typical requests include generating a daily briefing, reviewing outreach drafts, researching a company, finding a warm path to a contact, comparing objective outcomes, identifying pipeline risk, and preparing content for review. The available surface also includes person records, network identity resolution, accounts, imports, assistant tasks, and performance metrics.

How it works

The npm package communicates with an agent over local stdio and JSON-RPC. It serves a bundled tools.json snapshot for tools/list, so tool introspection does not require credentials or a network request. Calls made through tools/call are proxied to https://api.vruum.ai/mcp over HTTPS with bearer authentication.

Authorization is performed by Vruum's service using the permissions of the supplied account. The bridge does not add permissions. It also does not automatically retry failed tool calls, which matters for operations that can purchase provider work or create external effects.

The local listing is a release-time snapshot. New tools may not appear in the listing until a newer package is released, although calls are forwarded to the hosted endpoint. Clients that support remote MCP can instead connect directly to the hosted endpoint using OAuth 2.1, avoiding the local bridge and token environment variable.

Setup and configuration

The stdio bridge requires Node.js 20 or newer and a Vruum account. Create a personal access token in Vruum under Settings → API tokens, then configure the client to run npx -y @vruum/mcp with VRUUM_MCP_TOKEN set to that token. Claude Desktop, Claude Code, Cursor, and Codex examples are provided in the repository.

Vruum Gtm MCP MCP server can also read credentials from the Vruum CLI. After running npx @vruum/cli login --token ..., credentials are stored under ~/.vruum/credentials, allowing the token environment entry to be omitted. The CLI login path requires Node.js 22 or newer.

Supported configuration variables are VRUUM_MCP_TOKEN, VRUUM_MCP_URL, VRUUM_MCP_TIMEOUT_MS, and VRUUM_CONFIG_DIR. The endpoint defaults to https://api.vruum.ai/mcp, the per-call timeout defaults to 300000 milliseconds, and the credentials directory defaults to ~/.vruum. The token can also fall back to VRUUM_TOKEN.

Tools and capabilities

The tool groups include:

• Daily briefings, recommended next actions, and risk-first pipeline inspection.
• Search, fetching, company research, prospect imports, and warm-path discovery.
• Person 360 records, contact management, and network identity review.
• Objective inspection, message review, outreach management, and relationship actions.
• Engagement and content review, including agent-authored posts and comments subject to review.
• Objective outcomes, performance metrics, deal records, revenue, accounts, and knowledge bases.
• History imports, assistant actions, workspace discovery, settings, and skills.

research_lookup handles external lookups such as work email, LinkedIn profiles, company websites, careers pages, and LinkedIn people searches. These lookups can consume provider credits or LinkedIn budget. Email work uses review records and explicit approval flows; starting a private draft does not approve or send it.

Limitations and notes

Vruum Gtm MCP MCP server is primarily a compatibility bridge for stdio-only clients. Remote-MCP clients should use the hosted endpoint directly when appropriate. The package's static tool snapshot means introspection can lag behind the live server until the next release.

Tool authorization follows the Vruum account, workspace, role, and tenant checks. Some write operations have financial or external consequences, and each tool documents its own authorization and retry behavior. Analysis, draft creation, and review operations do not by themselves authorize delivery or sending.