Setup

Connect the Enrichley MCP server to your AI assistant in a couple of minutes. You will need an Enrichley account on a paid plan.

Prerequisites

An Enrichley paid plan (sign up).
An AI client that supports remote MCP servers with OAuth (Claude, Claude Code, Cursor, VS Code, or Codex).

MCP endpoint

Use this URL wherever your client asks for the MCP server URL:

https://mcp.enrichley.io/mcp

Client setup

Claude (web / desktop / mobile)
Claude Code
Cursor
VS Code
Codex

Add Enrichley as a custom connector to use it in Claude chats on the web, in the desktop app, and on mobile.

Open connector settings

In Claude, go to Settings → Connectors and click Add custom connector.

Name it and paste the URL

Name: Enrichley. URL: https://mcp.enrichley.io/mcp. Click Add.

Connect and sign in

Click Connect on the new connector. Your browser goes through Enrichley sign-in — use the same account you use at app.enrichley.io — and an authorization screen listing the requested scopes. Click Allow, then Authorize Claude.

Check the tools

Back in connector settings you should see Enrichley’s tools listed, grouped by permission. Paid actions default to Needs approval, so Claude asks before starting anything that spends credits.

Claude renders Enrichley’s interactive cards: your account status, preview tables, run quotes you can adjust and confirm yourself, and a download handoff with an Open in Enrichley button.

Complete the sign-in promptly after clicking Connect — the authorization attempt expires after a few minutes, and Claude will ask you to restart the connection.

On Claude Team and Enterprise plans, an Owner must first add the connector in Organization settings; members then connect it under Settings → Connectors with their own Enrichley sign-in.

The recommended path is the Enrichley plugin — it configures this server and bundles a skill that makes Claude noticeably better at multi-step lead workflows:

/plugin marketplace add getEnrichley/enrichley-mcp-plugin
/plugin install enrichley@enrichley

Alternative — add the server directly with the Claude Code CLI:

claude mcp add --transport http enrichley https://mcp.enrichley.io/mcp

Then open Claude Code and run:

/mcp

Follow the browser prompt to sign in to your Enrichley account and authorize the requested scopes. Claude Code stores and refreshes the OAuth token on your machine.Scope optionsPass --scope to control where the server is available and where the config is stored:

Flag	Scope	Config file
`--scope local` (default)	Current project only	`~/.claude.json`
`--scope project`	Shared with team	`.mcp.json` in project root
`--scope user`	All your projects	`~/.claude.json`

Example — share with your team via the project-level config:

claude mcp add --scope project --transport http enrichley https://mcp.enrichley.io/mcp

Each teammate still completes the OAuth flow with their own Enrichley account.Alternative — add via JSON

claude mcp add-json enrichley '{"type":"http","url":"https://mcp.enrichley.io/mcp"}'

Project-local .mcp.jsonIf you prefer to commit the config directly, drop this in your repo root:

{
  "mcpServers": {
    "enrichley": {
      "type": "http",
      "url": "https://mcp.enrichley.io/mcp"
    }
  }
}

Use the /mcp menu in Claude Code to clear authentication or reconnect.

Add the Enrichley server to your Cursor MCP configuration.File: .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global)

{
  "mcpServers": {
    "enrichley": {
      "url": "https://mcp.enrichley.io/mcp"
    }
  }
}

Create or edit the config file

Open .cursor/mcp.json in your project root, or ~/.cursor/mcp.json for all projects.

Paste the config above

Save the file.

Restart Cursor

Restart Cursor, enable the Enrichley server in the MCP/tools panel, and complete the OAuth browser flow when prompted.

Use the project-level config (.cursor/mcp.json) to scope Enrichley to a single repo. Use the global config (~/.cursor/mcp.json) to make it available everywhere.

VS Code’s built-in MCP client supports remote HTTP servers with OAuth.File: .vscode/mcp.json (workspace) or open the user mcp.json via Cmd+Shift+P → MCP: Open User Configuration

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

Create the config file

Add .vscode/mcp.json to your workspace, or open the user-level file via the command palette.

Paste the config above

Save the file. VS Code picks up MCP server changes automatically.

Authorize the server

Run MCP: List Servers from the command palette, select enrichley, and complete the browser sign-in.

VS Code uses "servers" (not "mcpServers") and requires "type": "http" for remote servers.

The OpenAI Codex CLI supports remote streamable HTTP MCP servers with OAuth.Quick install — register the server, then complete the OAuth login:

codex mcp add enrichley --url https://mcp.enrichley.io/mcp
codex mcp login enrichley

codex mcp login opens your browser to sign in to Enrichley and authorize the requested scopes. After it completes, run codex mcp list to confirm the server is connected.Manual configEdit ~/.codex/config.toml (user-level) or .codex/config.toml in your project root (project-level, trusted projects only):

[mcp_servers.enrichley]
url = "https://mcp.enrichley.io/mcp"

After saving, run codex mcp login enrichley to complete the OAuth flow.

