PayPls MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAYPLS_TOKEN | Yes | Your PayPls API token | |
| PAYPLS_API_URL | No | API endpoint URL | https://api.paypls.io |
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 |
|---|---|
| wallet_balanceA | Get the balance of a wallet bucket. Returns balance in the native unit (sats for BTC, dollars for USDC) plus approximate USD value. |
| wallet_list_bucketsA | List all wallet buckets you have access to, with their balances and auto-approve limits for both BTC and USDC. |
| wallet_send_btcA | Send Bitcoin to an address. May require human approval depending on amount and bucket settings. Always provide a clear justification. |
| wallet_send_usdcA | Send USDC (stablecoin) to an address. May require human approval depending on amount. USDC is ideal for stable-value payments. |
| wallet_receiveB | Get an address to receive funds into a bucket. Specify token type to get the appropriate address format. |
| wallet_tx_statusB | Check the status of a transaction by its ID. |
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 6 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are well-defined by their specific actions (balance, list, receive, send BTC, send USDC, transaction status) and target resources (wallets/buckets), making it easy for an agent to select the correct tool for any given task.
All tool names follow a consistent verb_noun pattern with a 'wallet_' prefix, such as wallet_balance and wallet_send_btc. This uniformity enhances readability and predictability, allowing agents to easily understand and navigate the toolset.
With 6 tools, the server is well-scoped for its wallet management domain. Each tool earns its place by covering essential operations like checking balances, listing buckets, receiving funds, sending different currencies, and checking transaction status, without being overly sparse or bloated.
The toolset provides complete CRUD/lifecycle coverage for wallet operations, including retrieval (balance, list), creation (receive), update (send actions), and status checks. There are no obvious gaps, ensuring agents can handle core workflows without dead ends.