Eryx MCP connector

Connect Eryx to Claude, ChatGPT, Codex, Cursor, or any client that supports the Model Context Protocol (MCP) over Streamable HTTP.

The connector can read projects, leads, usage, and run status. With explicit write scopes, it can also start a discovery run or send an outreach message. Review the requested permissions on the Eryx consent screen before allowing access.

Before you connect

You need an Eryx account and an existing workspace.
Only a workspace owner or admin can authorize a connector or create an API key.
Use the production MCP server URL: https://eryx-mcp.groundforr.workers.dev/mcp. The service currently runs on Cloudflare Workers; mcp.eryx.digital is not the production endpoint until that custom domain is announced.
Keep the server URL ending in /mcp.

Connect with OAuth

OAuth is recommended because you do not need to copy an API key into the client.

In your MCP client, choose Add connector, Add custom connector, or the equivalent option.
Enter the Eryx production MCP server URL.
Your browser opens the Eryx sign-in and consent flow.
Sign in, choose the intended workspace, review the requested scopes, and select Allow.
Return to the client and confirm that the seven Eryx tools are available.

Eryx uses OAuth 2.1 authorization code flow with PKCE. The issued bearer token is workspace-scoped and remains active until an owner or admin revokes the corresponding key in API keys.

Connect with a static API key

Use this option for local development or a client that does not support OAuth.

In Eryx, open API keys.
Select Create key, give it a recognizable name, and grant only the optional scopes the client needs.
Copy the token immediately. It is shown once.
Configure the client with the production MCP server URL and the header Authorization: Bearer eryx_pat_....

Example MCP configuration:

{
  "mcpServers": {
    "eryx": {
      "url": "https://eryx-mcp.groundforr.workers.dev/mcp",
      "headers": {
        "Authorization": "Bearer eryx_pat_..."
      }
    }
  }
}

Never put an Eryx token in source control, screenshots, support tickets, or chat messages. Revoke a token from API keys if it may have been exposed.

Tools and permissions

Tool	What it does	Permission and effect
`list_projects`	Lists projects in the authorized workspace	Read-only
`get_project`	Returns one project and its summary	Read-only
`list_leads`	Lists and filters workspace leads	Read-only; results can include contact and outreach fields
`get_usage`	Returns plan, credits, and run limits	Read-only
`trigger_run`	Starts a discovery run and can consume credits	Requires `runs:trigger`; irreversible after it starts
`get_run`	Returns run status and progress	Read-only
`send_outreach`	Sends the prepared outreach message through a connected channel	Requires `outreach:send`; external and not reversible

Read access is included with every valid connector token. OAuth clients request optional write scopes during authorization. Static keys receive only the optional scopes selected at creation.

Test the connection

After connecting, run each tool you intend to use:

Call list_projects, then get_project with one returned project ID.
Call list_leads with a small limit.
Call get_usage.
If you granted runs:trigger, start a run only in a test project and then poll it with get_run.
If you granted outreach:send, use a test lead and test destination. Sending outreach cannot be undone.

Tool results include structured data for MCP clients and a text representation for compatibility.

Example prompts

“List my active Eryx projects, then tell me which one ran most recently and how many run credits remain.”
“Find high-priority leads in project 42 with a score of at least 75 and summarize the best three without sending anything.”
“Start a discovery run for test project 42, then check its status and report the run ID.”
“Show me the prepared outreach for test lead 123. Send it only after I explicitly confirm.”

Disconnect or change permissions

Open API keys in Eryx and revoke the key named for the OAuth client or the static key you created. To use fewer permissions, revoke the existing key and reconnect or create a replacement with only the required scopes.

Data and privacy

The MCP Worker is a stateless proxy. It forwards the connector token and tool request to the Eryx API and does not add a separate connector database. Normal Eryx workspace retention still applies to projects, leads, runs, usage, and outreach records.

Your chosen MCP client receives the tool inputs and results needed to perform the request. That provider may retain or process this data under its own terms and privacy policy. Do not connect Eryx to a client unless your organization permits that transfer. See the Eryx Privacy Policy for the full connector disclosure.

Troubleshooting

The browser does not open for consent: confirm the client supports remote MCP OAuth and that the URL ends in /mcp.
Only an owner or admin can authorize: switch to an Eryx account with workspace management permission.
FORBIDDEN_SCOPE: reconnect with the required scope or create a replacement key with runs:trigger or outreach:send.
NOT_FOUND: the ID is not present in the authorized workspace, or the object was removed.
Connection lost after revocation: expected; authorize again to issue a new token.

For setup or review support, contact business@eryx.digital. Never email access tokens or passwords.