
Cygnix SEO
io.github.cygnixlabs-cmdPublished by GitHub account cygnixlabs-cmdv1.0.0Updated Nov 4, 2026
No-API-key SEO tools: keyword clustering, search intent, cannibalization, meta checks, briefs.
Overview
Local, no-API-key SEO toolkit that lets an assistant cluster keywords, classify search intent, find cannibalization, check titles and metas, and draft content…
- What you can do
- Cluster a keyword list into topical clusters with a pillar keyword per cluster
- Label keywords by search intent (informational, commercial, transactional, navigational)
- Read a Google Search Console query-plus-page CSV and flag queries where pages compete, ranked with a suggested fix
- Score title tags and meta descriptions for length, truncation, keyword placement and CTR hooks
- Build a content brief with intent, title options, meta draft, slug, H2 outline and checklist
- When to use it
- Useful when you are doing keyword research, on-page SEO review or content planning and want a fast, deterministic first pass on your own keyword lists, titles or Search Console exports without signing up for an SEO platform.
- Requirements
- Node.js 18 or later; runs as a local stdio process, typically launched with npx. No accounts, API keys, environment variables or headers are declared. Cannibalization checks need a Search Console export where each row is a query-page pair.
Installation
In SourceWeft
- Open Cygnix SEO in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Cygnix SEO MCP: free SEO tools for Claude, Cursor & any MCP client
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.
Install
Requires Node.js 18+.
Claude Desktop
Edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):
Restart Claude Desktop.
Cursor
Settings → MCP → Add new server, or add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
Claude Code
Other clients (VS Code, Windsurf, Cline, Zed…)
Any MCP client that supports stdio: command npx, args -y cygnix-seo-mcp.
From source
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)
GSC input contract (cannibalization): each CSV row must be one query–page pair, with columns for query, page, clicks, impressions and position (header names are matched loosely). Separate Queries-only and Pages-only aggregate exports cannot be joined to recover those pairs. Example file: gsc-query-page.csv.
How to get that export:
- Prefer Looker Studio or the Search Console API, which can export query + page together.
- In the Search Console UI, dimensions are one at a time (Google’s filtering docs; export docs). Manual route for selected-query coverage (not a full site-wide export): open Performance → Search results → click one query to filter → switch the dimension to Pages → Export → add that exact query as a column on every row. Repeat for the queries you care about, keep date/search-type filters the same, and append the rows.
More Cygnix SEO tools
Free agent skills (npx skills add cygnixlabs-cmd/cygnix-seo-skills), pay-per-use Apify actors for full-site SEO + AEO/GEO audits, and the rest of the toolkit: Cygnix Labs tool directory.
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.
Paid pro tools
Need more than the free tools? These run in the cloud on Apify. You pay per result, and Claude, ChatGPT and Cursor agents can call them through the Apify MCP server:
Prices checked 2026-10-29 against each Actor's live Apify Store pricing page (e.g. Keyword Cannibalization Finder pricing) and the public Apify API (api.apify.com/v2/acts/cygnix_labs~<actor>). The Apify Store page is the source of truth if they ever differ.
Full agent skills (Claude Code / Cursor SKILL.md packs): Cygnix Labs on Agensi
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.
- 🔎 SEO Toolkit Vol. 1: Keyword Research → Content Refresh (Agensi)
- 🛠️ SEO Toolkit Vol. 2: Audit & Fix Pack (Agensi)
- 📦 SEO Operator Bundle (Gumroad)
- 👤 All Cygnix Labs skills on Agensi · Gumroad store · Medium · X
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
Source: README.md at commit ec1a6af
Tools
0Version history
1- v1.0.0LatestOct 14, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts