For AI assistants

SEO Backlinks MCP server

Connect your AI assistant to your SEO Backlinks account to see your packages, order campaigns for your clients and track every link each campaign delivers, from Claude, Codex, Cursor or any MCP client.

Get your API key

Fastest setup

Paste one brief into your assistant.

Copy the setup brief and paste it into Claude, Codex or Cursor. The assistant connects itself to the SEO Backlinks MCP server and asks you for your API key, then runs two read-only tools to check the connection.

Setup brief

Set up the SEO Backlinks MCP server so you can order and track my link-building campaigns.

- MCP endpoint (Streamable HTTP): https://dashboard.seobacklinks.com/api/mcp
- Auth: my SEO Backlinks API key, sent as the header "Authorization: Bearer <key>". I create keys in my dashboard under Settings > API Keys (https://dashboard.seobacklinks.com/settings). Ask me for the key; never guess one.

How to add it, depending on which app you are:
- Claude Code: claude mcp add --scope user --transport http seo-backlinks https://dashboard.seobacklinks.com/api/mcp --header "Authorization: Bearer <key>"
- Codex: export SEO_BACKLINKS_API_KEY=<key>, then: codex mcp add seo-backlinks --url https://dashboard.seobacklinks.com/api/mcp --bearer-token-env-var SEO_BACKLINKS_API_KEY
- Cursor: in ~/.cursor/mcp.json add under "mcpServers": "seo-backlinks": { "url": "https://dashboard.seobacklinks.com/api/mcp", "headers": { "Authorization": "Bearer <key>" } }
- Claude Desktop: in claude_desktop_config.json add under "mcpServers": "seo-backlinks": { "command": "npx", "args": ["-y", "mcp-remote", "https://dashboard.seobacklinks.com/api/mcp", "--header", "Authorization:${AUTH_HEADER}"], "env": { "AUTH_HEADER": "Bearer <key>" } }, then restart Claude Desktop.

Once connected, call list_packages and list_campaigns to check it works.
Tools: list_packages, list_clients, list_campaigns, get_campaign, book_campaign.
book_campaign charges the card saved on my SEO Backlinks account: always show me its quote and wait for my yes before confirming.

Before you start

Get your API key.

Your assistant needs an API key from your SEO Backlinks dashboard. It takes a minute.

Sign in or create an accountSign in at dashboard.seobacklinks.com/login, or create an account at dashboard.seobacklinks.com/register.
Open Settings > API KeysGo to Settings in your dashboard and open the API Keys tab.
Create a key and copy itThe key is shown once, so copy it straight away and give it to your assistant when it asks.

Treat the key like a password. Anyone who has it can see your campaigns and order on your account.

Manual setup

Prefer to add the server yourself?

Use the snippet for your app and replace cr_live_... with your API key.

Claude Code

Run this in a terminal. --scope user makes the server available in every project.

claude mcp add --scope user --transport http seo-backlinks https://dashboard.seobacklinks.com/api/mcp \
  --header "Authorization: Bearer cr_live_..."

Codex

Codex reads the key from SEO_BACKLINKS_API_KEY, so set it in the shell profile you start Codex from.

export SEO_BACKLINKS_API_KEY=cr_live_...
codex mcp add seo-backlinks --url https://dashboard.seobacklinks.com/api/mcp --bearer-token-env-var SEO_BACKLINKS_API_KEY

Cursor

Add this to ~/.cursor/mcp.json. If the file already lists other servers, add the seo-backlinks entry inside the existing mcpServers block.

{
  "mcpServers": {
    "seo-backlinks": {
      "url": "https://dashboard.seobacklinks.com/api/mcp",
      "headers": { "Authorization": "Bearer cr_live_..." }
    }
  }
}

Claude Desktop

Add this to claude_desktop_config.json, then restart Claude Desktop. It connects through mcp-remote, so Node.js must be installed.

{
  "mcpServers": {
    "seo-backlinks": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://dashboard.seobacklinks.com/api/mcp",
               "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer cr_live_..." }
    }
  }
}

What it can do

Five tools for your campaigns.

Ask in plain language and your assistant picks the right tool.

list_packages
The packages you can order, with price, billing and the minimum number of placements.
list_clients
The client websites on your account.
list_campaigns
Every campaign, its status and the links it has delivered so far.
get_campaign
Each link a campaign has delivered: article URL, linked page, anchor text, domain authority and the date it landed.
book_campaign
Orders a campaign. The first call returns a quote only, and it charges the card on file only after you approve the quoted total.

Questions

Before you connect.

Is there a publisher list to choose from?

No. We run digital PR campaigns: our team develops stories and pitches them to journalists, so coverage is earned and the publications depend on the story and editorial interest. Each package guarantees a minimum number of placements.

Will my assistant spend money without asking?

No. Booking returns a quote first and only charges the card on your account when it is called again with the total you approved. Monthly packages renew monthly until canceled.

Which apps work?

Claude Code, Claude Desktop, Codex, Cursor and any MCP client that supports Streamable HTTP with a custom Authorization header.

Is there a REST API too?

Yes, and it uses the same key. See the API documentation.

Full documentation

Read the MCP reference.

The dashboard docs cover the MCP server and the REST API that shares your key.

Open the MCP docs