RichAPI hosts a remote MCP server at https://mcp.richapi.ai/mcp. Add that one URL to Claude, ChatGPT, Claude Code, Cursor, Windsurf, or another MCP client. Sign in to RichAPI and click Allow. The client then calls RichAPI tools directly, and every call spends credits from the organization balance, through the workspace that owns the API key named on the consent screen.

What is MCP?

Model Context Protocol (MCP) is an open standard that lets an AI assistant call an outside service through a fixed interface. RichAPI runs an MCP server, so an assistant such as Claude reads RichAPI data without a plugin and without custom code.

What does a RichAPI MCP connection give you?

A connection turns every public RichAPI endpoint into a tool that your AI assistant can call in plain language. You ask Claude to enrich a LinkedIn profile, and Claude sends the request to RichAPI and reads the response back to you. You copy no API key into the client. The client stores an OAuth bearer token. The token works with the access of an API key of the workspace, but it does not contain the key. RichAPI never sees the conversations inside your AI assistant.

What you get	Detail
One URL for every client	`https://mcp.richapi.ai/mcp`
Transport	Remote HTTP. Some clients name it Streamable HTTP.
Authorization	OAuth 2.1 with PKCE `S256`, plus dynamic client registration (RFC 7591)
Secret handling	The client never receives the RichAPI API key.
Tool list	Built at run time from the live RichAPI catalog
Revocation	One click on the Connected Apps page

Where is the MCP Setup page?

Page element	What it shows
Sidebar group	API Platform
Sidebar item	MCP Setup
URL	`/home/<account-slug>/mcp-setup`
Page title	MCP Setup
Browser tab title	MCP Setup — AI Integration
Page heading	Connect AI tools to RichAPI

The MCP Setup page holds a Copy button for the server URL, one tab for each client type, and a Go to Connected Apps link.

What do you need before you connect?

CAUTION: Create an API key first. When the workspace has no active API key, the consent screen refuses the authorization and shows No API key yet.

Prerequisite	Where to get it
An active RichAPI API key on the workspace	The API Keys page, at `/home/<account-slug>/api-keys`
Credits on the workspace	The Plans & Billing page
An MCP client with remote HTTP transport	Claude Desktop, Claude Code, Cursor, Windsurf, Zed, or another client
A RichAPI sign-in in the same browser	The browser that the client opens

When the workspace has no active key, the MCP Setup page shows a red alert. The alert is titled You need an active API key first. It holds a Create an API key link.

How to connect Claude Desktop to RichAPI

Open Claude Desktop.
Go to Settings → Connectors.
Click Add custom connector.
Paste https://mcp.richapi.ai/mcp into the URL field.
Click Connect.
Sign in to RichAPI in the browser window that Claude opens.
Read the Connect RichAPI consent screen. Confirm the client name and the account name.
Click Allow.
Return to Claude Desktop. The RichAPI tools are available in any chat.

How to connect Claude Code to RichAPI

Claude Code needs no JSON file. One terminal command adds the server.

Open a terminal.
Run the command below.
Claude Code opens RichAPI in your browser.
Sign in to RichAPI and click Allow.
Return to the terminal and send the example prompt to confirm the connection.

claude mcp add --transport http richapi https://mcp.richapi.ai/mcp

How to connect Cursor to RichAPI

Open Cursor → Settings → Cursor Settings → MCP.
Click New MCP Server. Cursor opens your mcp.json file.
Paste the snippet below. If the file already holds other servers, merge the snippet into mcpServers.
Save the file as ~/.cursor/mcp.json, or as .cursor/mcp.json inside the project.
Cursor re-reads the file and opens the RichAPI sign-in flow in your browser.
Sign in and click Allow.
Open a new Cursor chat. The RichAPI tools are available.

{
  "mcpServers": {
    "richapi": {
      "url": "https://mcp.richapi.ai/mcp"
    }
  }
}

How to connect Windsurf, Zed, or another MCP client

Open your client and find Add custom MCP server, Remote MCP, or Add HTTP MCP.
Enter the URL https://mcp.richapi.ai/mcp.
Set the transport to http. Some clients name it Streamable HTTP.
Sign in to RichAPI in the browser window that the client opens.
Click Allow.
Open a new chat in the client and send the example prompt.

How to test a new MCP connection

Send this prompt to your AI assistant. The MCP Setup page prints the same example.

Enrich the LinkedIn profile for linkedin.com/in/satyanadella

A correct answer names the profile and costs 1 credit. If the assistant reports no RichAPI tool, read the troubleshooting table below.

How does RichAPI authorize an MCP client?

RichAPI uses OAuth 2.1 with PKCE. The client never handles the RichAPI API key.

