MCP Server

Overview#

FoxReach provides a hosted Model Context Protocol (MCP) server that lets AI agents manage your leads, campaigns, templates, and email accounts through natural language. No local installation required. Just point your AI client at https://api.foxreach.io/mcp and sign in to FoxReach.

Supported clients: Claude Desktop, Cursor, Claude Code, VS Code, Cline, Goose, Gemini CLI, and any MCP-compatible client that supports remote servers.

FoxReach is listed in the official MCP Registry as io.foxreach/foxreach, so clients that browse the registry can find it by name. Setup for every client is also on GitHub: foxreach/foxreach-mcp.

Prerequisites#

• A FoxReach account with an active workspace
• A compatible MCP client installed

Setup#

Claude Desktop#

1. Open Claude Desktop settings

   Go to Settings > Connectors > Add custom connector.

2. Add the FoxReach MCP server

   Enter FoxReach as the name and the following remote MCP server URL:

   https://api.foxreach.io/mcp
3. Sign in to FoxReach

   Claude Desktop opens a browser window on FoxReach. Sign in the way you usually do (Google, an emailed sign-in link, or email and password) and click Allow. Once authorized, the MCP tools icon appears in the chat input area, confirming the connection.

Cursor#

Add FoxReach to Cursor installs the server in one step. To add it by hand instead:

1. Open Cursor settings

   Go to Settings > MCP in Cursor.

2. Add a new MCP server

   Click Add new MCP server and configure it with the following JSON:

   JSON

   {
     "foxreach": {
       "url": "https://api.foxreach.io/mcp"
     }
   }

3. Verify connection

   Cursor prompts you to authenticate. Sign in to FoxReach in the browser window and click Allow. The server should show a green status indicator once connected.

Claude Code#

Run this command in your terminal:

claude mcp add foxreach \
  --transport http \
  "https://api.foxreach.io/mcp"

Then run /mcp inside Claude Code to complete the FoxReach sign-in.

VS Code#

Add FoxReach to VS Code installs the server for GitHub Copilot chat. To add it by hand, put this in .vscode/mcp.json:

{
  "servers": {
    "foxreach": { "type": "http", "url": "https://api.foxreach.io/mcp" }
  }
}

VS Code asks you to sign in to FoxReach the first time a tool runs.

Cline#

In Cline, open MCP Servers > Remote Servers, add https://api.foxreach.io/mcp with the name foxreach, then click Authenticate and sign in to FoxReach. In cline_mcp_settings.json the entry is:

{
  "mcpServers": {
    "foxreach": { "type": "streamableHttp", "url": "https://api.foxreach.io/mcp" }
  }
}

Goose#

Add FoxReach to Goose adds FoxReach as a remote extension. Goose opens the FoxReach sign-in on first use.

Gemini CLI#

Install the FoxReach extension:

gemini extensions install https://github.com/foxreach/foxreach-gemini-extension

Then sign in to FoxReach when Gemini CLI opens the browser on the first FoxReach tool call.

Other clients#

Add a remote Streamable HTTP server with the URL https://api.foxreach.io/mcp. Clients that support MCP sign-in discover it automatically and open the FoxReach sign-in page. Clients without sign-in support can send an API key, see Connect with an API key.

Available Tools#

FoxReach exposes 89 tools across fourteen resource categories:

Leads#

Campaigns#

Sequences#

Templates#

Email Accounts#

Lead Finder#

search_people, search_companies, and count_lead_finder_results take filters as a typed object with named keys (not a free-form JSON string), so an unknown key is rejected with a 400 naming it instead of being silently dropped. get_lead_finder_filters lists every valid key.

Tracking Domains#

Warmup#

Managed Mailboxes#

Analytics#

Inbox#

Email Verification#

Webhooks#

Leads import#

Example Prompts#

Once connected, you can use natural language to interact with FoxReach:

• "List all my active campaigns": calls list_campaigns with status filter
• "Create a lead for john@acme.com at Acme Inc": calls create_lead
• "Pause the campaign named Q1 Outreach": calls list_campaigns to find it, then pause_campaign
• "Show me all email templates": calls list_templates
• "Draft a cold outreach template and save it": AI writes the copy, then calls create_template

Authentication#

The MCP server authenticates with OAuth, with FoxReach itself as the identity provider. Your MCP client opens a browser window on FoxReach's sign-in page; use Google, an emailed sign-in link, or your email and password, then approve the connection. Behind the scenes, FoxReach mints a short-lived session API key scoped to your personal workspace, so tool calls carry the same permissions and plan limits as the REST API.

All communication is encrypted via HTTPS.

Connect with an API key#

Hosts that cannot complete a browser-based sign-in flow (the Claude Messages API MCP connector, headless agents, CI, and most server-to-server integrations) can authenticate with a FoxReach API key instead of OAuth. Create one in Settings > Integrations > API Keys, then send it as either:

Authorization: Bearer otr_...

or, for hosts that only let you configure arbitrary headers:

X-API-Key: otr_...

Tool calls made with an API key run against that key's own workspace, and its scopes and plan limits apply exactly as they do for the REST API. A read-only key can still list tools, but gets a clear error back from any write tool.

Troubleshooting#

Tools not appearing in Claude Desktop Make sure the URL in your config is exactly https://api.foxreach.io/mcp. Restart Claude Desktop after making changes.

"401 Unauthorized" error Your session has expired or the tokens are stale. Clear the server's authentication in your MCP client and reconnect to sign in again.

"No FoxReach account found" error The account you signed in with has no FoxReach workspace. Sign in with the email you use for FoxReach, or create an account first.

Connection drops or timeouts Streamable HTTP connections are long-lived. Some network environments or proxies may drop idle connections. Your MCP client will automatically reconnect.

Tool calls returning errors The MCP tools call the FoxReach REST API under the hood. Check the error message. It follows the same error format as the API (e.g., 404 for not found, 409 for duplicate email).