Skip to main content

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, and any MCP-compatible client.

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:
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

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:
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:
Then run /mcp inside Claude Code to complete the FoxReach sign-in.

Available Tools

FoxReach exposes 61 tools across eleven 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

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.
Session keys created by MCP appear in Settings > API Keys as MCP Session (...) entries. They expire automatically after 2 hours and expired entries are cleaned up on the next connection.

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 > API Keys, then send it as either:
or, for hosts that only let you configure arbitrary headers:
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).