Buun Group Developers
Pages

How the gateway works

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.

Markdown

What an agent sees

ToolWhat it does
buun_whoamiWho the agent is signed in as
buun_productsEvery product the gateway offers, and whether this person can reach it
buun_connectA link that connects a product the old way, with the product's own sign-in, for ten minutes and once
buun_disconnectDisconnects a product
<product>__<tool>Each product's own tools, approved by staff, such as plotwork__draw_diagram

Connecting an AI tool

People connect from the account portal, under Connected products: one address, https://mcp.buungroup.com/mcp, and the steps for each tool, with its own command, config file or one-click install. Staff see the same panel on the console's Gateway page. Every tool signs in with Buun Group by OAuth the first time, so nobody pastes a key.

ToolHow
Claude Codeclaude mcp add --transport http buun-group https://mcp.buungroup.com/mcp, then /mcp to sign in
ClaudeSettings, Connectors, Add custom connector, and paste the address
ChatGPTSettings, Apps & Connectors, Advanced settings, Developer mode; then Create, and paste the address
Codexcodex mcp add buun-group --url https://mcp.buungroup.com/mcp, then codex mcp login buun-group
CursorThe one-click install link, or ~/.cursor/mcp.json
VS CodeThe one-click install link, or code --add-mcp
Windsurf~/.codeium/windsurf/mcp_config.json with serverUrl
Gemini CLIgemini mcp add --transport http buun-group https://mcp.buungroup.com/mcp, then /mcp auth buun-group
Zedcontext_servers in its settings
Roo Code, Kilo Code.roo/mcp.json or .kilocode/mcp.json, type streamable-http
Kiro, LM StudioTheir mcp.json with the address
Ampamp mcp add buun-group https://mcp.buungroup.com/mcp
OpenCodeopencode.json, type remote, then opencode mcp auth buun-group
Goosegoose configure, Add Extension, Remote Extension (Streamable HTTP)
JetBrains AI, Le Chat, Cline, and any other MCP clientTheir MCP or connector settings, and paste the address

Connecting an AI tool from the account portal: every tool with its stepsConnecting an AI tool from the account portal: every tool with its steps

The list lives in AGENT_CLIENTS of @buun-group/ui, and the panel is its AgentConnect component.

Signing in to the gateway

The gateway is a resource server of Buun Identity (RFC 9728). Its metadata is at /.well-known/oauth-protected-resource and names Buun Identity as the authorization server. An agent such as Claude Code registers itself with a client ID metadata document, signs the person in, and sends the access token whose aud is the gateway on every MCP request.

Reaching a product

There are two ways, chosen per product in the gateway's catalogue:

WayWhenThe person does
Token exchangeThe product accepts Buun Identity tokens (acceptsIdentityTokens)Nothing. Anyone on the product's plan sees its tools
The product's own sign-inAny other productCalls buun_connect once and signs in to the product. The gateway keeps the product's tokens sealed for them

Connecting a product automatically once it trusts Buun IdentityConnecting a product automatically once it trusts Buun Identity

Token exchange is the way every new product should take: see Accepting Buun Identity tokens.

The catalogue

The products the gateway reaches are a closed list in code, src/upstreams/catalogue.ts of buun-group/buungroup-gateway, one list for each of production, preview and local development:

ts
{ product: 'plotwork', endpoint: 'https://mcp.plotwork.dev/mcp-oauth', authorizationServer: 'https://mcp.plotwork.dev', acceptsIdentityTokens: true }
FieldMeaning
productThe product id
endpointThe product's MCP endpoint. It is also the aud of every token traded for it
authorizationServerThe one sign-in server the gateway trusts for the product's own sign-in
acceptsIdentityTokensSet once the product checks Buun Identity tokens. The gateway then trades instead of asking the person to connect

A product is added by a reviewed change, never by a row or a request. Staff can turn a product off at the gateway from the console at any time.