Connect in 2 minutes
You need the server URL https://mcp.cygnixlabs.com/mcp and an API key. Get a free key if you don't have one yet.
Claude (web and desktop)
- Open Settings → Connectors and click Add custom connector.
- Name it Cygnix SEO and set the URL to
https://mcp.cygnixlabs.com/mcp. - Under Authentication choose Sign in now (OAuth). Claude opens a Cygnix page; paste your API key and click Approve.
If your organization has request headers instead: choose No sign-in, add headerAuthorizationwith valueBearer cyg_live_YOUR_KEY. - In a chat, enable the connector from the tools menu and ask: “Use Cygnix SEO to check AI-search readiness for https://example.com”.
ChatGPT (web)
- Turn on Developer mode in Settings (Apps / Security → Developer mode; plan and workspace permissions apply).
- Open Apps, click Create app (or Add custom MCP server).
- Server URL:
https://mcp.cygnixlabs.com/mcp. Authentication: OAuth. ChatGPT registers itself automatically. - When the Cygnix page opens, paste your API key and approve. Then in a chat type @Cygnix SEO and ask, for example, “cluster these keywords: …”.
ChatGPT desktop and Codex can also send the key as a bearer token from an environment variable instead of OAuth. Prices and upgrade CTAs are hidden inside ChatGPT, per OpenAI's rules.
Cursor
Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project), then reload MCP servers in Settings → MCP.
{
"mcpServers": {
"cygnix-seo": {
"url": "https://mcp.cygnixlabs.com/mcp",
"headers": { "Authorization": "Bearer cyg_live_YOUR_KEY" }
}
}
}Claude Code
One command (HTTP transport):
claude mcp add --transport http cygnix-seo https://mcp.cygnixlabs.com/mcp \ --header "Authorization: Bearer cyg_live_YOUR_KEY"
Add --scope user to use it in every project. Check with claude mcp list, then run /mcp inside Claude Code.
VS Code (Copilot agent mode)
Create .vscode/mcp.json. VS Code prompts for the key once and stores it securely:
{
"inputs": [
{ "type": "promptString", "id": "cygnix-key", "description": "Cygnix API key", "password": true }
],
"servers": {
"cygnix-seo": {
"type": "http",
"url": "https://mcp.cygnixlabs.com/mcp",
"headers": { "Authorization": "Bearer ${input:cygnix-key}" }
}
}
}Open the Chat view, switch to Agent mode and enable the Cygnix tools.
Any MCP client or the API
Transport: Streamable HTTP (stateless, JSON responses). Auth: Authorization: Bearer cyg_live_YOUR_KEY or X-Api-Key, or OAuth 2.1 (metadata at /.well-known/oauth-authorization-server, dynamic client registration, PKCE S256).
curl -s https://mcp.cygnixlabs.com/mcp \
-H "Authorization: Bearer cyg_live_YOUR_KEY" -H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"account_status","arguments":{}}}'
Prefer local? npx -y cygnix-seo-mcp runs the five core tools over stdio for free.
Google Search Console
Search Console connect is rolling out as early access and is not yet available to every account (Google's consent screen is still in testing). If you have access, open your account and click Connect Google (read-only, revocable any time). Then ask: “list my Search Console sites”, “compare the last 28 days to the previous 28”, or “find quick wins”. You can always paste a Search Console CSV into find_keyword_cannibalization.
Try these prompts
- “Here is my Search Console export (CSV). Find keyword cannibalization and tell me which pages to merge.”
- “Can ChatGPT and Perplexity cite https://example.com/pricing? Fix what blocks them.”
- “Audit https://example.com/blog/post for on-page SEO, schema, redirects and Core Web Vitals.”
- “Check our llms.txt and write a better one.”
- “Did any Google algorithm update line up with a traffic drop in May?”
- “Turn this audit into a branded PDF for Client Co.” (Agency)