If you run multiple OAuth-protected MCP servers and need a fixed callback port (for example, behind a corporate proxy), set mcp_oauth_callback_port at the top level of ~/.codex/config.toml. Otherwise Codex picks an ephemeral port automatically.

Need to test the server outside of an AI client? See Debugging with MCP Inspector.

More clients

Beyond the clients above, the Enrichley MCP server has been validated against these additional MCP-compatible clients. Pick your client below for setup details.

Amazon Q Developer CLI

Amazon Q Developer CLI supports remote HTTP MCP servers with OAuth.Config file: ~/.aws/amazonq/mcp.json (global) or .amazonq/mcp.json (workspace)

{
  "mcpServers": {
    "enrichley": {
      "type": "http",
      "url": "https://mcp.enrichley.io/mcp"
    }
  }
}

After saving, start a Q CLI session with an agent that includes this server. Run /mcp — Q CLI will mark the server as “not yet loaded” and provide an authorization URL. Open it in your browser, sign in to Enrichley, and authorize the requested scopes.

Cline (VS Code extension)

Cline supports remote HTTP MCP servers via the streamableHttp transport, including OAuth.Open the Cline panel → Configure → Configure MCP Servers, and add:

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

On first connect, Cline displays an OAuth URL in VS Code. Click it to complete sign-in in your browser. Cline stores credentials securely and reconnects automatically when you reload.

Gemini CLI

Gemini CLI supports remote HTTP MCP servers with OAuth via auto-discovery.Config file: ~/.gemini/settings.json (user) or .gemini/settings.json (project)

{
  "mcpServers": {
    "enrichley": {
      "url": "https://mcp.enrichley.io/mcp"
    }
  }
}

Gemini CLI auto-detects HTTP transport, falls back to SSE if needed, and discovers the OAuth flow from the server’s protected-resource metadata. On first use it opens your browser for sign-in.

JetBrains IDEs (AI Assistant 2025.2+)

JetBrains AI Assistant supports remote MCP servers with OAuth 2.1 + PKCE in version 2025.2 and newer.Open Settings → Tools → AI Assistant → Model Context Protocol (MCP) and add a new server, or edit the JSON config directly:

{
  "mcpServers": {
    "enrichley": {
      "url": "https://mcp.enrichley.io/mcp"
    }
  }
}

When you first invoke an Enrichley tool, the IDE opens your browser to complete the OAuth flow. Tokens are stored and refreshed automatically.

Requires AI Assistant 2025.2 or newer for full OAuth + Streamable HTTP support.

Roo Code (workaround required)

Roo Code’s native streamable-http transport does not yet trigger OAuth flows reliably on a 401 challenge (tracked in Issue #8119). Until that ships, use mcp-remote as a local stdio bridge — it handles OAuth on Roo Code’s behalf.Open Roo Code’s MCP settings and add:

{
  "mcpServers": {
    "enrichley": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.enrichley.io/mcp"
      ]
    }
  }
}

mcp-remote opens your browser for OAuth on first run and caches tokens locally. Once Roo Code adds native OAuth 2.1 support, you can switch to a direct HTTP config.

Zed

Zed supports remote HTTP MCP servers with OAuth. Note that Zed uses context_servers in its config (not mcpServers).Open Zed’s settings (Cmd+, on macOS) and add:

{
  "context_servers": {
    "enrichley": {
      "url": "https://mcp.enrichley.io/mcp"
    }
  }
}

When no Authorization header is configured, Zed initiates the standard MCP OAuth flow on first use.

There are open reports of Zed’s OAuth flow not always triggering reliably (Issue #43162). If you hit this, fall back to mcp-remote as a stdio bridge.

Not currently supported

GitHub Copilot Coding Agent cannot be used with the Enrichley MCP server. Per GitHub’s documentation, the Copilot cloud agent does not support remote MCP servers that use OAuth for authentication. We will revisit this when GitHub adds OAuth support.

Other MCP-compatible clients

The Enrichley MCP server works with any client that implements Streamable HTTP transport with OAuth 2.1 + PKCE. If your client meets that bar, point it at:

https://mcp.enrichley.io/mcp

Static-API-key client configurations (using a header field like x-api-key) are not supported. The Enrichley MCP server requires OAuth.

If you get it working with a client we haven’t documented, let us know at support@enrichley.io and we’ll add it.

Verify the connection

Ask your AI assistant:

“Check my Enrichley credit balance.”

Your assistant should call the enrichley_get_account_status tool and return your available credits — in Claude, it renders as a card with a Refresh button. This call is free. If it works, you’re done. If not, see Troubleshooting.

Get Started

Lead Discovery

API Reference

Integrations

MCP Server

Prerequisites

MCP endpoint

Client setup

More clients

Not currently supported

Other MCP-compatible clients

Verify the connection

Next steps

Tools Reference

Authentication

​Prerequisites

​MCP endpoint

​Client setup

​More clients

​Not currently supported

​Other MCP-compatible clients

​Verify the connection

​Next steps

Tools Reference

Authentication

Prerequisites

MCP endpoint

Client setup

More clients

Not currently supported

Other MCP-compatible clients

Verify the connection

Next steps