Step	What happens	Where
1	The client reads the server metadata.	`https://mcp.richapi.ai/.well-known/oauth-authorization-server`
2	The client registers itself and sends its `client_name`.	`POST /register`
3	The client opens `/authorize` in your browser with a `code_challenge`.	`GET /authorize`
4	RichAPI signs the request and redirects to the consent page.	`https://app.richapi.ai/oauth/consent`
5	If you are signed out, RichAPI asks you to sign in first.	`/auth/sign-in`
6	You read the consent screen and click Allow or Deny.	The consent page
7	RichAPI records the connection and returns an authorization code to the client.	`GET /oauth/callback`
8	The client exchanges the code and the PKCE verifier for a bearer token.	`POST /token`
9	Every tool call carries the bearer token.	`POST /mcp`

The consent screen is titled Connect RichAPI. It names the client under Requesting access, the signed-in user under Signed in as, and the API key prefix that pays for the calls. The buttons are Deny and Allow.

OAuth setting	RichAPI rule
Authorization request lifetime	10 minutes
Access token lifetime	1 hour
Refresh token lifetime	30 days, non-rotating
Scope	`mcp`
PKCE method	`S256`, mandatory

A client that honours expires_in refreshes the access token without a second sign-in. For the full OAuth parameter table and the stored connection fields, read Connected Apps Management.

Which tools become available after you connect?

The RichAPI MCP server builds its tool list at run time. The server sends GET https://api.richapi.ai/api/v1/catalog, registers one tool for each catalog entry, and caches the list for 24 hours. RichAPI publishes a new endpoint, and the tool reaches your client after that cache expires. No tool list is compiled into the server.

A tool name equals the endpoint name. The catalog sets both name and api_path to the endpoint name. The enrich_profile endpoint becomes the enrich_profile tool. Examples:

Tool	What it does
`enrich_profile`	Returns LinkedIn profile data.
`enrich_company`	Returns LinkedIn company data.
`people_search`	Searches indexed LinkedIn profiles.
`post_keyword_search`	Searches LinkedIn posts by keyword.
`profile_activities`	Returns the activity feed of a profile.
`post_details`	Returns a post and its comments.
`email_finder`	Finds a professional email address.
`email_verifier`	Verifies the deliverability of an email address.
`phone_finder`	Finds a mobile phone number.

Two lists can disagree. This table states what each one is.

Source	What it holds	Status
The Available tools card on the MCP Setup page	A fixed list of 9 example tools	A sample. It does not come from the live catalog.
`GET /catalog` on the live API	The names that the MCP server registers	The shipped list.

Three names on the MCP Setup page do not match any endpoint. Use the real name in a prompt.

Name on the MCP Setup page	Real tool name
`find_emails`	`email_finder`
`verify_emails`	`email_verifier`
`check_usage`	No tool carries this name.

To read the live list from your client, ask the assistant to list its RichAPI tools.

Which prompts does the RichAPI MCP server provide?

The server registers seven prompts alongside the tools. A prompt is a ready-made instruction that chains several tools.

Prompt	What it does
`enrich-lead`	Enriches a LinkedIn profile, then finds the professional email address.
`research-company`	Returns firmographic data on a company and finds decision makers.
`find-prospects`	Searches LinkedIn profiles by title, industry, location, and company size.
`monitor-topic`	Searches LinkedIn posts about a topic and summarises the conversation.
`email-campaign-prep`	Finds and verifies emails for a list of people.
`waterfall-enrich-contact`	Enriches one contact from a LinkedIn URL, an email, or a name and domain.
`ai-classify-leads`	Scores or classifies prospects against a rubric with `ai_enrich`.

How much does an MCP connection cost?

CAUTION: An MCP tool call spends credits. A prompt that asks the assistant to enrich 500 profiles sends 500 tool calls and charges for all of them.

The connection itself costs nothing. A tool call costs the same number of credits as a direct API call to the same endpoint. The organization balance of the workspace that owns the API key on the consent screen pays. 1 credit costs $0.02 on the 1,000 and 5,000 credit packs, and less on larger packs.

Rule	Effect
Price parity	An MCP tool call and a direct API call to the same endpoint cost the same.
Who pays	The organization balance, through the workspace of the API key named on the consent screen.
Failed calls	A non-2xx response costs no credits.
Per-result endpoints	The charge follows the number of results returned, not the number requested.
Free endpoints	An endpoint priced at 0 credits stays free through MCP.

The enrich_profile tool costs 1 credit per call, or 2 credits when the call asks for social metrics.

Calls	Credits	Cost
100	100	$2.00
500	500	$10.00
1,000	1,000	$20.00

The credit price of each endpoint is stated in that endpoint's API Endpoints article. The Available tools card on the MCP Setup page prints its own credit labels, and some of them are out of date. Read the endpoint article for the price that RichAPI charges.

