Burnbound MCP Server

Burnbound is an MCP integration. Let your AI agent pay x402 APIs within daily caps, allowed hosts and human approval.

Packages and local setup

The published npm package is @burnbound/mcp, version 0.3.3. Its declared MCP transport is stdio.

The package declares BURNBOUND_KEY (required): Agent key (bb_agent_…) created in the Burnbound dashboard. Sent only to the Burnbound API.; BURNBOUND_API: Burnbound API base URL. https:// only (http:// only for loopback). Set it for a self-hosted or local API.; BURNBOUND_AGENT_ID: Only with an org key instead of an agent key: the agent the tools act for. Ignored with an agent key.; BURNBOUND_WALLET_PROFILE: Local wallet profile for client-side signing (created with npx -y @burnbound/mcp wallet init). 1–32 of a-z, 0-9, _ and -.; BURNBOUND_HOME: Directory for the local wallet file when the OS keychain is not used.; BURNBOUND_MAX_RESPONSE_BYTES: fetch_paid response body cap in bytes (maximum 10485760). Longer bodies are truncated.; BURNBOUND_FETCH_TIMEOUT_MS: fetch_paid deadline for the whole exchange with the URL, between 1000 and 120000 ms..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project website. This profile uses version 0.3.3 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.