Feed the systems you already use

GitMir publishes what it knows as an MCP server, so the assistant you already use can ask it directly. Seventeen tools cover the same ground as the screens: what this part is, what a change reaches, what the product calls something, what changed between builds, what work is waiting. Claude Code, Codex and Cursor are all good at working in your codebase; GitMir hands them the product understanding they would otherwise rebuild from the repository on every task. The address /mcp?project=<id> starts the assistant in one repository or in the whole project.

Each agent has its own key that reads only the project or repository it was connected to; a key that may not take work can read and ask but is refused when it tries to record a word, take a task or close one. Every call names one repository or one project; there is no call that covers a whole workspace at once. Traffic goes one way — GitMir answers and hands out work, it never reaches into your runtime, your issue tracker or your data. One-click setup is written for Claude Code, Codex, Cursor and VS Code; any other MCP client works with the configuration the same tab gives. Each answer an agent gets uses 1–10 credits.