Skip to main content
The Enrichley MCP server uses OAuth 2.1 with PKCE to authorize AI clients. You sign in once per client, and your Enrichley API key stays server-side — your AI assistant never sees it.

OAuth-protected

Industry-standard OAuth 2.1 with PKCE. Your AI client receives a short-lived token, not your API key.

Server-side credentials

Your account credential is resolved server-side, never exposed to the AI client or returned in tool responses.

Credit-based

Paid actions deduct from the same credit balance as the app, at the same prices.

​
How it works

1

Your AI client requests access.

When you connect Enrichley to a new client, it opens a browser window to begin the OAuth flow.
2

You sign in to Enrichley.

Sign in to your Enrichley account in the browser — the same account you use at app.enrichley.io.
3

The server checks account readiness.

The server confirms your Enrichley account, plan, and API credential are ready before completing the flow.
4

The client receives an OAuth token.

Your AI client only receives a short-lived OAuth token — never the API key itself.
5

Tool calls check your account live.

Every request resolves your account’s live state — plan, billing, and credential — rather than trusting what was true at connection time. An assistant can never spend against a lapsed subscription.

​
Account requirements

You need an Enrichley account with an active or trialing paid plan. The MCP server resolves your account credential server-side; you never paste an API key into the MCP authorization flow. The plan gates and service permissions that apply in the app apply identically through MCP — a service denied on your account is denied to your assistant too.

​
Scopes

When you authorize an AI client, you grant the following scopes: All five scopes are requested by default. The same scopes apply to every connected client.

​
Security best practices

Treat your API key like a password. Never paste it into a chat, share it in screenshots, or commit it to a public repo.
  • Use your own paid Enrichley account. Usage and credits are billed to the signed-in account.
  • Rotate your key if you think it has leaked. Generating a new key on your Enrichley profile immediately invalidates the old one.
  • Disconnect MCP clients you no longer use. Each client holds its own OAuth token; revoke them when you stop using a device or workspace.
  • Keep paid tools on “Needs approval” in Claude. That’s the default for run tools — your assistant asks before anything that spends.

​
Disconnecting and revoking access

You have three ways to revoke access:
  1. Disconnect inside your AI client.
    • Claude (web/desktop/mobile): Settings → Connectors → Enrichley → Disconnect.
    • Claude Code: run /mcp and clear authentication for enrichley.
    • Cursor: disable the Enrichley server in the MCP panel.
  2. Rotate your Enrichley API key. Generate a new key on your Enrichley profile. The old key is revoked immediately, and existing MCP clients may need to reconnect.
  3. Contact support. Email support@enrichley.io if you need help revoking access for a specific client or session.

​
Authentication errors

If something goes wrong during connection or a tool call, you may see one of these:

​
Next steps

Setup Guide

Connect the MCP server to your AI client.

Tools Reference

See what each tool does and how credits work.