MCP server for the Bitrefill API v2 (Bearer API key) — products, invoices, orders, and eSIMs
Bitrefill MCP server exists for a simple reason — assistants are far more useful when they can act on Bitrefill directly instead of describing what you should do. MCP server for the Bitrefill API v2 (Bearer API key) — products, invoices, orders, and eSIMs.
This server wraps the Bitrefill API v2 (https://api.bitrefill.com/v2) using Authorization: Bearer ${BITREFILL_API_KEY}. Only request parameters are validated with Zod; API responses are returned as JSON text unchanged.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once Bitrefill is connected, these are the calls the assistant has available:
search-products — GET /products/search (with q) or GET /products (browse)product-details — GET /products/{id}buy-products — POST /invoicesget-invoice-by-id — GET /invoices/{id}get-order-by-id — GET /orders/{id}list-invoices — GET /invoiceslist-orders — GET /orderspay-invoice — POST /invoices/{id}/payget-account-balance — GET /accounts/balancecheck-phone-number — GET /check_phone_numberping — GET /pinglist-esim-products — GET /products/esimsYou will need 2 environment variables: BITREFILL_API_KEY, YOUR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Bitrefill's toolset — search-products, product-details, buy-products and 11 more — is a fair guide to whether it matches your workflow. It is maintained by bitrefill; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Bitrefill's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| search-products | GET /products/search (with q) or GET /products (browse) |
| product-details | GET /products/{id} |
| buy-products | POST /invoices |
| get-invoice-by-id | GET /invoices/{id} |
| get-order-by-id | GET /orders/{id} |
| list-invoices | GET /invoices |
| list-orders | GET /orders |
| pay-invoice | POST /invoices/{id}/pay |
| get-account-balance | GET /accounts/balance |
| check-phone-number | GET /check_phone_number |
| ping | GET /ping |
| list-esim-products | GET /products/esims |
| get-esim-product | GET /products/esims/{id} |
| create-esim-invoice | POST /esims |
{
"mcpServers": {
"bitrefill": {
"command": "npx",
"args": ["-y", "bitrefill-mcp-server"],
"env": {
"BITREFILL_API_KEY": "your_api_key_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| BITREFILL_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.