Claude SEO Skills
Server Details
Two open-source SEO skill packs (Claude SEO, Illyism SEO Skills) served read-only to any AI agent.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- NoteSupreme/claude-seo-skills-mcp
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 5 tools
The descriptions explicitly carve roles: get_ship_digest is the navigation map, list_ship_nodes is flat enumeration, search_nodes is ranked retrieval, and read_node fetches bodies. The one soft spot is get_blueprint_overview, which falls back to the exact same section map as get_ship_digest, so an agent can't always predict which call it needs. Overall boundaries are clear enough that misselection is unlikely.
All snake_case with a leading verb (get_, list_, read_, search_) and a resource noun, which is predictable. Minor deviation: read_node uses 'read' where the rest use 'get_' for single-item retrieval, and blueprint/ship/node are three different nouns for what is arguably the same object graph.
Five tools is tight and well-matched to a read-only knowledge-base navigation surface: orient, enumerate, search, read, and read authored prose. Each call earns its place and none looks like a redundant wrapper.
Retrieval is well covered (map, flat list, search, node body, prose overview), but the surface is strictly read-only with no create/update/append and no bulk multi-node fetch, so reading N nodes means N sequential read_node calls. Link traversal is only implicit via outbound_links on read_node, with no dedicated expand/resolve tool, which are notable gaps if the Ship is meant to be edited.
Available Tools
5 toolsclaudeseoskills__get_blueprint_overviewAInspect
Read the human-AUTHORED overview prose for the Ship (omit node_id) or for one section. Useful only where someone has written a summary; it is not the way to navigate — claudeseoskills__get_ship_digest is the map, call that first. When no summary has been written this falls back to the same section map claudeseoskills__get_ship_digest returns, drilled with { section_id } and paged with { cursor }.
Inputs: cursor, node_id, section_id.
claudeseoskills__get_ship_digestAInspect
Orient on this Ship — ALWAYS call this first. With no arguments it returns the section MAP and nothing else: every top-level section with its description and child_count, which is small and cheap even on a Ship of hundreds of nodes. Then pass { section_id } to list one section's direct children, and claudeseoskills__read_node for the ones worth reading. A large section arrives in pages — continue it with { cursor }.
Inputs: cursor, section_id.
claudeseoskills__list_ship_nodesAInspect
List every node: node_id, title, parent_id, node_type, plus type/description/tags/resource when set. No bodies. This is a flat list of the WHOLE Ship — on a large one it is long and arrives in pages, so pass { cursor } to continue. To navigate rather than enumerate, use claudeseoskills__get_ship_digest.
Inputs: cursor.
claudeseoskills__read_nodeAInspect
Read one node's full markdown body + frontmatter by node_id. Response includes outbound_links[] (resolved graph edges) unless with_links:false, plus source attribution. Pass heading (e.g. "Tactics") to get ONLY that markdown section — a few hundred chars instead of the whole body; every heading read, hit or miss, carries the node's headings list, and a miss is heading_not_found — so a guessed heading is cheap (heading "" just lists the headings). A heading read is partial — never write it back as a node's content; re-read without heading first. A long body is returned one page at a time — when the response says truncated, call again with { cursor } to continue it.
Inputs: node_id (required), cursor, heading, with_links.
claudeseoskills__search_nodesAInspect
Search nodes by text, node_type, and/or semantic type. Token-AND across title + description + tags. Primary retrieval path — use it before reading bodies. Results are ranked best match first — score on each row is the match strength (title hits count double). Page 1 is the top of the ranking. A one-word query can match hundreds of rows — put two or more terms in query so the top rows are the answer, not a dump. Terms are AND-ed: if two return nothing, drop one. Reports total_matches; when more matches exist than fit in one response, narrow the query or pass { cursor } for the next page (a cursor is only valid for the query that produced it).
Inputs: type, query, cursor, node_type.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Live SEO workflow tools for Claude Code, Codex, and AI agents.
Search, browse & read 340+ Claude Code marketing & SEO skills from any MCP client.
Find, read and install 50,000+ Agent Skills for Claude Code and other agents, with trust scores.
Search and read free, scanned AI agent skills and configs. Read-only, no account.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to access self-hosted SEO data and workflows, including keyword research, rank tracking, competitor insights, backlinks, site audits, and AI visibility.MIT
- AlicenseAqualityDmaintenanceEnables Claude to perform multi-agent SEO analysis with specialist prompts and tools for fetching pages, PageSpeed, and SERP data.3MIT
- AlicenseAqualityDmaintenanceProvides AI agents with professional-grade SEO capabilities including on-page analysis, technical audits, PageSpeed insights, and Ahrefs data integration.13135 npm42 PyPI5MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude, ChatGPT, Cursor, and other MCP clients to query Google Search Console, GA4, PageSpeed Insights, and live SERPs through 38 read-only SEO tools for quick wins, content decay, indexing, Core Web Vitals, AI traffic, and conversion analysis.2MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.