Sitemapkit MCP Server

MCP server for SitemapKit — discover and extract sitemaps from any domain

Local serverstdio

What is the Sitemapkit MCP MCP server?

Sitemapkit MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Sitemapkit MCP directly instead of describing what you should do. MCP server for SitemapKit — discover and extract sitemaps from any domain.

What you get

Model Context Protocol (MCP) server for SitemapKit. Lets any MCP-compatible AI assistant (Claude, Cursor, Windsurf, etc.) discover and extract sitemaps from any website.

What the assistant can call

Once Sitemapkit MCP is connected, these are the calls the assistant has available:

  • discover_sitemaps — Find all sitemap files for a domain (checks robots.txt, common paths, sitemap indexes)
  • extract_sitemap — Extract all URLs from a specific sitemap file
  • full_crawl — Discover + extract all URLs across all sitemaps in one call
  • Cursor — Add to .cursor/mcp.json in your project (or the global ~/.cursor/mcp.json):
  • Windsurf — The Windsurf tool exposed by this server

Configuration and credentials

You will need one environment variable: SITEMAPKIT_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Sitemapkit MCP's toolset — discover_sitemaps, extract_sitemap, full_crawl and 2 more — is a fair guide to whether it matches your workflow. It is maintained by 0nl1n1n; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the sitemapkit mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
discover_sitemapsFind all sitemap files for a domain (checks robots.txt, common paths, sitemap indexes)
extract_sitemapExtract all URLs from a specific sitemap file
full_crawlDiscover + extract all URLs across all sitemaps in one call
CursorAdd to .cursor/mcp.json in your project (or the global ~/.cursor/mcp.json):
WindsurfThe Windsurf tool exposed by this server.

How to install the Sitemapkit MCP MCP server

{
  "mcpServers": {
    "sitemapkit": {
      "command": "npx",
      "args": ["sitemapkit-mcp"],
      "env": {
        "SITEMAPKIT_API_KEY": "your-api-key-here"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
SITEMAPKIT_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Sitemapkit MCP to discover sitemaps.
  • Use Sitemapkit MCP to extract sitemap.
  • Use Sitemapkit MCP to full crawl.

Frequently asked questions

It connects Sitemapkit MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (discover_sitemaps, extract_sitemap, full_crawl, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Sitemapkit MCP directly.