MCP server
Point an external agent at mcp.flagon.io to operate Flagon and read its documentation.
Flagon exposes a Model Context Protocol server at mcp.flagon.io, so an external agent (for example, an assistant in your editor) can work with Flagon directly.
One registry, three front doors
The MCP server, the in-product assistant, and the HTTP API all draw from the same set of operations. Add a capability once and it is available everywhere. Nothing the agent can do reaches around the permission-checked API.
What it exposes today
- Documentation tools. Any agent can search Flagon's docs and read pages, so it can learn how Flagon works before acting. These are read-only and safe to use without authentication.
- Operational tools. Acting on your organization's data over MCP requires authentication, so the agent operates as you, with your scopes.
Connecting
Point your MCP-capable client at https://mcp.flagon.io to get started. With no
credentials, the server exposes only the read-only documentation tools.
To reach the operational tools, present a Flagon access token as a bearer token:
Authorization: Bearer flagon_xxx
The token acts as you: the server resolves it to your identity and the tools you can use are exactly the ones your token's scopes allow (a token with no scopes has full access, still bounded by your role). A tool your token cannot reach is simply not listed. This is the same permission model as the REST API - the token is the ceiling, and tenant isolation always applies.