Developer docs
Reference for developers integrating with M1rror, including the MCP server and its tools, authentication, the REST API's status and webhooks.
M1rror's integration surface for developers is its MCP server: coding agents and MCP clients use it to read your design system, screens, releases and build plans and to draft changes, through the same policy-checked actions as the app.
- The MCP server: transport, authentication, scopes and limits.
- MCP tools: the tools agents can call, grouped by area.
- REST API and webhooks: what is and isn't public.
To connect a specific agent, see connect a coding agent.
In this section
- The MCP serverReference for M1rror's MCP server, covering Streamable HTTP transport, OAuth 2.1 and agent tokens, scopes, effective permissions, limits and errors.
- MCP toolsEvery tool a coding agent can use on M1rror's MCP server, grouped by area and generated from the same action registry the server uses.
- REST API and webhooksWhether M1rror has a public REST API or outbound webhooks today, and what to use instead for integrations, which is the MCP server.
Last updated
Edit this page on GitHub