Skip to main content
Surnex exposes an MCP (Model Context Protocol) server at https://api.surnex.io/mcp. Connect it to an AI client and the agent can query and act on your SEO data directly — reading rankings, running audits, adding keywords — without you copying figures into a chat.

​
What it gives an agent

88 tools across 14 areas, covering essentially everything in the dashboard: Some tools go beyond the dashboard — generate_meta_tags and generate_content_brief have no UI equivalent.

​
Reads and writes

Most tools read. Some change your account: create_project, delete_project, add_tracked_keywords, remove_tracked_keywords, add_competitor, remove_competitor, add_geo_topics, remove_geo_topics, save_keywords, delete_saved_keywords, start_site_audit, refresh_backlinks, and trigger_web_vitals_check.
delete_project permanently destroys a project and all its history, and an agent can call it — subject to your role, since the token acts as you. Several tools also consume plan quota: start_site_audit, refresh_backlinks, and the research tools all draw on your allowance. Configure your client to confirm before running tools if it supports that.
The consent screen states the grant before you approve it, including that audits and research cost money against your plan. Tools are also annotated — read-only, destructive, idempotent — so a client that supports it can confirm only the calls that warrant it. delete_project is the one marked destructive.

​
What it’s good for

The value is in the questions that would otherwise take several pages and a spreadsheet:
  • “Which keywords dropped out of the top 10 this month, and what’s the search volume we lost?”
  • “Compare our backlink profile to these three competitors and tell me the best link targets.”
  • “Read our latest audit and write a prioritized fix list for the dev team.”
  • “We’re publishing about X — what should the page cover, and who currently owns that topic in AI answers?”
An agent can chain tools: pull the audit, cross-reference the affected pages against ranking data, and rank the fixes by traffic at risk. That’s the actual advantage over the dashboard.

​
Authentication

The server uses OAuth, not API keys. Your client sends you through a consent screen and receives a token that identifies you — so the agent inherits your role and reaches every organization you belong to. API keys are explicitly refused by this endpoint. See MCP authentication. Because a token can span several organizations, org-scoped tools take an optional organization argument. Belong to more than one and name none, and the call is refused with a list rather than resolved to a guess.

​
Getting started

Connect the server

Setup for Claude Code, Claude Desktop, Cursor, and Windsurf.

Authentication

The OAuth flow, the consent screen, and what an agent can reach.

Tools

The full inventory, and which ones write.

Playbooks

Prompt patterns that work.