maib-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAIB_CLIENT_ID | Yes | OAuth client ID from MAIB developer portal | |
| MAIB_PROJECT_ID | Yes | Project ID from MAIB dashboard | |
| MAIB_CLIENT_SECRET | Yes | OAuth client secret |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_paymentB | Create a new MAIB e-commerce payment. |
| get_paymentB | Get payment details by ID. |
| refund_paymentB | Refund a payment (full or partial). |
| create_recurringC | Create a recurring payment with a saved card token. |
| get_recurringC | Get recurring subscription details. |
| cancel_recurringB | Cancel a recurring subscription. |
| create_one_click_paymentC | Create a one-click payment with a saved card. |
| get_transaction_statusC | Get detailed transaction status. |
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 8 tools
Each tool targets a distinct action (create, get, refund, cancel) on specific resources (payment, recurring, transaction). No overlap or ambiguity.
All tools follow a consistent verb_noun snake_case pattern (e.g., create_payment, get_recurring), making them predictable.
8 tools cover the essential payment operations without bloat. The scope is appropriate for an e-commerce payment server.
Covers core CRUD for payments and recurring, plus refund and status. Missing listing endpoints (e.g., list_payments) but these are not critical for basic workflows.