BuildrEnterprise
Buildr for sellersBook a walkthrough

Turn your GitHub APIs into MCP — with roles.

Connect the OpenAPI already in your repo. We turn it into MCP tools for Cursor, Claude and your agents. You decide which roles can call which tools.

Book a walkthroughExplore the checklist
  • Keep your services as they are
  • Roles on every agent key
  • Hosted in the UK or EU
buildr.policy.yamlrolesfrom GitHub

Policy on the MCP

actions:
  issueRefund:
    class: money_moving
    allow: [finance]
    approval:
      required: always
      approvers: finance-leads
  deleteCustomer:
    allow: []
    # denied by default

RolesWho may call what

  • supportlistInvoices, getCustomer
  • financeissueRefund · needs approval
  • vieweraudit log only

Convert from GitHub. Run under roles.

  • GitHub
  • Cursor
  • Claude
  • Your own agents
  • Role-scoped keys
  • Vaulted credentials

How it works

From your repo to MCP with roles.

Keep shipping the same services. We convert the OpenAPI you already have, then you put roles on the tools.

1

Connect GitHub

Install the App on the repo that already holds your OpenAPI and services.

org/billing-api · openapi.yaml

2

We generate MCP tools

One tool per operation, documented from real sandbox responses.

48 operations → 48 MCP tools

3

You set roles

Builders, agents and groups: which tools each role may call, and what needs approval.

support: reads · finance: refunds

4

Agents connect

Issue a Vybe Access Key scoped to that role. Cursor, Claude or your bots use MCP under the policy.

vkey_… · tools allow-list

Roles

Roles live with the tools.

Policy and roles sit next to the OpenAPI in GitHub. You review who may call what in a pull request. The gateway only enforces what merged to the default branch.

Bot summary · sync tools from OpenAPI

  • +3 MCP tools for role support
  • NEWDELETE /customers/{id} → denied for all roles
  • Role finance: issueRefund needs approval
  • OpenAPI drift: listInvoices · contracts refreshed

What you get

Convert. Assign roles. Go live.

Companies already have the APIs. What they need is MCP for agents, with roles so support, finance and ops each get a different tool set.

GitHub in, MCP out

Point us at the OpenAPI in your repo. We generate the tools from those operations.

Generated from your OpenAPI

Roles on the MCP

Decide which agents and groups can call which tools. Support gets reads. Finance gets refunds. Viewers see audit.

Per-key allow-lists

Policy reviewed like code

buildr.policy.yaml lives in GitHub. Merges to the default branch are what the gateway loads. New risky actions stay denied until someone allows them.

PR review → live policy

Approvals when it matters

Writes and money-moving calls can hold for a named human. Timeout means deny. Every decision lands in the audit log. Upstream credentials stay in the vault.

UK or EU hosted gateway

Why Enterprise

DIY MCP stops at the tools.

We keep tools in sync with the repo and put roles on every agent key.

DIY MCP

  • Blank MCP server or pasted tools
  • Engineers writing tools by hand
  • One shared key, or nothing
  • Risky endpoints live until someone notices
  • No approval path for writes
  • Policy in a console somewhere
  • Credentials in agent config or env

With Buildr Enterprise

  • Your existing GitHub OpenAPI
  • Generated, then reviewed in a PR
  • Roles and groups on every key
  • Denied until policy allows them
  • Hold for a named human
  • buildr.policy.yaml in your repo
  • Vault refs on the gateway

Book a walkthrough

Pricing

Start free. Pay for builders only.

Free covers one repo and three MCP actions. Paid seats are for people who convert APIs and edit roles. Approvers, viewers and agent keys stay free. Mid-cycle seat changes prorate in GBP.

£0/ month

1 repo · 3 actions

One GitHub repo, three MCP actions, read-only roles. Enough to prove the path before you pay.

Start free

Figures are design-partner estimates. Prefer to click through yourself? Explore the checklist.

Questions

Straight answers.

What are we buying, exactly?

You get two things: MCP tools generated from the OpenAPI already in your GitHub, and role governance on that MCP — tool allow-lists, approvals and audit. Marketplace Buildr is a different product for publishing paid tools.

Is there a free plan?

Yes. Free Enterprise covers one GitHub repo and three MCP actions, read-only. Custom and Business add seats, credits and write approvals when you outgrow that.

Do we rewrite our services?

No. Keep the code and OpenAPI you have. We install a GitHub App, generate MCP tools from the spec, and sync through pull requests when the API changes.

How do roles work?

Builders edit policy and tools. Approvers clear held writes. Viewers read audit. Each agent key is scoped to the tools its role may call.

What if nobody approves a write?

The call stays held, then is denied when the timeout expires (default 15 minutes). Deny is the default for anything new and risky.

Who is this for?

Companies rolling Cursor, Claude or in-house agents onto their own APIs, and needing role control before security signs off. Typical champions: Head of Platform and CISO.

When can we start?

We are taking design-partner walkthroughs now. Bring the GitHub repo and OpenAPI path you want agents on first — or start on Free from the checklist.

Bring the repo you want on MCP.

Design-partner walkthroughs now. Thirty minutes. No deck spam.

Book a walkthrough for

Bring the GitHub repo and OpenAPI path you want on MCP.

Support: support@vybe.finance