Bitrefill MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITREFILL_API_ID | Yes | Your Bitrefill API ID. | |
| BITREFILL_API_SECRET | Yes | Your Bitrefill API secret key. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchB | Search for gift cards, esims, mobile topups and more. It's suggested to use the |
| detailB | Get detailed information about a product |
| categoriesA | Get the full product type/categories map. It's suggested to use this tool to get the categories and then use the |
| create_invoiceB | Create a new invoice for purchasing products with various payment methods |
| get_invoicesC | Retrieve a list of invoices with optional filtering |
| get_invoiceA | Retrieve details for a specific invoice by ID |
| pay_invoiceA | Pay an unpaid invoice (only works with 'balance' payment method) |
| get_ordersB | Retrieve a list of orders with optional filtering |
| get_orderB | Retrieve details for a specific order by ID |
| unseal_orderB | Reveal codes and PINs for a specific order by ID |
| get_account_balanceA | Retrieve your account balance |
| pingA | Check if the Bitrefill API is available |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| payment-methods | |
| product-types | |
| giftcards | |
| refills | |
| bills | |
| esims | |
| crypto-utils |
TDQS
Scored across 12 tools
Each tool targets a distinct operation: browsing categories, searching products, getting details, managing invoices and orders, checking balance, and pinging. No two tools overlap in purpose.
Most tools follow a verb_noun pattern (e.g., create_invoice, get_invoice, pay_invoice), but 'categories', 'detail', and 'ping' deviate slightly. Overall, names are understandable and predictable.
12 tools cover the core workflow of a purchase platform without being excessive. Each tool serves a clear role, and the count is well-scoped for the domain.
The tool set covers the full purchase lifecycle: browsing, product details, account balance, invoicing, payment, order retrieval, and order fulfillment. Minor gaps like cancellation or refund are absent but not critical for typical use.