Agent runtimes
Keep orchestration, workflow state, permissions, tools and execution where they already run.
GitMir connects as one more MCP server over HTTPS. Whatever runs your agents — Claude Code, Codex, an in-house runner — keeps deciding what runs, in what order, with which permissions and against which live data. Adding GitMir is a config line and a key, not a migration.
Keep your orchestration and tool permissions exactly where they are.
Add one HTTP MCP endpoint and a bearer key to the client's config.
Restart the client; it should list seventeen gitmir_ tools.
Give your agents the habit of asking before reading the repository.
GitMir has no orchestration, no scheduler and no hosting for your agents — none of that exists in the product. Connection is per client, by config file or CLI: there is no plugin, extension or marketplace listing, and nothing installs itself. Transport is streamable HTTP only, so a client that cannot reach an HTTPS MCP endpoint cannot connect.
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.