# Buun Group developers > How a Buun Group product signs people in with Buun Identity, reads their plan, and takes the tokens the Buun MCP gateway sends it, so an agent reaches the product through one MCP endpoint. Every page below is plain Markdown. The whole site in one file: https://developers.buungroup.com/llms-full.txt ## Get started - [Build on Buun Identity](https://developers.buungroup.com/index.md): One Buun Group account for every product, and one MCP endpoint in front of all of them. These pages say how a product signs people in with Buun Identity, reads what they pay for, and takes the tokens the Buun MCP gateway sends, so an agent reaches the product with no second sign-in. - [Quick start](https://developers.buungroup.com/quick-start.md): What a new Buun Group product does to sign people in with Buun Identity and to be reachable through the MCP gateway, in the order it does it. - [Architecture](https://developers.buungroup.com/architecture.md): What runs where, what each part may do, and which repository holds it. ## Sign in with Buun - [The sign-in flow](https://developers.buungroup.com/sign-in/flow.md): Sign in with Buun is OAuth 2.1 with OpenID Connect: an authorization code with PKCE S256, traded at the token endpoint for an access token, an ID token and, when asked for, a refresh token. - [Tokens and keys](https://developers.buungroup.com/sign-in/tokens.md): Every access token and ID token is a JWT signed with ES256 by Buun Identity. A product checks one with the published keys, without calling the issuer. - [Plans](https://developers.buungroup.com/sign-in/plans.md): What a person pays for lives at Buun Identity, product by product. A product asks for it each time it matters, with the access token it already holds. - [Clients](https://developers.buungroup.com/sign-in/clients.md): A client is anything that signs people in with Buun Identity: a product's website, the gateway, another company's app, or an agent. Staff register one in the staff console; an agent registers itself with a metadata document. ## MCP gateway - [How the gateway works](https://developers.buungroup.com/mcp/how-it-works.md): The Buun MCP gateway is one MCP endpoint, https://mcp.buungroup.com/mcp, in front of every Buun Group product. A person connects an agent to it once and reaches the tools of every product they use. - [Accepting Buun Identity tokens](https://developers.buungroup.com/mcp/accepting-tokens.md): What a Buun product's MCP server (Plotwork, Flung, and the next one) adds so the Buun MCP gateway can call it for anyone on its plan, with no second sign-in. The gateway trades the agent's token at Buun Identity for a token meant for your server (RFC 8693, see Token exchange). Your server checks that token like any other access token, learns who the person is, and answers. - [Token exchange](https://developers.buungroup.com/mcp/token-exchange.md): How the gateway turns the agent's token into one meant for a product (RFC 8693), and every check Buun Identity makes before it does. A product never takes part in the trade; it only checks the token it is sent. - [Tool review](https://developers.buungroup.com/mcp/tool-review.md): A product's tool reaches an agent only once staff approve that exact version. A tool's name, title, description, input schema and annotations are words an agent reads and acts on, so a change to any of them waits for review again. ## Run and test - [Local development](https://developers.buungroup.com/local-development.md): How to run Buun Identity, the portal, the gateway and the staff console on one machine, and test a product through the gateway over localhost. - [Staff console](https://developers.buungroup.com/staff-console.md): Where staff set up what a product needs at Buun Identity and the gateway. Every change asks for a reason and is written to the console's audit trail and to the service's own. ## Reference - [Endpoints](https://developers.buungroup.com/reference/endpoints.md): Every address of Buun Identity a product, an agent or the gateway calls. Paths are on the issuer of each environment, such as https://id.buungroup.com. - [Scopes and claims](https://developers.buungroup.com/reference/claims.md): What a client may ask for, and what each token says about the person. - [Errors](https://developers.buungroup.com/reference/errors.md): How Buun Identity says no. The OAuth endpoints answer in the protocol's own shape; everything else in one envelope of its own. - [Environments](https://developers.buungroup.com/reference/environments.md): Every address of every environment. Put them in each Worker's wrangler.jsonc vars, one set per environment, and never read them from a token or a request. ## For agents - [Building a product, for agents](https://developers.buungroup.com/agents/building-a-product.md): The brief an agent follows when it builds a new Buun Group product, or adds Buun Identity to one, without reading the Buun Group repositories. Each step is something to do, then something to check.