Bacon Services MCP server

baconservices-mcp

An MCP server that lets an AI agent buy image work from Bacon Services, one call at a time, paid in USDC on Base over x402 from your own wallet, within spending limits you set. There's no account and no API key: the agent calls a tool, the server checks the price against your limits, signs a USDC payment for exactly that price, and returns the result.

Also listed in the MCP Registry as io.github.afmontoya/baconservices-mcp.

Wallet safety

Your wallet private key stays on your machine. Bacon Services never receives or stores it. Payments are signed locally and are subject to configurable per-call, session, and daily spending limits.

What it sells

Image tools take PNG, JPEG or WebP up to 8 MB, as imageurl (public https) or imagepath (a local file). removebackground, optimizeimage and vectorizeimage return a signed download link (valid 24 hours); imagepalette and brandfromurl return their JSON result in the tool result. Add save_to to write either kind to disk. Prices come from Bacon's live catalog, and each paid tool states its current price in its description.

imagepalette, brandfromurl and vectorizeimage appear once Bacon's catalog publishes them with contract versions. A service the installed package doesn't understand is listed by list_services but can't be called until you update the package.

Free tools:

version of the package can run it.

• list_services: everything Bacon sells right now, with prices, limits, and whether this

Nothing is signed.

• quote: Bacon's current price for one service, and whether your limits and wallet allow it.

and whether you can afford each service (yes/no).

• wallet_status: network, whether a wallet is configured, your limits and what's left of them,

Before you start

You don't need ETH: x402 payments are signed authorizations (EIP-3009), and the facilitator pays the gas.

1. Node.js 20 or newer.
2. A dedicated wallet holding only what you're willing to spend. Fund it with USDC on Base.

Pointing BACONWALLETKEYFILE at that file keeps the key out of MCP host configs, which are often synced or shared. BACONWALLETPRIVATEKEY also works.

1. Put the private key in a file that only you can read, for example ~/.bacon/buyer.key.

The key never leaves your machine. Only signatures are sent, and only to Bacon. The key is never logged, never written to the spend ledger, and never accepted as a tool argument.

Install

Claude Code

claude mcp add bacon -e BACON_WALLET_KEY_FILE=/home/you/.bacon/buyer.key -- npx -y baconservices-mcp

Add more -e NAME=value pairs for the limits below. Check it with claude mcp list.

Claude Desktop

Settings → Developer → Edit Config (claudedesktopconfig.json):

Shortened. The full README is on GitHub.