Use BacklinkGPT from ChatGPT, Claude, and other AI tools (MCP)

BacklinkGPT ships a remote MCP server. Any assistant that speaks MCP can read your pipeline, review and approve drafts, record wins, and change the agent's settings, with the same permissions you have in the app.

Server URL: https://backlinkgpt.com/api/mcp

Connect with OAuth

Connections use OAuth by default. You sign in with your normal BacklinkGPT account, pick the workspace the client may use, and approve the access. No API key is needed, and nothing is pasted into config files.

Each connection is bound to exactly one workspace. To use another workspace, connect again and pick it on the consent screen.

ChatGPT

Open Settings → Apps & Connectors, turn on Developer mode under Advanced settings if you do not see a Create button, then create a connector with the server URL above and OAuth as the authentication. Leave the client ID and secret empty; BacklinkGPT registers the client automatically. Once the BacklinkGPT plugin is listed in the ChatGPT directory, installing it from there does the same thing.

Claude (web and desktop)

Open Settings → Connectors → Add custom connector, name it BacklinkGPT, paste the server URL, and leave the advanced OAuth fields empty. Click Connect when Claude prompts you and approve the access in the browser.

Claude Code

claude mcp add --transport http backlinkgpt https://backlinkgpt.com/api/mcp

Then run /mcp inside Claude Code, pick backlinkgpt, and complete the sign-in.

Codex

Add the server to ~/.codex/config.toml and log in:

[mcp_servers.backlinkgpt]
url = "https://backlinkgpt.com/api/mcp"

codex mcp login backlinkgpt

If the login fails with Authorization server response missing required issuer, update the Codex CLI (the fix shipped in 0.147.0).

Cursor

Use the one-click install on the Agents page, or add the server to .cursor/mcp.json (project) or the global Cursor MCP config:

{
  "mcpServers": {
    "backlinkgpt": {
      "url": "https://backlinkgpt.com/api/mcp"
    }
  }
}

Cursor starts the OAuth flow the first time the server is used.

VS Code

Use the one-click install on the Agents page, or add the server to .vscode/mcp.json (workspace) or your user MCP configuration:

{
  "servers": {
    "backlinkgpt": {
      "type": "http",
      "url": "https://backlinkgpt.com/api/mcp"
    }
  }
}

Raycast and other clients

Raycast has a one-click link in the app sidebar under MCP Server. Any other client can point at the server URL as a remote HTTP server with OAuth. Clients without built-in OAuth support can bridge through npx mcp-remote https://backlinkgpt.com/api/mcp.

Connect with an API key

For agents that run unattended, or for one agent that has to switch between several workspaces, use a workspace API key instead of OAuth. Owners and admins create keys under API → API Keys; a key is bound to the workspace it was created in and acts as the member who created it.

Send the key as Authorization: Bearer <key> or as the x-api-key header. Clients that support custom headers take it in the server config, for example in Cursor:

{
  "mcpServers": {
    "backlinkgpt": {
      "url": "https://backlinkgpt.com/api/mcp",
      "headers": { "x-api-key": "<your-api-key>" }
    }
  }
}

The same key authenticates the REST API. Pause or delete it from the API Keys page when the agent retires.

What the assistant can do

The server exposes the same tools the in-app Copilot uses:

• Status and results: agent status, outreach KPIs and history, engagements, blocked engagements, backlinks won.
• Prospects: search the ledger, see recent keeps and the agent's verdicts, settle parked prospects, research or import pages you vouch for, run the nightly sourcing early.
• Inbox: list what needs you, read full threads, approve, reject, or redraft outreach and replies, triage replies, record a won link.
• Playbook: keywords, target pages, standing rules, competitor policy, exclusions, cadence and pacing, senders, site positioning.

Safety rails

• Sending needs your word. Approving a draft sends a real message from your connected account. Well-behaved assistants show you the draft and ask first; the tool is marked destructive so clients confirm before calling it.
• Credits are quoted before they are spent. Tools that spend prospecting credits (researching a page, importing prospects, running sourcing early) return an estimate and your remaining balance first and only spend on an explicit confirmation.
• Your permissions, your workspace. Every call runs as you (or as the member who created the API key), inside the workspace the connection is bound to. Membership is re-checked on every call, so removing a member cuts their connections and keys immediately.
• A live plan is required. The server answers only for workspaces with an active plan or trial, whichever credential is used.

Revoke access

Under Settings → Security → MCP Clients you see every OAuth-connected client with the workspace it is bound to. Remove revokes that client's access immediately. Sign out all clients in the sidebar's MCP menu revokes every connection at once. API keys are paused or deleted under API → API Keys.

For developers

• Discovery: https://backlinkgpt.com/.well-known/oauth-authorization-server and https://backlinkgpt.com/.well-known/oauth-protected-resource. Dynamic client registration is supported.
• Scopes: mcp:read, mcp:write, mcp:credits. OAuth connections and API keys currently receive all three.
• The server publishes a guide for assistants as the MCP resource mcp://backlinkgpt.com/docs (tool groups, rules of engagement, data model notes).
• The REST API reference lives at /api/v1/docs; see the API docs for keys and authentication.