Aigon MCP over HTTP

A mirror of the MCP tools, for agents — not a stable integration API. Same registry, same dispatch, over plain HTTP for when MCP is not practical — most often an LLM that can run curl but cannot speak MCP at all (several hosted assistants, on their cheaper plans), and for fetching attachments or piping JSON into a script. No backwards compatibility — none. Never hard-code an integration against it: field names, shapes and defaults can change under you at any time without notice, including in a patch release. Keep a human or an LLM in the loop, composing the calls or reading the outputs; unattended code parsing a fixed shape will break, and will break silently. Read the shape at call time from /rest/help. If you need a contract that holds still, use the product's own REST API; this is not that.

Your token stays in this tab. It is held in a JavaScript variable for as long as the page is open — never written to storage, never put in a URL, and sent only to this same server as an Authorization header. Reload and it is gone. If you would rather not paste a long-lived one, call admin.mint_rest_token from your MCP client for a short-lived token and use that. This page renders /rest/openapi.json fresh on every load, so it shows what this server actually serves. The catalogue of namespaces and functions is at /rest/help.