Chargily MCP

A public Model Context Protocol (MCP) server for the Chargily Pay V2 API, hosted on Cloudflare Workers. Anyone can connect with their own Chargily API key — no shared secrets, no server-side configuration needed.

MCP Endpoint

https://mcp.ta9in.com/chargily-mcp/mcp

Related MCP server: btcpayserver-mcp

Quick Start

1. Get your Chargily API key from pay.chargily.com → Developer → API Keys

2. Set it in your project's .env file:

   CHARGILY_API_KEY=test_sk_your_key_here

3. Add to your MCP client config (e.g. claude_desktop_config.json):

   {
     "mcpServers": {
       "chargily": {
         "command": "npx",
         "args": [
           "mcp-remote",
           "https://mcp.ta9in.com/chargily-mcp/mcp",
           "--header",
           "Authorization: Bearer ${CHARGILY_API_KEY}"
         ]
       }
     }
   }

4. Restart your MCP client. The server auto-detects test vs live mode from your key prefix (test_sk_ / live_sk_).

Your key is never stored on the server — it's sent per-request and kept only in your MCP session.

Tools

How Authentication Works

Your Chargily API key is passed as an HTTP header with each request:

Authorization: Bearer <your_key>

or alternatively:

X-Chargily-Api-Key: <your_key>

The server reads it from the header, uses it for that session's API calls, and automatically selects test mode (test_sk_...) or live mode (live_sk_...) based on the key prefix.

Self-Hosting

git clone https://github.com/ta9in-oss/chargily-mcp
cd chargily-mcp
npm install

# Local dev
npm run dev
# → http://localhost:8788/chargily-mcp/mcp

# Deploy to your own Cloudflare account
npm run deploy

No secrets to configure — the Worker has no server-side API keys. Each user brings their own.

API Reference

Full Chargily Pay API docs: https://dev.chargily.com/pay-v2/introduction

License

MIT