bog-ipay-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOG_CLIENT_ID | Yes | OAuth client ID from BOG iPay | |
| BOG_CLIENT_SECRET | Yes | OAuth client secret from BOG iPay |
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 |
|---|---|
| get_auth_tokenA | Get OAuth 2.0 access token from BOG iPay. |
| create_orderC | Create a new payment order. |
| get_order_statusA | Get order status by ID. |
| refund_orderB | Refund an order (full or partial). |
| create_recurringC | Set up a recurring payment. |
| charge_recurringB | Charge a recurring subscription. |
| preauth_orderB | Pre-authorize (hold) an amount on a card. |
| complete_preauthC | Complete/capture a pre-authorized order. |
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 payment operation: auth, order creation, status check, refund, recurring setup/charge, preauth and capture. No overlapping purposes.
All tool names follow a consistent verb_noun snake_case pattern (e.g., get_auth_token, create_order, refund_order). Even compound verbs like preauth_order fit the pattern.
8 tools is well-scoped for a payment processing server, covering core payment lifecycle without unnecessary bloat.
Covers the main payment lifecycle: auth, create, status, refund, recurring, preauth/capture. Missing explicit cancel/void for orders and recurring cancellation, but core workflows are functional.