mcp

specification.website — MCP server

A Cloudflare Worker exposing The Website Specification as an MCP server. Public, read-only, no authentication.

Live endpoint: https://mcp.specification.website/mcp Server card: https://specification.website/.well-known/mcp/server-card.json Spec page: /spec/agent-readiness/mcp-and-tool-discovery/

Tools

Tool	Purpose
search(query, limit?)	Full-text search across all 96 spec pages, ranked, with body excerpts.
list_topics({ category?, status?, limit? })	Filtered list of spec items.
get_topic({ slug })	Full canonical Markdown for one spec page (frontmatter + body).
get_checklist({ category?, status? })	Audit-style flat checklist grouped by category.
get_categories()	The ten categories with topic counts.

Prompts

Prompt	Purpose
audit_url(url, focus?)	Builds an audit plan for a target URL against the required (or category-focused) items.

Architecture

• Cloudflare Worker, Streamable HTTP transport (MCP 2025-03-26).
• Stateless. No sessions, no SSE, no auth.
• The spec content is bundled at build time via scripts/build-data.mjs, which reads every Markdown file in ../src/content/spec/ and writes a single src/data.json. The Worker imports it via JSON module assertion — zero runtime parsing.

Local development

cd mcp
npm install
npm run dev    # wrangler dev on http://localhost:31338

Try it:

curl -sX POST http://localhost:31338/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | jq

Deploy

First time:

npx wrangler login                                # one-time
cd mcp
npm install
npm run deploy

wrangler.toml is configured to register the custom domain mcp.specification.website on first deploy. The parent zone specification.website must already be on Cloudflare.

Connecting an MCP client

Claude Desktop and any MCP-aware client:

{
  "mcpServers": {
    "specification-website": {
      "transport": "http",
      "url": "https://mcp.specification.website/mcp"
    }
  }
}

Updating the spec content

The Worker bundles content at build time. Whenever the spec content under ../src/content/spec/ changes, redeploy:

cd mcp
npm run deploy    # predeploy regenerates src/data.json automatically

No drift between site and MCP server: both read from the same Markdown source of truth.

Licence

MIT (code) / CC BY 4.0 (the spec content the Worker serves).