mercure.rocks
Mercure is an open protocol and reference hub for pushing real-time updates over Server-Sent Events. The mercure.rocks site provides the specification, self-hosted hub software, and a managed cloud service for running Mercure hubs.
mercure.rocks documents one HTTP integration surface: the Mercure Hub endpoint at `/.well-known/mercure`, used for publish and subscribe over HTTP/SSE with JWT-based auth (Bearer header or auth cookie, with anonymous subscribe optionally configurable).
- Mercure Hub HTTP interfacediscovered
For a self-hosted hub, generate your own shared secret or key pair and configure it in the hub with publisher_jwt / subscriber_jwt or the MERCURE_PUBLISHER_JWT_KEY / MERCURE_SUBSCRIBER_JWT_KEY settings described in Hub configuration. Then mint JWTs for publishers and/or subscribers signed with that configured key; publisher tokens must carry a mercure.publish claim and subscriber tokens for private updates must carry mercure.subscribe, as shown in Getting Started and Troubleshooting. For Mercure Cloud, buy a hub via Pricing and configure the same JWT settings from the cloud administration interface described in Mercure Cloud.
conventions · 1/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✓https://mercure.rocks/llms.txt
- API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing