Skip to main content
Glama
README.md
# paas.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):**

```bash
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**:

```bash
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)

```bash
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](https://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 |
| `create_subscription_plan` | Creates a recurring plan (week/month/year) and returns a planId. Needs the vendor's `access_token` |
| `create_subscription_checkout` | First charge + stored card + auto-renew for a plan; returns a payable link. Needs `access_token` |
| `list_subscriptions` | Lists the vendor's subscriptions for reconciliation. Needs `access_token` |

## 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?](https://paas.build/agentic-payments)

- Site: [paas.build](https://paas.build) · Docs for agents: [paas.build/agents](https://paas.build/agents)
- React checkout: [`@paasbuild/react`](https://github.com/UNIPaaS/paas-react)
- Powered by [UniPaaS](https://www.unipaas.com) — FCA-authorised payment institution (No. 929994)

MIT © UniPaaS

mcp-name: io.github.UNIPaaS/paas-build-mcp

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation3/5

add_payments is explicitly a composite of identify_business + go_live + optional create_checkout, so it overlaps three other tools and forces an agent to choose between the one-shot and the step-wise path. The descriptions give conflicting directives (identify_business says 'call this FIRST whenever a user wants to accept payments' while add_payments says 'prefer this whenever a user says add payments'), which magnifies the ambiguity. The remaining tools (checkout, subscription plan/checkout, list) are cleanly separated.

Naming Consistency4/5

All names are snake_case and nearly all follow a verb_noun pattern (add_payments, identify_business, create_checkout, create_subscription_plan, create_subscription_checkout, list_subscriptions). go_live is the one deviation, being a verb_adverb rather than verb_noun, but it is still readable and consistent in casing.

Tool Count5/5

Seven tools is well within the ideal 3-15 range and tightly scoped to the payments-onboarding domain. Each tool maps to a concrete step in the merchant lifecycle, with no filler or redundant wrappers beyond the deliberate add_payments convenience tool.

Completeness3/5

The surface covers onboarding (identify, go_live), one-off checkout, and subscription creation plus listing, but has notable gaps: no refunds, no subscription cancel/update/get, and no retrieval of individual payments, checkouts, or plans. Only list_subscriptions provides read access, leaving reconciliation and lifecycle management partially covered.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues