discover_sitemaps
Find all sitemap files for a given domain by checking robots.txt, common paths, and sitemap indexes. Returns a list of sitemap URLs. Use this first to understand a site's sitemap structure.
LABSCO SUMMARY
Checking robots.txt and sitemap indexes is the difference between finding the sitemap and finding one of them.
Large sites split their sitemap into an index pointing at many child files, and a naive fetch of the obvious path finds a fraction of the URLs. Following the index and reading robots.txt for the declared location is the unglamorous part that makes the result complete. Reach for the combined call when you just want the list; use the two separate tools when you need to see which sitemap a URL came from.
What it is
A server over SitemapKit's API, for getting the complete URL list of a website without crawling it page by page.
What you get
- discover_sitemaps — find a domain's sitemap files, checking robots.txt, the common paths and sitemap indexes
- extract_sitemap — pull every URL out of one sitemap file
- full_crawl — discovery and extraction across all of them in a single call
Requirements
An API key from their site, and npx to run it.
Setup effort
One command plus a key — npx sitemapkit-mcp, then supply credentials
USE CASES
01
Getting every URL on a site
One call that discovers and extracts across all sitemaps.
02
Finding where the sitemaps are
Checks robots.txt, common paths and indexes.
03
Reading one sitemap
Extract the URLs from a specific file.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
extract_sitemap
Extract all URLs from a specific sitemap file (including sitemap indexes that link to child sitemaps). Returns URL entries with optional lastmod, changefreq, and priority metadata.
full_crawl
Discover all sitemaps for a domain and extract every URL across all of them in one call. This is the most convenient tool when you want the complete URL list for a site. Returns deduplicated URLs with metadata.
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected.
Requires
- npx on PATH
- SITEMAPKIT_API_KEY in your environment
Where it runs
All 3 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
Sign up at sitemapkit.com and grab your API key from app.sitemapkit.com/settings/api.
TERMINAL
npx sitemapkit-mcpMCP Clients
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"sitemapkit": {
"command": "npx",
"args": [
"sitemapkit-mcp"
],
"env": {
"SITEMAPKIT_API_KEY": "<YOUR_SITEMAPKIT_API_KEY>"
}
}
}
}Cursor
Add to .cursor/mcp.json in your project (or the global ~/.cursor/mcp.json):
CURSOR · JSON
{
"mcpServers": {
"sitemapkit": {
"command": "npx",
"args": [
"sitemapkit-mcp"
],
"env": {
"SITEMAPKIT_API_KEY": "<YOUR_SITEMAPKIT_API_KEY>"
}
}
}
}Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
WINDSURF · JSON
{
"mcpServers": {
"sitemapkit": {
"command": "npx",
"args": [
"sitemapkit-mcp"
],
"env": {
"SITEMAPKIT_API_KEY": "<YOUR_SITEMAPKIT_API_KEY>"
}
}
}
}
