Aloha WebMCP Registry
Hosted WebMCP manifests for third-party domains. Each manifest describes the AI-agent action surface of a website — primary CTAs, search, content fetch, due-diligence endpoints — in the format Chrome's Early-Preview-Program agents (and adjacent tools) consume.
The manifest lives here. The domain owner deploys a one-line edge rewrite so https://<their-domain>/.well-known/webmcp.json resolves to our hosted copy.
Live manifests
How a domain owner wires this up
Next.js / Vercel — add to next.config.js:
module.exports = {
async rewrites() {
return [
{
source: "/.well-known/webmcp.json",
destination: "https://webmcp.aloha.digital/m/<your-domain>.json",
},
];
},
};
Cloudflare Worker on the customer zone:
export default {
async fetch(req) {
const u = new URL(req.url);
if (u.pathname === "/.well-known/webmcp.json") {
return fetch("https://webmcp.aloha.digital/m/<your-domain>.json",
{ cf: { cacheTtl: 3600 } });
}
return fetch(req);
},
};
What's a WebMCP manifest?
A JSON document at /.well-known/webmcp.json declaring the callable actions of a website to AI agents — signup, search, content fetch, sales contact, etc. Agents read it and act on it instead of guessing at the UI. Inspired by, and complementary to, Anthropic's MCP: where MCP exposes in-product tools via a connected server, WebMCP exposes marketing-site / public-surface actions via a static manifest.