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_..."
For AI assistants
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.
Fastest setup
Open the AI assistant page in your dashboard. It creates your API key and puts it straight into a setup brief, so there is nothing to copy from Settings. Paste the brief into Claude, Codex or Cursor and the assistant connects itself, then checks your account.
The page also tells you what is ready: whether a card is saved for booking, and how many campaigns your assistant can report on. No campaigns yet? Your assistant can open a sample campaign to show you the data.
New accounts land straight back on the brief after signing up. Prefer to copy it here instead? This version has no key in it, so your assistant will ask you for one.
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 get_account to check it works and tell me what it says.
Tools: get_account, list_packages, list_clients, list_campaigns, get_campaign, get_sample_campaign, book_campaign.
get_sample_campaign is an example from SEO Backlinks' own campaigns, not my results.
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
Your assistant needs an API key from your SEO Backlinks dashboard. It takes a minute.
Or skip these steps: the AI assistant page creates a key and puts it in the brief for you.
Treat the key like a password. Anyone who has it can see your campaigns and order on your account.
Manual setup
Use the snippet for your app and replace cr_live_... with your API key.
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 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
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_..." }
}
}
}
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
Ask in plain language and your assistant picks the right tool.
get_accountWho the key belongs to, whether a card is saved so campaigns can be booked, and how many campaigns the account has.
list_packagesThe packages you can order, with price, billing and the minimum number of placements.
list_clientsThe client websites on your account.
list_campaignsEvery campaign, its status and the links it has delivered so far.
get_campaignEach link a campaign has delivered: article URL, linked page, anchor text, domain authority and the date it landed.
get_sample_campaignOne of our own campaigns with its latest delivered links, so you can see the data before your first campaign. Always marked as a sample, never your results.
book_campaignOrders a campaign. The first call returns a quote only, and it charges the card on file only after you approve the quoted total.
Questions
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.
No. Booking returns a quote first and only charges the card on your account when it is called again with the quote you approved. Monthly packages renew monthly until canceled.
Yes. Connect your assistant and ask for the sample campaign: it shows one of our own campaigns with the links it delivered, so you can see what your assistant will report. Booking needs a card saved on your account.
Claude Code, Claude Desktop, Codex, Cursor and any MCP client that supports Streamable HTTP with a custom Authorization header.
Yes, and it uses the same key. See the API documentation.
Full documentation
The dashboard docs cover the MCP server and the REST API that shares your key.