MCP server for RevyOps - connect Claude to your outbound campaign data
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"revyops-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# RevyOps MCP Server Connect [Claude](https://claude.ai) to your [RevyOps](https://revyops.com) outbound campaign data using the [Model Context Protocol](https://modelcontextprotocol.io). ## Quick Start ### 1. Install `uv` (if you don't have it) ```bash curl -LsSf https://astral.sh/uv/install.sh | sh ``` ### 2. Get your API key Log in to [RevyOps](https://app.revyops.com) and go to **Settings > API Keys** to create one. ### 3. Add to Claude Desktop Open your Claude Desktop config file: - **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json` - **Windows**: `%APPDATA%\Claude\claude_desktop_config.json` Add the following (merge into your existing config if you have other MCP servers): ```json { "mcpServers": { "revyops": { "command": "uvx", "args": ["revyops-mcp"], "env": { "REVYOPS_API_KEYS": "RO-your-key-here" } } } } ``` For multiple workspaces, comma-separate your keys: ```json { "env": { "REVYOPS_API_KEYS": "RO-key-for-client-a, RO-key-for-client-b" } } ``` ### 4. Restart Claude Desktop The RevyOps tools will appear automatically. Ask Claude things like: - "Show me campaign performance for last month" - "Which campaigns have the highest reply rate?" - "Find contacts at acme.com" - "What's our deliverability looking like?" ## Available Tools | Tool | Description | |------|-------------| | `list_clients` | List available workspaces | | `get_campaigns` | Campaign performance metrics | | `get_campaign_drilldown` | Individual contacts/companies in a campaign | | `get_email_thread` | Full email thread with a contact | | `get_deliverability` | Sending domain health metrics | | `get_campaign_stats` | High-level campaign statistics | | `get_contacts_stats` | Contact-level aggregate stats | | `get_variable_report_variables` | Available A/B tracking variables | | `get_variable_report` | A/B test report by tracking variables | | `add_campaign_note` | Add/update a campaign note | | `a…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.