Paylo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": true
} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_merchantsA | List available Paylo merchants and storefronts. Use this to discover stores before searching for products. |
| search_productsC | Search for products across Paylo stores. Can filter by merchant or category. |
| get_product_detailsC | Get detailed information about a specific product including price, description, and availability. |
| create_orderC | Create a new order for products. Returns an order ID that can be used to generate a payment link. |
| generate_payment_linkA | Generate a Paystack payment link for an existing order. Returns the URL to share with the user. |
| check_payment_statusB | Check the payment status of an order. Returns 'success', 'pending', or 'failed'. |
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
Each tool has a clearly distinct purpose with no overlap: check_payment_status handles payment status, create_order creates orders, generate_payment_link generates payment links, get_product_details retrieves product info, list_merchants lists merchants, and search_products searches products. An agent can easily differentiate between these operations.
All tools follow a consistent verb_noun naming pattern (e.g., check_payment_status, create_order, generate_payment_link, get_product_details, list_merchants, search_products). This uniformity makes the tool set predictable and easy to understand.
With 6 tools, the server is well-scoped for handling payments and product discovery in a Paylo context. Each tool serves a clear and necessary function, avoiding bloat while covering core workflows like order creation, payment processing, and product browsing.
The tool set covers key operations for payment processing and product discovery, including order creation, payment link generation, status checking, and product/merchant listing. A minor gap is the lack of tools for updating or deleting orders, but agents can likely work around this given the focused scope on payment flows.