paas-build
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAAS_PROXY | No | The paas.build API (secrets stay server-side) | https://paas.build |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| identify_businessA | Identify a business from a name, website, or short phrase — using Opus 4.8 with live web search and website reading. Returns business name, what they do, website, country and region (uk/eu/us/other). Use this first to understand who the merchant is before going live. |
| go_liveA | Take a business live on UniPaaS — creates a payment vendor and returns access tokens so the app can start accepting payments immediately (progressive KYB, capped £1,500 individual / £2,500 company). By default provisions BOTH sandbox and production and returns a token for each. Individuals go live instantly; companies get an onboarding link to finish identity/document steps. |
| create_checkoutA | Create a hosted checkout session for a vendor and return a payable shortLink. The vendor must already be live (go_live). Use this to demonstrate a real payment. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: identify_business identifies the merchant, go_live provisions it, and create_checkout creates a payment session. No overlap.
All tools use consistent snake_case verb_noun pattern: identify_business, go_live, create_checkout.
With only 3 tools, the surface is minimal. While it covers a basic flow, it feels thin for a payment platform; borderline acceptable.
Missing key operations like updating business info, handling refunds, or managing vendor status. The flow has dead ends after go_live and checkout, limiting agent autonomy.