This server enables AI agents to onboard businesses onto a payment platform and start accepting real payments — without a dashboard or manual forms.
Identify a Business (identify_business): Resolve a business name, website, or free-text description into structured business information (name, what they do, website, country, and region) using live web search — use this first before onboarding a merchant.
Go Live with Payments (go_live): Create a real merchant account on UniPaaS (FCA-authorised rails) in sandbox and/or production environments, returning scoped access tokens for immediate payment acceptance. Supports individuals (instant) and companies (with KYB onboarding link), with progressive KYB and spend caps (£1,500 individual / £2,500 company).
Create a Checkout Session (create_checkout): Generate a hosted, payable checkout link for an already-onboarded vendor, specifying the environment, amount, currency, and an optional order reference.
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%.
Set up the skill + slash commands (one command):
npx @paasbuild/mcp installThis 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."
Related MCP server: Brighty MCP Server
npx @paasbuild/mcp checkRuns 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.
Tool | What it does |
| Resolves a name / website / phrase into a business (uses web search) |
| Creates a real merchant account — sandbox + production — and returns scoped access tokens |
| Creates a checkout session and returns a payable link |
Env | Default | Notes |
|
| The paas.build API (secrets stay server-side) |
The agent never holds platform keys — only scoped tokens for the vendor it created.
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
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
United States payments for AI agents — Stripe checkout via Stripe. Never holds funds.
Pakistan payments for AI agents — Safepay checkout via Safepay. Never holds funds.
Ireland payments for AI agents — cards / Apple Pay via Stripe. Never holds funds.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/UNIPaaS/paas-build-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server