zbd

This MCP server provides a set of ZBD-related tools for handling Bitcoin Lightning payments, gamertag charges, and other ZBD-specific operations. The server exposes a collection of tools under the ZBD namespace (e.g., send-lightning-payment, create-charge, get-payment, etc.) that you can invoke as modular commands in your MPU environment or via the generated executables. The design centers around modular TypeScript tools that can be built into standalone binaries for easy deployment with your client applications, such as Claude Desktop or Cursor. To use the server locally, ensure you have a valid ZBD API key and run the server executable or a TS runner pointing at the main entry index.ts; you’ll then be able to call the included tools against the ZBD API to perform payments, create charges, validate addresses, and manage vouchers and withdrawals. The repository documents a wide range of capabilities, including sending payments, creating and validating charges, converting Gamertags, retrieving user IDs, and handling wallet information and region checks. When integrating with a client, you typically build the tools to executables, invoke them directly, and pass the required parameters (addresses, amounts, gamertags, etc.) to perform the corresponding ZBD operations.

Prerequisites:

• Node.js 23+ (or Bun/Deno/Anything that can run TypeScript files)
• pnpm (or npm/yarn as an alternative)
• ZBD API key (create from ZBD Developer Dashboard)

Installation steps:

1. Install dependencies

pnpm install

2. Create configuration file with your API key

# In project root, create a .env or update existing environment with your key
# Example (bash):
export ZBD_API_KEY=YOUR_ZBD_API_KEY

3. Build the executables (if you want standalone binaries)

# Build all tools (as described in the project)
pnpm build

# Build a specific tool (example for ZBD tool)
pnpm run build:zbd

4. Run the MCP server (development/run locally)

# Using node to run the TS entry (as described in the readme)
node src/index.ts

# Or, after building, run the generated binary located under bin/ (example)
./bin/mcp-zbd

5. Verify installation

pnpm test

Notes:

• This MCP server is deprecated in favor of a newer implementation. A migration path is provided in the repository README, directing you to the newer MCP server at the Zebedee repository. Use that version for production workloads.
• Ensure your ZBD_API_KEY is kept secure and not committed to version control. Use environment variables or a secure vault.
• If you run multiple instances, use the ps aux / pkill commands shown in the README to monitor and manage processes, avoiding duplicate MCP server instances.
• When building with Cursor, always reference the full path to the executable, e.g. /path/to/your/project/bin/mcp-zbd. If running TS directly with Node, you can point to src/index.ts, but ensure the runtime supports TS execution or use ts-node if required.
• The available tools inside the ZBD MCP Server cover a broad range of operations (payments, charges, gamertags, vouchers, withdrawals, and wallet info); consult the project’s source and docs for exact CLI signatures and required parameters for each tool.