Back to Directory/Search & Knowledge

Cygnix SEO

No-API-key SEO tools: keyword clustering, search intent, cannibalization, meta checks, briefs.

Search & KnowledgeTypeScriptv1.0.0

Cygnix SEO MCP: free SEO tools for Claude, Cursor & any MCP client

npm License: MIT

5 no-API-key SEO tools that work on your data: paste keywords, a Google Search Console export or your titles, and get clusters, intent, cannibalization fixes, CTR checks and content briefs. Everything is deterministic and runs locally. No accounts, no tracking, and no made-up search volumes.

Built by Cygnix Labs.

ToolWhat it does
cluster_keywordsGroups a keyword list into topical clusters and picks a pillar keyword per cluster (one cluster ≈ one page)
classify_search_intentLabels keywords informational / commercial / transactional / navigational, with the matching signal
find_keyword_cannibalizationReads GSC CSV (Query + Page) and flags queries where your own pages compete, ranked HIGH/MEDIUM/LOW, with a fix
check_title_metaScores title tags and meta descriptions (0–100): char + pixel truncation, keyword placement, CTR hooks
content_brief_outlineBuilds a brief from your keyword: intent, title options, meta draft, slug, H2 outline, questions to answer, on-page checklist

Install

Requires Node.js 18+.

Claude Desktop

Edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):

{
  "mcpServers": {
    "cygnix-seo": { "command": "npx", "args": ["-y", "cygnix-seo-mcp"] }
  }
}

Restart Claude Desktop.

Cursor

Settings → MCP → Add new server, or add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "cygnix-seo": { "command": "npx", "args": ["-y", "cygnix-seo-mcp"] }
  }
}

Claude Code

claude mcp add cygnix-seo -- npx -y cygnix-seo-mcp

Other clients (VS Code, Windsurf, Cline, Zed…)

Any MCP client that supports stdio: command npx, args -y cygnix-seo-mcp.

From source

git clone https://github.com/cygnixlabs-cmd/cygnix-seo-mcp && cd cygnix-seo-mcp
npm install && npm test
node dist/index.js

Example prompts

  • "Cluster these 80 keywords and tell me which page each cluster should target:" (paste list)
  • "Classify the search intent of these keywords and flag the commercial ones."
  • "Here is my GSC export (query + page). Find keyword cannibalization and tell me what to merge."
  • "Check the titles and meta descriptions for these 10 URLs against their target keywords."
  • "Write a content brief for 'technical seo audit' using these related keywords: …"

Example output (cannibalization)

## [HIGH] "seo audit checklist" (2 pages, #2 page share 38%)
| Page | Clicks | Impr | Avg pos |
| https://site.com/a | 30 | 1000 | 4.2 |
| https://site.com/b | 5 | 600 | 9.1 |
Action: Pick https://site.com/a as canonical target; merge/301 or de-optimize the others...

Getting GSC data: Search Console → Performance → Search results → add the Page dimension alongside Query (or use the Looker Studio / API export) → Export CSV → paste the text.

Honest limits

  • Intent and clustering are rule-based/lexical, so treat them as a fast first pass and confirm with the live SERP.
  • Title pixel widths are approximations of Google's SERP rendering.
  • No tool estimates search volume or difficulty. Use your own data source for that.

Want the full workflow?

These tools are the free starter layer of the Cygnix SEO Toolkit: full agent skills, prompts and sheets for keyword research → briefs → audits → content refresh.

Keywords

MCP server, Model Context Protocol, SEO MCP, keyword research, keyword clustering, search intent classifier, keyword cannibalization, Google Search Console, title tag checker, meta description length, CTR optimization, content brief generator, Claude SEO, Cursor SEO, AI SEO tools, free SEO tools, no API key.

License

MIT © Cygnix Labs

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y cygnix-seo-mcp

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json
{
  "mcpServers": {
    "io-github-cygnixlabs-cmd-cygnix-seo-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "cygnix-seo-mcp"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

cygnix-seo-mcpnpm

Compatible MCP Clients

Cygnix SEO works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More