How to disconnect an MCP client

Open the Connected Apps page at /home/<account-slug>/connected-apps.
Find the connection under Active connections.
Click Disconnect.
Confirm the browser dialog.
Wait up to about one minute.

RichAPI caches the "not revoked" verdict for 60 seconds, so a tool call inside that window can still succeed. After the cache expires, the connection returns 403. RichAPI cannot re-enable a revoked connection. Authorize the client again to restore access. For the rename flow, the revoked list, and the stored fields, read Connected Apps Management.

CAUTION: A client that sends the RichAPI API key in an x-api-key header creates no connection row. Disconnect does not stop that client. Revoke its API key on the API Keys page instead.

How to fix a failed MCP connection

What you see	Cause	What to do
`No API key yet` on the consent screen	The workspace has no active API key.	Create a key on the API Keys page. The link returns you to the consent screen.
`Invalid authorization request`	The consent page opened without a valid MCP authorization request.	Return to the client and add the connector again.
`Authorization request expired or tampered with`	The signed request passed its 10-minute limit.	Return to the client and start the connection again.
`401` with `Missing or invalid credentials`	The client sent no bearer token, or the token expired.	Remove the server from the client, add it again, and click Allow.
`403` with the text that the connection was disconnected	A workspace member clicked Disconnect, or you authorized the same client again and the new connection replaced this one.	Add the connector again and click Allow.
A tool call fails, and the Connected Apps row says the API key no longer works	Somebody revoked or deleted the API key that the connection uses.	Disconnect the old row, then add the connector again and click Allow. The new connection uses the newest active key.
`403` with the text that the token matches no known connection	The bearer token points at a row that no longer exists.	Add the connector again and click Allow.
`code_challenge is required (PKCE mandatory)`	The client sent no PKCE challenge.	Use a client that supports OAuth 2.1 with PKCE.
`code_challenge_method must be S256`	The client sent `plain` instead of `S256`.	Use a client that supports PKCE `S256`.
`redirect_uri must be a valid http(s) or app callback URL`	The client sent an unsupported callback scheme.	Update the client to a build that registers a normal callback URL.
The client lists no RichAPI tool	The catalog fetch failed, so the server registered no tools.	Wait, then restart the client. If the list stays empty, contact support.
The client lists an old tool set	The 24-hour catalog cache is not yet expired.	Wait for the cache to expire, then restart the client.
A tool call returns `402`	The organization has no credits, or the workspace reached its monthly spend limit.	Buy credits on the Plans & Billing page, or ask the organization owner to raise the spend limit.
A tool call returns `429`	Too many requests.	Wait, then send the prompt again.
The client works after a disconnect	The 60-second revocation cache is not yet expired.	Wait one minute, then send another tool call.
The client asks for a new sign-in every hour	The client does not use the refresh token.	Update the client. The access token lasts 1 hour and the refresh token lasts 30 days.

Frequently asked questions

What is the RichAPI MCP server URL?

The RichAPI MCP server URL is https://mcp.richapi.ai/mcp. The same URL works in Claude, ChatGPT, Claude Code, Cursor, Windsurf, Zed, and any other client that supports the remote HTTP transport.

How do I add RichAPI to Claude Code?

Run claude mcp add --transport http richapi https://mcp.richapi.ai/mcp in a terminal. Claude Code opens RichAPI in your browser, and the tools become available after you sign in and click Allow.

Do I need an API key to connect an MCP client to RichAPI?

Yes. The workspace must hold an active RichAPI API key before the consent screen approves the connection. You never paste that key into the AI client. The connection uses the newest active key of the workspace, and the consent screen shows its prefix.

Does my AI client receive my RichAPI API key?

No. The client receives an OAuth bearer token. The token works with the access of that API key, but it does not contain the key. If somebody revokes the key, the connection stops too.

How much does an MCP tool call cost?

An MCP tool call costs the same number of credits as a direct API call to the same endpoint. 1 credit costs $0.02 on the 1,000 and 5,000 credit packs, and less on larger packs. The enrich_profile tool costs 1 credit per call. A failed call costs no credits.

Which tools does the RichAPI MCP server expose?

The server exposes one tool for every public endpoint that GET /catalog returns, and the tool name equals the endpoint name. Ask your AI assistant to list its RichAPI tools to read the live set.

Why does my client show a tool that no longer exists?

The MCP server caches the tool catalog for 24 hours. A tool that RichAPI removed stays visible until that cache expires and the client reconnects.

Can two people in one workspace connect their own AI clients?

Yes. Each member gets their own connection, and every connection bills the same workspace. If the same member authorizes the same client again, the new connection replaces the old one. Every member of the workspace can see and disconnect every connection.

Next: Connected Apps Management

Connecting Model Context Protocol (MCP)