OutreachFox MCP server: use OutreachFox from Claude, Cursor and other AI agents

Draft — written from product facts + domain knowledge; UI labels to be verified before publishing.

The OutreachFox MCP server lets AI assistants that support the Model Context Protocol (Claude, Cursor, Windsurf, VS Code Copilot and others) read and act on your OutreachFox workspace. Once connected you can ask an assistant to summarise yesterday's replies, draft a three-step sequence, upload a lead list or pause a campaign with a high bounce rate, and it calls OutreachFox for you.

Prerequisites

• An OutreachFox API key. Use Read only scope if you want the assistant to report but never change anything; use Read and write to let it create campaigns and leads.
• A client that supports remote MCP servers. Claude (web, desktop and Claude Code), Cursor 0.45 or later, Windsurf and VS Code with Copilot all do.

Steps: Claude

1. In Claude, open Settings → Connectors (or Customize → Connectors on the web) and click Add custom connector.
2. Enter the name OutreachFox and the server URL https://mcp.outreachfox.com/mcp.
3. Click Add. When prompted, paste your API key in the Authorization field as Bearer of_live_..., or sign in with your OutreachFox account if OAuth is offered.
4. Start a new chat and confirm the OutreachFox tools are listed under the tools menu.

For Claude Code, run claude mcp add --transport http outreachfox https://mcp.outreachfox.com/mcp --header "Authorization: Bearer of_live_...".

Steps: Cursor and other editors

1. Open Settings → MCP and click Add new MCP server, or edit .cursor/mcp.json in your project.
2. Add:

{

"mcpServers": {

"outreachfox": {

  "url": "https://mcp.outreachfox.com/mcp",

  "headers": { "Authorization": "Bearer of\_live\_xxxxxxxx" }

}

}

}

1. Save and reload. The server should show a green status with its tool list.

For VS Code use the same JSON under "servers" in .vscode/mcp.json; for Windsurf use ~/.codeium/windsurf/mcp_config.json.

Tools the server exposes

Write tools ask your client for confirmation before running, so nothing is sent or changed without you approving it.

Example prompts

• "List campaigns with a bounce rate above 3% and pause them."
• "Summarise interested replies from the last 7 days, grouped by campaign, with the lead's company and the sentence that shows intent."
• "Draft a 3-step email sequence for CFOs at Series B SaaS companies, run it through the spam words checker, then create it as a paused Email Outreach campaign named 'CFO Q4'."
• "Which mailboxes have a health score below 70? Show their spam placement for the last 14 days."
• "Add these 40 leads from the CSV in this folder to the 'CFO Q4' campaign, skipping duplicates."

Tips

• Create a separate API key named mcp so you can revoke agent access without breaking other integrations.
• Start with Read only. Move to Read and write once you trust the assistant's judgement on your data.
• The server respects the workspace of the key. Connect a second server entry with a different key to work across several workspaces.
• Agents count against the same rate limit as the API (60 requests per minute per key).

Troubleshooting

• Server shows as disconnected: check the header format (Bearer plus the key) and that the key is not revoked.
• "Permission denied" on a write: the key is Read only.
• Tools missing in the chat: start a new conversation after adding the connector; existing chats do not pick up new tools.

Related articles

• API keys and authentication
• Webhooks: events, payload examples and retries
• Connect OutreachFox to Zapier and Make
• Adding Steps to Email Campaigns
• Mailbox Warmup Analytics Guide