seo-toolkit-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| meta_tagsA | Fetch a URL and analyze its SEO meta tags. Returns title (with length check), meta description, Open Graph tags, Twitter Card tags, canonical URL, and actionable issues. Use this to audit any page's on-page SEO. |
| robots_txtA | Fetch and parse a site's robots.txt. Returns user-agent rules, allowed/disallowed paths, sitemap directives, crawl-delay, and issues. Use this to check what search engines can/cannot crawl. |
| sitemap_checkA | Validate a sitemap.xml file. Returns URL count, format (XML/index/text), sample URLs, last modified dates, and issues like duplicates or missing lastmod. Pass a domain to check /sitemap.xml, or a direct sitemap URL. |
| keyword_densityA | Analyze text for keyword frequency and density. Returns top single words, bigrams, and trigrams with percentages. Optionally check density of a specific target keyword. Use to optimize content for target keywords. |
| readabilityA | Score text readability using Flesch-Kincaid metrics. Returns Flesch Reading Ease score, grade level, word/sentence/syllable counts, average sentence length, reading time, and actionable tips. Use to ensure content matches your target audience. |
| heading_structureA | Analyze a page's heading hierarchy (H1-H6). Returns the heading outline/tree, counts per level, and issues like missing H1, multiple H1s, or skipped levels. Use to verify content structure for SEO and accessibility. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.