About paas-build-mcp
paas-build-mcp is a payment onboarding MCP server for AI agents. It can identify a business, open sandbox and production merchant accounts, and create checkout links; progressive KYB lets accounts start with a cap while verification proceeds.
Key features
- 01Identify a business
- 02Open sandbox and production merchant accounts
- 03Create checkout sessions and payment links
- 04Check payment needs locally
- 05Give agents scoped tokens
Use cases
- 01Enable payments for a new application
- 02Check whether an app needs Connect or a company account
- 03Create a payable checkout link for a business
MCP support
The server exposes identify_business, go_live, and create_checkout to MCP clients, and can also be reached at https://paas.build/mcp.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @paasbuild/mcpPAAS_PROXYpaas.build API base (secrets stay server-side).Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
3Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| input | string | Yes | A business name, website domain, or free-text description (e.g. "clubright", "triibe.ai", "we sell candles in Austin") |
Details
From the project READMEpaas.build MCP server
Let your AI agent take a business live on payments — no dashboard, no forms, no week-long review.
Most payment MCPs manage an account you already have. This one goes a level deeper: it creates the account. From Claude Code, Cursor, Windsurf or any MCP client, an agent can identify a business, open a real merchant account (sandbox and production, on FCA-authorised rails), and mint checkout tokens — in one session. Progressive KYB: live immediately with a cap, verification completes in the background. One rate: 3.9%.
Install
Set up the skill + slash commands (one command):
npx @paasbuild/mcp install
This writes a paas.build skill plus /paas-add-payments and /paas-check commands into your project (.claude/ + AGENTS.md), so your agent knows when and how to add payments. Then wire the tools:
claude mcp add paas-build -- npx -y @paasbuild/mcp
(or point any MCP client at https://paas.build/mcp)
Then just say: "add payments to my app."
Check your app first (private-safe)
npx @paasbuild/mcp check
Runs locally in your repo — nothing is uploaded. Tells you if you'll hit the Stripe no-company wall or need Connect to pay out your users, and how to go live instead. Public repo or a live URL instead? Use the web version at paas.build/check.
Tools
| Tool | What it does |
|---|---|
identify_business | Resolves a name / website / phrase into a business (uses web search) |
go_live | Creates a real merchant account — sandbox + production — and returns scoped access tokens |
create_checkout | Creates a checkout session and returns a payable link |
Configuration
| Env | Default | Notes |
|---|---|---|
PAAS_PROXY | https://paas.build | The paas.build API (secrets stay server-side) |
The agent never holds platform keys — only scoped tokens for the vendor it created.
Why this exists
AI agents build full products in one evening — then hit the last blocker: accepting money. Traditional merchant onboarding assumes a human filling forms and waiting days. This server makes onboarding itself agent-native. Read more: Agentic payments — agents can pay, but can they get paid?
- Site: paas.build · Docs for agents: paas.build/agents
- React checkout:
@paasbuild/react - Powered by UniPaaS — FCA-authorised payment institution (No. 929994)
MIT © UniPaaS
mcp-name: io.github.UNIPaaS/paas-build-mcp
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.