MCP.so
Sign In

Bitrefill MCP Server

@bitrefill

About Bitrefill MCP Server

A Model Context Protocol Server connector for Bitrefill public API, to enable AI agents to search and shop on Bitrefill.

Basic information

Category

Other

License

MIT

Runtime

node

Transports

stdio

Publisher

bitrefill

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "bitrefill": {
      "command": "npx",
      "args": [
        "-y",
        "bitrefill-mcp-server"
      ],
      "env": {
        "BITREFILL_API_KEY": "your_api_key_here"
      }
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Bitrefill MCP Server?

The Bitrefill MCP Server is a sample/reference implementation that wraps the Bitrefill API v2 using a Bearer token. It is intended for developers who want to study, fork, extend, or self-host a customized MCP server on top of the Bitrefill API. For production use, a hosted remote MCP server is recommended instead.

How to use Bitrefill MCP Server?

Set the BITREFILL_API_KEY environment variable with an API key from the Bitrefill Developers page. The server exposes 18 tools that map to Bitrefill v2 endpoints. For production, connect to the hosted remote MCP at https://api.bitrefill.com/mcp (with OAuth or an API key in the URL).

Key features of Bitrefill MCP Server

  • Wraps 18 Bitrefill v2 API endpoints as MCP tools
  • Input validation via Zod schemas
  • Includes resources for allowed payment methods, categories, and product types
  • Supports self-hosting for private or air‑gapped environments
  • Sample implementation for learning and customization

Use cases of Bitrefill MCP Server

  • Study a working reference implementation of a Bitrefill MCP server
  • Fork and add custom tools, prompts, or validation logic
  • Self‑host inside a private network or air‑gapped environment
  • Experiment with a wider set of v2 endpoints than the curated production server

FAQ from Bitrefill MCP Server

How does this sample differ from the official hosted MCP?

The official hosted MCP (at https://api.bitrefill.com/mcp) is maintained by Bitrefill, supports OAuth, and exposes a curated set of 7 tools. This sample exposes 18 tools and is meant for learning, forking, or self‑hosting.

What authentication does the sample use?

The sample requires a BITREFILL_API_KEY environment variable. Requests are authenticated with Authorization: Bearer ${BITREFILL_API_KEY}.

What dependencies are needed to run the sample locally?

Node.js, pnpm (pnpm install, pnpm run build), and a valid Bitrefill API key from the Developers page.

What tools are available in the sample?

The 18 tools cover products, invoices, orders, account balance, phone number checks, ping, and a full eSIM workflow (list, get, create‑invoice, pay‑invoice, list, get).

How do I test the sample locally?

Run pnpm run build && pnpm run smoke for in‑process MCP client tests, or use the MCP Inspector with pnpm run inspector. Smoke tests only target the built server, not the remote hosted MCP.

Comments

More Other MCP servers