> ## Agent Instructions
>
> Base URL: https://api.anysite.io
> Authentication: send the `access-token` header. Do NOT use `Authorization: Bearer`.
> Full endpoint catalog: https://app.anysite.io/docs
# Connect a client

Connect Claude, Cursor, Codex, ChatGPT, n8n, Make, Clay or Grok to the Anysite MCP server.

Goal: add the Anysite MCP server to your AI client and confirm its tools are available.

Pick your client below. The box at the top of each tab holds your personal URL, command or install button
(sign in to see it); the steps under it happen inside the client. What the auth modes mean:
[MCP server](/docs/mcp/overview#authentication).

#### Claude.ai

> ACTION FOR THE HUMAN: open https://app.anysite.io/mcp?client=claude-ai, sign in, and follow the Claude.ai instructions there. An agent cannot obtain the key or URL itself.

1. In Claude, open **Settings → Connectors** and choose **Add custom connector**.
2. Paste the MCP URL from the box above and save.
3. Click **Connect**. An Anysite page opens: pick the plan under **Use credits from** and click **Allow access**.
4. Start a new chat and ask: `What tools do you have from Anysite?`

#### Claude Desktop

> ACTION FOR THE HUMAN: open https://app.anysite.io/mcp?client=claude-desktop, sign in, and follow the Claude Desktop instructions there. An agent cannot obtain the key or URL itself.

1. In Claude Desktop, open **Settings → Connectors** and choose **Add Custom Connector**.
2. Paste the MCP URL from the box above and add the connector.
3. Click **Connect**. Your browser opens the Anysite consent page: pick the plan under **Use credits from** and click **Allow access**.
4. If Claude does not reach for the Anysite tools on its own, set Claude's **Tool access** option to **Tools already loaded**, so the tools are always in context instead of being looked up by name.
5. Start a new chat and ask: `What tools do you have from Anysite?`

#### Claude Code

> ACTION FOR THE HUMAN: open https://app.anysite.io/mcp?client=claude-code, sign in, and follow the Claude Code instructions there. An agent cannot obtain the key or URL itself.

1. Run the command from the box above in your terminal. It registers the server under the name `anysite`, with your key in the URL.
2. Run `claude mcp list` and check that `anysite` is listed as connected.
3. Start a new Claude Code session and ask: `What tools do you have from Anysite?`

#### Cursor

> ACTION FOR THE HUMAN: open https://app.anysite.io/mcp?client=cursor, sign in, and follow the Cursor instructions there. An agent cannot obtain the key or URL itself.

1. Click **Add to Cursor** in the box above. Cursor opens with the `anysite` server prefilled, authenticated with your key in an `Authorization` header.
2. Confirm the installation in Cursor.
3. Restart Cursor.
4. In an agent chat, ask: `What tools do you have from Anysite?`

#### Codex

> ACTION FOR THE HUMAN: open https://app.anysite.io/mcp?client=codex, sign in, and follow the Codex instructions there. An agent cannot obtain the key or URL itself.

1. Run the command from the box above in your terminal.
2. Start a new Codex session.
3. If Codex opens a browser window, sign in to Anysite and click **Allow access**.
4. Ask: `What tools do you have from Anysite?`

#### ChatGPT

> ACTION FOR THE HUMAN: open https://app.anysite.io/mcp?client=chatgpt, sign in, and follow the ChatGPT instructions there. An agent cannot obtain the key or URL itself.

1. In ChatGPT, add a custom MCP connector and paste the MCP URL from the box above.
2. Connect it. The Anysite consent page opens: pick the plan under **Use credits from** and click **Allow access**.
3. In a new chat with the connector enabled, ask: `What tools do you have from Anysite?`

#### n8n

> ACTION FOR THE HUMAN: open https://app.anysite.io/mcp?client=n8n, sign in, and follow the n8n instructions there. An agent cannot obtain the key or URL itself.

1. In your workflow, open the **AI Agent** node and add the **MCP Client Tool** to it.
2. Paste the Direct URL from the box above into the endpoint field.
3. Set the transport to **HTTP Streamable** and authentication to **None** — the key is already in the URL.
4. Run the workflow with a prompt such as `List the tools you have from Anysite` and check the agent's tool calls.

#### Make

> ACTION FOR THE HUMAN: open https://app.anysite.io/mcp?client=make, sign in, and follow the Make instructions there. An agent cannot obtain the key or URL itself.

1. In Make, open **AI Agents** and select or create an agent.
2. In the agent's **MCP** section click **Add**, then choose **New MCP server** in the connection dialog.
3. Paste the Direct URL from the box above as the server URL. Leave the API key / access token field empty — the key is already in the URL.
4. Save the connection and ask the agent: `What tools do you have from Anysite?`

#### Clay

> ACTION FOR THE HUMAN: open https://app.anysite.io/mcp?client=clay, sign in, and follow the Clay instructions there. An agent cannot obtain the key or URL itself.

1. In Clay, open **Settings → Tools** and click **Add custom MCP server**.
2. Name the connection, paste the Direct URL from the box above as the MCP URL, and leave the MCP API key empty.
3. Save, and make sure the new server's toggle is on.
4. Use it from a Clay AI enrichment column, for example: `Use Anysite to get the LinkedIn profile for {LinkedIn URL}`.

Clay can also call the REST API directly from its **HTTP API** enrichment instead of MCP: send
`POST https://api.anysite.io/api/<endpoint>` with your key in the `access-token` header (not
`Authorization: Bearer`). Request format: [Quickstart](/docs/quickstart) and [Authentication](/docs/authentication);
endpoints and parameters: [API reference](/docs/api).

#### Grok

> ACTION FOR THE HUMAN: open https://app.anysite.io/mcp?client=grok, sign in, and follow the Grok instructions there. An agent cannot obtain the key or URL itself.

1. In Grok, open **Skills and Connectors**, switch to the **Connectors** tab and click **New Connector → Custom**.
2. Enter the name `Anysite`, paste the MCP URL from the box above as the server URL, and click **Add Connector**.
3. Click **Connect**. In the Anysite pop-up pick the plan under **Use credits from** and click **Allow access**. If Grok shows "Connection failed", your browser blocked the pop-up: allow pop-ups for grok.com and click **Connect** again.
4. Open a new conversation and ask: `What tools do you have from Anysite?`

## Verify

The client lists `discover`, `execute`, `get_page`, `query_cache`, `merge_data`, `export_data` and
`search_requests`. The `crm_*` tools appear as well once the CRM integration is enabled
([CRM tools](/docs/mcp/crm)). Then try a real request, for example
`Use Anysite to find the LinkedIn profile of the CEO of Anthropic`: the client should call `discover` and then `execute`.

## Clients without HTTP transport

#### stdio bridge (npx @anysiteio/mcp)

Use this only if your client cannot connect to an HTTP MCP server. The npm package `@anysiteio/mcp` runs
locally over stdio and forwards every request to `https://mcp.anysite.io/mcp` with your key; the tools
are the same as on the hosted server.

```json
{
  "mcpServers": {
    "anysite": {
      "command": "npx",
      "args": ["-y", "@anysiteio/mcp"],
      "env": {
        "ANYSITE_ACCESS_TOKEN": "YOUR_API_KEY"
      }
    }
  }
}
```

> ACTION FOR THE HUMAN: copy your API key at https://app.anysite.io/billing — an agent cannot obtain it.

`ANYSITE_ACCESS_TOKEN` is the only required variable. `ANYSITE_MCP_URL` overrides the server URL and is
not needed for normal use.

The variable was renamed. A config written before the rename sets the old name and stops working —
replace that name with `ANYSITE_ACCESS_TOKEN`; the key value itself is unchanged.

## Troubleshooting

| What you see | Cause and fix |
|---|---|
| `401` `Authentication required. Include Authorization: Bearer <token> header.` | The client sent no key: the Direct URL was cut before `?api_key=`, or the header is missing. Copy the URL or config again from the MCP page. |
| `Active subscription required. Please subscribe first.` | The account has no active plan. Finish setup or choose a plan, then connect again. |
| `429` `You've reached your 5-hour usage limit…` (or weekly) | An MCP plan window is used up. Check usage on the MCP page and wait for the reset or change the plan. |
| The Direct URL or the key on the MCP page stays on "Loading…" | Not a key or billing problem: that client cannot use the Direct URL. Connect it with the OAuth URL from the same page instead. |
| A tool call fails once with a `502`, a proxy error or a timeout | Transient. Ask the client to run the same request again; if every call fails, check the plan and the connection first. |
| An OAuth client that worked stops authenticating | OAuth access lasts 30 days. Reconnect the connector and allow access again. |
| No `crm_*` tools | The CRM integration is off. Enable it in your profile, then refresh the client's tool list; the change reaches the server within a minute. |

> ACTION FOR THE HUMAN: open https://app.anysite.io/mcp (Open MCP integration).