Build on Buun Identity
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.
Who this is for
| You are | Start with |
|---|---|
| Building a new Buun Group product | Quick start, then Building a product, for agents |
| Adding "Sign in with Buun" to a product's website | The sign-in flow |
Making a product's MCP server reachable through mcp.buungroup.com | Accepting Buun Identity tokens |
| Testing several products together on one machine | Local development |
| An agent reading these pages | llms.txt lists every page as Markdown; llms-full.txt is all of them in one file |
The parts
| Part | Address | What it does |
|---|---|---|
| Buun Identity | id.buungroup.com | The OpenID Connect issuer. The only thing that signs a token or keeps a credential |
| Account portal | account.buungroup.com | Where a person signs in, approves a product, and sees their products and plans |
| MCP gateway | mcp.buungroup.com | One MCP endpoint in front of every product. An agent connects once |
| Staff console | staff.buungroup.com | Where staff manage people, plans, clients, resource servers and gateway tools |
| A product | Its own domain | Plotwork, Flung, GunSpec, Destroy Network, CryptFlare, and the next one |
Three rules that hold everywhere
- A token has one audience. A product accepts only a token whose
audis its own address. A token for the gateway does not open Plotwork, and one for Plotwork does not open Flung. - A token never travels on. Nothing forwards the token it was sent. The gateway trades it at Buun Identity for one meant for the product, or uses the person's own connection to the product.
- A plan is never in a token. A product asks Buun Identity what the person pays for each time it matters, so a cancelled plan is gone at once.