AutoRank 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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_title_lengthA | Check whether a page title will be truncated in Google results. Measures approximate pixel width rather than character count, because Google truncates on width. Returns the estimate, the limit, and a verdict. |
| check_description_lengthB | Check whether a meta description will be truncated in Google results. |
| generate_meta_tagsA | Generate a complete head block: title, description, canonical, Open Graph and Twitter Card tags. Returns HTML ready to paste. |
| generate_robots_metaB | Build a robots meta tag from directives, with the resulting tag and an explanation of what it permits. |
| generate_robots_txtC | Generate a robots.txt. Optionally block the major AI training crawlers. |
| validate_robots_txtA | Validate a robots.txt and surface the mistakes that actually cause damage. |
| generate_faq_schemaA | Generate FAQPage JSON-LD. Each item needs 'question' and 'answer'. The answers MUST already be visible on the page. Schema that disagrees with the rendered page is a spam signal, not a shortcut. |
| generate_article_schemaC | Generate Article JSON-LD. Dates should be ISO 8601 (YYYY-MM-DD). |
| generate_breadcrumb_schemaA | Generate BreadcrumbList JSON-LD. Each item needs 'name' and 'url'. |
| generate_local_business_schemaC | Generate LocalBusiness JSON-LD with a postal address. |
| validate_json_ldA | Validate a JSON-LD block: parse it, check required Schema.org fields, and flag the things that commonly cause a rich-result warning. |
| keyword_densityC | Word and phrase frequency for a body of text, with a density warning. |
| readability_scoreB | Flesch Reading Ease and grade level for a body of text. |
| build_utm_linkB | Build a UTM-tagged tracking URL. |
| slugifyB | Turn a title into a clean URL slug. |
| generate_hreflangA | Generate hreflang link tags. Each page needs 'lang' (e.g. en-us) and 'url'. Every listed page must carry the full set, including a self-reference, or the cluster is ignored. |
| serp_previewA | Preview how a result will render in Google, including truncation. |
| autorank_free_toolsC | List the browser versions of these tools, plus the ones not exposed here. |
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 18 tools
Each tool targets a distinct SEO asset or action, making most selections unambiguous. Some overlap exists between check_title_length/check_description_length and serp_preview, but the descriptions clarify the different outputs. No tools are redundant.
The naming is mostly consistent with a generate_/check_/validate_ pattern, and all names use snake_case. Exceptions like slugify, keyword_density, and readability_score deviate slightly but remain intuitive and readable.
At 18 tools, the count is slightly above the typical 3-15 range but justified by the breadth of SEO functionality. Each tool serves a distinct purpose, though a few could be consolidated or omitted without major loss.
The toolkit covers many core SEO tasks: meta generation, robots handling, common schemas, and content analysis. However, significant gaps remain, such as sitemap generation, redirect handling, and a broader set of schema types (e.g., Product, Recipe). These missing pieces limit full lifecycle coverage.