Skip to content
Mercury
English
  • English
  • Русский — скоро
Design Book
Menu
English
  • English
  • Русский — скоро

Mercury documentation MCP server

The Mercury documentation MCP server is at https://mercury.jonnify.com/mcp. It runs in the Elixir Mercury LMS behind the same edge as this website. It provides public guidance; it does not install software, execute code, edit projects, read arbitrary files or require credentials.

Connect

Configure a remote Streamable HTTP MCP connection in your agent host using this URL:

{"mcpServers":{"mercury":{"url":"https://mercury.jonnify.com/mcp"}}}

The enclosing configuration and transport field vary by host. Select HTTP rather than a local command. The server negotiates MCP 2025-11-25 or 2025-06-18. It returns JSON responses to POST requests. It is stateless, issues no session ID, and offers no independent SSE stream: GET and DELETE return 405 with Allow: POST. Finish initialization before calling tools and send the negotiated MCP-Protocol-Version header on subsequent requests.

An experimental MCP Server Card publishes the same server identity, transport and versions. Runtime MCP lists remain authoritative; the card does not list tools or grant access.

Tools and component prompts

  • mercury_skills returns installation guidance for the public mercury-design-builder and mercury-playground skills, including manual installation without npm. Read the guidance.
  • mercury_installation accepts a target platform such as linux-x64 or darwin-arm64 and returns current mx installation guidance. An unsupported or unverified platform is not presented as an available native binary.
  • mercury_component accepts an exact public UI export name, such as Button, and returns its family reading guide and implementation checks. All tools are read-only and idempotent.
  • prompts/list returns a named reading prompt for each public UI component or composition export; prompts/get retrieves it. Names are generated from the public UI export graph. These prompts guide reading and verification, and do not replace the installed version's prop types.
  • resources/list and resources/read expose authored lesson companions and skills. Arbitrary URLs, local paths and private workspace artifacts are refused.

HTTP example

curl https://mercury.jonnify.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"my-agent","version":"1.0"}}}'

Then POST {"jsonrpc":"2.0","method":"notifications/initialized"} and {"jsonrpc":"2.0","id":2,"method":"tools/list"} with the same headers plus MCP-Protocol-Version: 2025-11-25. Notifications return 202 with no body. Tool validation errors explain how to recover; unknown methods return JSON-RPC errors.

Limits and privacy

Requests are limited to 16 KiB and 120 POST requests per client IP per minute, per application instance. A 429 response includes Retry-After; honor it rather than looping. Browser origins are restricted to the canonical Mercury site and its preview; ordinary native MCP clients may omit Origin. There is no CORS grant for unrelated browser origins. This public documentation service has no OAuth or account-specific data. Do not send secrets, private code or personal information as arguments. See privacy and contact.