seo-toolkit-mcp
# seo-toolkit-mcp
SEO toolkit as an MCP server. Analyze meta tags, robots.txt, sitemaps, keyword density, readability, and heading structure from any AI assistant that supports MCP.
## Install
Add to your MCP client config (Claude, Cursor, etc.):
```json
{
"mcpServers": {
"seo-toolkit-mcp": {
"command": "npx",
"args": ["-y", "seo-toolkit-mcp"]
}
}
}
```
## Tools
| Tool | Description |
|------|-------------|
| `meta_tags` | Analyze a page's SEO meta tags (title, description, OG, Twitter, canonical) |
| `robots_txt` | Parse robots.txt rules, sitemaps, and crawl directives |
| `sitemap_check` | Validate sitemap.xml format, URL count, and common issues |
| `keyword_density` | Keyword frequency analysis with single words, bigrams, and trigrams |
| `readability` | Flesch-Kincaid readability scoring with actionable tips |
| `heading_structure` | Heading hierarchy (H1-H6) analysis with structure validation |
## Example Prompts
- "Analyze the meta tags on https://example.com"
- "Check the robots.txt for example.com"
- "Validate the sitemap at https://example.com/sitemap.xml"
- "What's the keyword density of this text for 'machine learning'?"
- "Score this blog post for readability"
- "Check the heading structure of https://example.com/blog/post"
## License
MIT
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of SEO: meta tags, robots.txt, sitemap, keyword analysis, readability, and heading structure. While keyword_density and readability both analyze text, they answer different questions (keyword frequency vs. reading level), so there is minimal risk of confusion.
The names mostly follow a noun-based pattern with snake_case (meta_tags, robots_txt, keyword_density, readability, heading_structure), but sitemap_check breaks the pattern by using a verb prefix. This is a minor inconsistency in an otherwise clear and predictable set.
With 6 tools, the set is well-scoped and each tool provides a distinct function. It's within the ideal 3-15 range and doesn't feel bloated or sparse.
The toolkit covers meta tags, technical SEO files, heading structure, and text-based content analysis. However, there is a notable gap: keyword_density and readability require raw text input, but no tool fetches a page's body content, so agents must rely on external sources to analyze on-page text. Missing features like schema markup analysis are less critical but represent additional gaps.