MCP / API
Transport the request and response into the tools you already use.
MCP is an open standard for connecting AI applications to data and tools, so nothing about the connection is GitMir-specific. GitMir speaks it over HTTP with a bearer key, accepts three protocol versions, and forwards your request to the engine byte for byte without rewriting it.
Point the client at the endpoint shown on the Access page.
Send the key as an Authorization bearer header.
Call tools/list once to see everything that is available.
Call the context tool with the task in the user's own words.
HTTP only: there is no local server to install and no stdio transport, so a client that cannot reach an HTTPS MCP endpoint cannot connect. A request with no key gets a plain refusal, not a sign-in flow. And this is only transport — the standard says nothing about the quality of what comes back, which is why the case for GitMir is a measurement rather than a protocol.
See it on a real product.
Three models are published in full and open without an account. Ask one of them the question this page is about.