Vruum AI revenue platform — outbound, deals, pipeline & CRM automation over one MCP.
MCPpedia last refreshed this data
ai.vruum/mcp is an MCP server that vruum AI revenue platform — outbound, deals, pipeline & CRM automation over one MCP. Its tool list has not been published yet over http and stdio, requires no API key, and scores 87/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"vruum": {
"env": {
"VRUUM_MCP_TOKEN": "vk_live_…"
},
"args": [
"-y",
"@vruum/mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@vruum/mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @vruum/mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in data / finance
Manage Supabase projects — databases, auth, storage, and edge functions
🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
DataForSEO API modelcontextprotocol server
The Apify MCP server enables your AI agents to extract data from social media, search engines, maps, e-commerce sites, or any other website using thousands of ready-made scrapers, crawlers, and automation tools available on the Apify Store.
MCP Security Weekly
Get CVE alerts and security updates for ai.vruum/mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
@vruum/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 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.
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_config.json or .mcp.json{
"mcpServers": {
"vruum": {
"command": "npx",
"args": ["-y", "@vruum/mcp"],
"env": { "VRUUM_MCP_TOKEN": "vk_live_…" }
}
}
}
~/.cursor/mcp.json{
"mcpServers": {
"vruum": {
"command": "npx",
"args": ["-y", "@vruum/mcp"],
"env": { "VRUUM_MCP_TOKEN": "vk_live_…" }
}
}
}
~/.codex/config.toml[mcp_servers.vruum]
command = "npx"
args = ["-y", "@vruum/mcp"]
env = { VRUUM_MCP_TOKEN = "vk_live_…" }
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
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.
29 compound tool