Skip to main content
The MCP server says what a connection can read. A client connects in one of two ways:
  • Sign in and approve. ChatGPT, claude.ai and Claude Desktop’s connector settings connect this way. They need no key.
  • An API key. Claude Code, Cursor and other clients that send a header connect this way.
The endpoint is https://mcp.fullreach.ai for both.

Sign in and approve

1

Add the server in the assistant

Add a custom connector with the URL https://mcp.fullreach.ai. Leave the client ID and secret empty.
  • ChatGPT: enable developer mode in the settings, then add the connector.
  • claude.ai and Claude Desktop: add a custom connector in the connector settings.
2

Sign in to FullReach AI

The assistant opens a FullReach AI page in your browser. Sign in there with your company email, Google or Microsoft. After you sign in, the browser shows the page again.
3

Read the request, then approve

The page shows where the assistant’s answers go, such as chatgpt.com. Check that address. Then choose what the connection may read: every project, or one project. If the assistant asks for write access, the page offers a box for it, and the box starts empty. Select Approve.
The browser then returns to the assistant, which can call the tools.

What the page checks

  • Only an admin approves. A member sees who to ask, and may deny the request.
  • The request works in the browser the assistant opened. A link to the page that somebody forwards does not work in another browser.
  • The destination comes first. An app names itself, but the page leads with the address its answers go to. If the name and the address do not match, the page warns you. Deny unless you added that app yourself.
  • An organization with no project cannot connect. Start a trial first.

How a connection ends

Settings, Organization, Connections lists each connection. A row names the assistant, where its answers go, what it reads and whether it also writes. It also names who approved it, and when the assistant last used it. A connection belongs to the admin who approved it. It stops working when:
  • an admin revokes it on that card. The card asks first, and the next call fails at once.
  • that admin leaves the organization, another admin removes them, or they stop being an admin.
  • the organization is deleted.
  • the assistant stays unused until its sign-in expires. Connect it again from the assistant.

An API key

  • The endpoint: https://mcp.fullreach.ai. Settings, Organization, API keys shows it with a Copy button.
  • An API key. An admin creates it on the same card. Name it after the client, such as “Cursor”. Under Access, choose Read and write only for a key that needs write access. The key shows once, so copy it before you close the panel. It starts with fr_.
When the organization runs more than one project, choose which projects the key reaches: every project, or one. A key for every project needs the tools’ project argument. The assistant finds the ids with list_projects. A connection that reads every project works the same way. The server takes the key as a bearer token: Authorization: Bearer fr_…. Treat the key as a password. Anybody who holds it can read what the organization measured. A key belongs to the organization, not to a person, and works until an admin revokes it.

Claude Code

Run this in a terminal, with your key in place of fr_…:
Then run /mcp in Claude Code to check that fullreach is connected.

Claude Desktop with a key

Claude Desktop’s connector settings sign in, as above. To use a key instead, Claude Desktop reaches the server through mcp-remote, a small bridge that runs on Node.js.
  1. Install Node.js, if it is not installed.
  2. In Claude Desktop, open Settings, Developer, Edit Config.
  3. Add the server to claude_desktop_config.json, with your key in place of fr_…:
  1. Quit Claude Desktop completely and open it again.
The key sits in env, not in args, because Claude Desktop on Windows breaks an argument that holds a space.

Cursor

Add the server to Cursor’s mcp.json, with your key in place of fr_…. The file is ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside one project:

Other clients

A client can connect when it speaks MCP over Streamable HTTP, and either signs in with OAuth or sends an Authorization header. The server takes one JSON-RPC message per request, and it opens no event stream.

Write access

A key or a connection with write access also gets the write tools. With them, an assistant can add, pause, resume and reword prompts, and set the markets that a prompt runs in. It can rename topics and move prompts between them. It can also track or dismiss suggested questions, add competitors, change their spellings and stop monitoring them. These are the edits that a member makes in the dashboard, with the same limits. No write tool changes a plan, a person or any other setting.
  • An admin grants it, once. For a connection, the assistant asks for it, and the admin selects the box on the approval page. For a key, the admin chooses Read and write under Access when creating the key. To change it later, create a new key or approve a new connection, and revoke the old one.
  • Without it, a credential only reads. Its assistant does not see the write tools. A call to one returns a sentence that says how to get write access.
  • The assistant asks before each write. Each write tool says so, and the project_tune_up prompt proposes changes and waits for a yes.
  • A call is all or nothing. If the server refuses one item, it writes nothing.

Add the manual beside it

This manual has its own MCP server: https://docs.fullreach.ai/mcp. Add it as a second server in the same client. It needs no key and no sign-in. The assistant can then find how FullReach AI counts each number, rather than guess. Claude Code adds it with:
A client without MCP can read the manual’s page index at https://docs.fullreach.ai/llms.txt.

Limits

  • Plan limits states how many tool calls an organization may make a minute. Keys and connections share it. Every answer carries the rate-limit headers, so a client can pace itself.
  • A key or a connection reaches only this organization. It never reaches the dashboard. Without write access, it cannot change anything.