MCP
Expose product understanding and development tasks inside the agent and tool workflows you already run.
Access is one HTTP endpoint and one bearer key per person, issued on the Access page in the account. The same key reaches every project that person is allowed to read. The page also tells you whether the key has actually arrived at GitMir — with the time and the tool that got through — so that "a key exists" and "the connection works" stop looking identical from your side.
Open Access in your account and reveal or copy your key
Add the endpoint to your client with the key as a bearer header
Restart the client and confirm the tools are listed
Come back to the Access page to see the last connection and how it arrived
Rotate the key from the same screen if it ever leaks
A key belongs to a person, not to an agent or to a single repository: you cannot issue a key scoped to one project, and cutting off an agent means rotating that person's key. Access is MCP over HTTPS with a bearer token — there is no OAuth app and no third-party marketplace listing. A viewer's key is refused by the three tools that write. The key is never shown anywhere but inside the account.
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.