
Paas Build Mcp
io.github.UNIPaaSPublished by GitHub account UNIPaaSv0.1.4Updated Oct 24, 2026
Your agent opens a real merchant account (go_live) and takes payments the same day. 3.9% flat.
Overview
Lets an AI agent identify a business, open a real merchant account and create checkout links and subscription plans through paas.build.
- What you can do
- Identify a business from a name, website or phrase, using web search
- Open a real merchant account in sandbox and production and return scoped access tokens
- Create checkout sessions that return payable links
- Create recurring subscription plans and subscription checkouts, and list a vendor's subscriptions for reconciliation
- Install a project skill and slash commands, and run a local check of whether an app will hit payment onboarding blockers
- When to use it
- Use it when an agent-built app needs to start accepting payments and you want the merchant account itself created from the assistant session rather than through a dashboard and forms. It suits quick sandbox-to-production onboarding for a small business or side project.
- Requirements
- Runs as a local npm package over stdio, so Node.js is needed; a remote endpoint is also mentioned. The PAAS_PROXY environment variable sets the API base (default paas.build). Subscription tools need the vendor's access_token returned by account creation. An MCP client such as Claude Code, Cursor or Windsurf is assumed.
Installation
In SourceWeft
- Open Paas Build Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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):
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:
(or point any MCP client at https://paas.build/mcp)
Then just say: "add payments to my app."
Check your app first (private-safe)
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
Configuration
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
Source: README.md at commit 785f0b3
Tools
0Version history
1- v0.1.4LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts