All Insights
#SundayCoffeeAndCode
November 2026

Sunday Coffee & Code: First I wrote a standard for website front doors. Then I had to meet it.

Two weeks ago I published the MCP Website Profile (MCP-WP) v0.1 and admitted my own site didn't pass it. This week Claude and I aligned www.ai4enterprise.ca/mcp with the spec, adopting only the parts that fit.

By Steve Harris

โ˜• ๐—ฆ๐˜‚๐—ป๐—ฑ๐—ฎ๐˜† ๐—–๐—ผ๐—ณ๐—ณ๐—ฒ๐—ฒ & ๐—–๐—ผ๐—ฑ๐—ฒ: ๐—™๐—ถ๐—ฟ๐˜€๐˜ ๐—œ ๐˜„๐—ฟ๐—ผ๐˜๐—ฒ ๐—ฎ ๐˜€๐˜๐—ฎ๐—ป๐—ฑ๐—ฎ๐—ฟ๐—ฑ ๐—ณ๐—ผ๐—ฟ ๐˜„๐—ฒ๐—ฏ๐˜€๐—ถ๐˜๐—ฒ ๐—ณ๐—ฟ๐—ผ๐—ป๐˜ ๐—ฑ๐—ผ๐—ผ๐—ฟ๐˜€. ๐—ง๐—ต๐—ฒ๐—ป ๐—œ ๐—ต๐—ฎ๐—ฑ ๐˜๐—ผ ๐—บ๐—ฒ๐—ฒ๐˜ ๐—ถ๐˜.

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.

๐—ฅ๐—ฒ๐—บ๐—ฒ๐—บ๐—ฏ๐—ฒ๐—ฟ: ๐—ง๐—ต๐—ถ๐—ป๐—ธ. ๐— ๐—ผ๐—ฑ๐—ฒ๐—น. ๐—”๐—ฐ๐˜. (๐™–๐™ฃ๐™™ ๐™˜๐™ค๐™›๐™›๐™š๐™š)

Want to Discuss This Topic?

Steve is always happy to have a direct conversation.