MCP / API
Bring the same Intelligence into Claude, Codex, internal agents and connected systems.
One HTTPS endpoint speaking MCP, with a bearer key issued per person. Seventeen tools, all of them questions about the product or small writes about work — there is no bulk read. The engine has REST routes behind it too, but the key you get in the workspace is an MCP key.
Open Access in the workspace and reveal or copy your key.
Paste the ready-made line for Claude Code, Codex, Cursor or VS Code.
Restart the client and check that seventeen gitmir_ tools are listed.
On the People page, check whether a member's key has actually reached GitMir.
Keys carry the role of the person they belong to: a viewer's key can read and ask, but the three tools that write — confirming a word, claiming work, closing it — refuse it. A key is not a side door: the same access checks, the same per-minute rate limit and the same plan apply to it as to the screens. The API is not a self-serve product yet: several engine routes exist with no screen and no documented public contract, so treat MCP as the supported path. Neither path can export a model.
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.