Sitemap MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host to bind to if using SSE as the transport | 0.0.0.0 |
| TRANSPORT | No | The transport mechanism for the MCP server, either 'stdio' or 'sse' | sse |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_sitemap_treeC | Fetch and parse the sitemap tree from a website URL |
| get_sitemap_pagesB | Get all pages from a website's sitemap with optional limits and filtering options. Supports cursor-based pagination. |
| get_sitemap_statsC | Get comprehensive statistics about a website's sitemap structure |
| parse_sitemap_contentC | Parse a sitemap directly from its XML or text content |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_sitemap | Analyze a website's sitemap structure and organization |
| sitemap_health_check | Check the health and SEO aspects of a website's sitemap |
| extract_sitemap_urls | Extract and filter specific URLs from a website's sitemap |
| sitemap_missing_analysis | Analyze what content might be missing from a website's sitemap |
| visualize_sitemap | Visualize a sitemap as a Mermaid.js diagram |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The tools have mostly distinct purposes with clear boundaries: get_sitemap_pages retrieves individual pages, get_sitemap_stats provides analytics, get_sitemap_tree handles hierarchical structure, and parse_sitemap_content processes raw content. However, get_sitemap_pages and get_sitemap_tree could potentially overlap in some use cases as both involve fetching sitemap data from a URL, though their outputs differ significantly.
All tool names follow a consistent verb_noun pattern with 'get_' or 'parse_' prefixes and snake_case formatting. This uniformity makes the tool set predictable and easy to understand at a glance, with no deviations in naming conventions.
With 4 tools, this server is well-scoped for its sitemap-focused purpose. Each tool serves a distinct function without redundancy, and the count is appropriate for covering core operations like retrieval, analysis, structure parsing, and content processing in this domain.
The tool set provides comprehensive coverage for sitemap operations, including fetching pages, analyzing statistics, parsing trees, and handling raw content. A minor gap exists in update or modification capabilities (e.g., editing or generating sitemaps), but this is reasonable for a read-focused server, and agents can work around this limitation.