โ ๐ฆ๐๐ป๐ฑ๐ฎ๐ ๐๐ผ๐ณ๐ณ๐ฒ๐ฒ & ๐๐ผ๐ฑ๐ฒ: ๐๐ถ๐ฟ๐๐ ๐ ๐๐ฟ๐ผ๐๐ฒ ๐ฎ ๐๐๐ฎ๐ป๐ฑ๐ฎ๐ฟ๐ฑ ๐ณ๐ผ๐ฟ ๐๐ฒ๐ฏ๐๐ถ๐๐ฒ ๐ณ๐ฟ๐ผ๐ป๐ ๐ฑ๐ผ๐ผ๐ฟ๐. ๐ง๐ต๐ฒ๐ป ๐ ๐ต๐ฎ๐ฑ ๐๐ผ ๐บ๐ฒ๐ฒ๐ ๐ถ๐.
Two weeks ago I published the MCP Website Profile (MCP-WP) v0.1, a proposed draft for giving every website the same front door for AI agents: a known address (/mcp), standard tool names and standard answers.
I also admitted that my own www.ai4enterprise.ca/mcp, the โ๐ณ๐ฆ๐ง๐ฆ๐ณ๐ฆ๐ฏ๐ค๐ฆ ๐ช๐ฎ๐ฑ๐ญ๐ฆ๐ฎ๐ฆ๐ฏ๐ต๐ข๐ต๐ช๐ฐ๐ฏโ, didnโt actually pass my own spec - slightly awkward. So this week Claude and I fixed that.
๐ฃ๐ถ๐ฐ๐ธ๐ถ๐ป๐ด ๐๐ต๐ฒ ๐ฏ๐ถ๐๐ ๐๐ต๐ฎ๐ ๐ณ๐ถ๐
MCP-WP is modular on purpose, so a site only implements what it needs. Mine now claims Core plus two Extended modules:
- ๐๐ผ๐ฟ๐ฒ: get_site_info, get_services, get_contact, search_site and get_page
- ๐๐ ๐๐ฒ๐ป๐ฑ๐ฒ๐ฑ-๐๐ป๐๐ถ๐ด๐ต๐๐: search, read, latest and topics for the articles. These are the tools I already had, now speaking the standardโs language.
- ๐๐ ๐๐ฒ๐ป๐ฑ๐ฒ๐ฑ-๐ฆ๐ฒ๐ฟ๐๐ถ๐ฐ๐ฒ ๐ฑ๐ฒ๐๐ฎ๐ถ๐น๐: the full write-up of each service.
And what I deliberately left out:
- ๐ฃ๐ฒ๐ผ๐ฝ๐น๐ฒ: thereโs one person on this site, and itโs me. A people directory with one entry is an About page with extra steps.
- ๐ง๐ฟ๐ฎ๐ป๐๐ฎ๐ฐ๐๐ถ๐ผ๐ป๐ฎ๐น: calls are booked through an external scheduler - one โbook a callโ button, the link in get_contact does the job.
๐๐ผ๐๐ฝ๐น๐ฒ ๐ผ๐ณ ๐ผ๐ฏ๐๐ฒ๐ฟ๐๐ฎ๐๐ถ๐ผ๐ป๐:
- Search was the real work. Core says search must cover every page, so agents need clean page text. Most of my pages are rendered on request, and SvelteKit politely declines (with an HTTP 204) to fetch those during the build. So after the build, a small script renders each page and turns its main content into Markdown.
- Agents get what people see, minus the menus and footer. That partly answers my own question about whether Core is too heavy: for a static site itโs easy, but for one that renders pages on request, getting the content out is most of the job.
- Let the specโs schemas do the policing. The tools use the standardโs JSON Schemas exactly as published.
- The rate limiter tripped my own conformance checker. The checker makes well over 60 calls; the server allows 60 a minute.
- Implementing the spec also found some rough edges in it. A small one: get_page can tell an agent that a page was cut short, but get_insight canโt. Thatโs going on the v0.2 list.
๐๐๐ถ๐น๐ ๐๐ถ๐๐ต:
- Cloudflare Workers and Pages
- SvelteKit
- Model Context Protocol (MCP)
- The MCP-WP v0.1 JSON Schemas
- Claude Code
The spec, schemas and examples are at github.com/steveh250/website-mcp-standard. If you try it on your own site, Iโd love to hear what breaks first.
๐ฅ๐ฒ๐บ๐ฒ๐บ๐ฏ๐ฒ๐ฟ: ๐ง๐ต๐ถ๐ป๐ธ. ๐ ๐ผ๐ฑ๐ฒ๐น. ๐๐ฐ๐. (๐๐ฃ๐ ๐๐ค๐๐๐๐)
