Mcp · LLM Mart

Name: Mcp
Author: LLM Mart

No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.

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 29 compound tools rather than a sprawl of endpoints.

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

{
  "mcpServers": {
    "vruum": {
      "command": "npx",
      "args": ["-y", "@vruum/mcp"],
      "env": { "VRUUM_MCP_TOKEN": "vk_live_…" }
    }
  }
}

Cursor — ~/.cursor/mcp.json

{
  "mcpServers": {
    "vruum": {
      "command": "npx",
      "args": ["-y", "@vruum/mcp"],
      "env": { "VRUUM_MCP_TOKEN": "vk_live_…" }
    }
  }
}

Codex CLI — ~/.codex/config.toml

[mcp_servers.vruum]
command = "npx"
args = ["-y", "@vruum/mcp"]
env = { VRUUM_MCP_TOKEN = "vk_live_…" }

Already use the Vruum CLI? — no token needed here

npx @vruum/cli
vruum login --token vk_live_…

Credentials land in ~/.vruum/credentials and the bridge picks them up automatically — omit the env block entirely.

Verify it works without configuring anything:

npx -y @modelcontextprotocol/inspector --cli npx -y @vruum/mcp --method tools/list

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 campaigns are actually working?"	`get_campaign_outcomes` — contacted, replies, meetings booked, cohort-consistent
"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

Important

Your agent writes the prose — the server never does. Outreach copy, replies, LinkedIn posts and comments surface to your harness as work items. Vruum schedules, gates, persists and sends; it has no server-side message generation. That's a deliberate design position, not a gap.

Tool surface

29 compound tools — one per decision, so an agent never disambiguates between overlapping verbs. read is safe to call freely; write mutates; destructive can delete or archive.