Share Content Across Servers Without Sharing Databases
Federation lets multiple Aipokit instances share media catalogs while keeping full control of their own data. No shared database. No vendor cloud. Just servers talking to servers.
One Model Context Protocol server for the sites we publish. AI assistants connect once and search across jueewo.ventures and aipokit.com — structured passages with links, not scraped HTML guesses.
Live endpoint: mcp-sites.yawninghero.com (infrastructure hostname). Part of Agent Experience Optimization (AXO) — the agent-era complement to SEO. We built and used it before writing about it; see From SEO to AXO.
Each site publishes an agent index at build time (/api/agent-index.json). This Bun service fetches those indexes on a schedule, merges them, and exposes four MCP tools:
| Tool | Purpose |
|---|---|
search | Keyword, semantic, or hybrid search across one site or the indexed set |
list_sites | Indexed origins with document counts |
get_page | Full text of one page or article by URL |
get_related | Topically nearest entries — powers in-site related blocks |
The server also serves POST /chat (SSE-streamed, tool-using answers for the on-site chat widget) and GET /api/related.json (precomputed neighbours consumed at Astro build time).
Point any MCP client at https://mcp-sites.yawninghero.com/mcp and ask something that spans the indexed sites — e.g. “Search for BPMN agents and summarise the connection.” The journal post reproduces a real multi-site synthesis from that workflow.

paraphrase-multilingual-MiniLM-L12-v2 (local, cached on disk)Source repo: mcp-server-sites in the platform workspace beside the studio websites.