BotSupply
Prepaid credits for agents: browse SKUs, open a wallet, check balance, buy packs, Stripe top-up.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"botsupply": {
"url": "https://botsupply.onrender.com/mcp"
}
}
}Remote endpoints
https://botsupply.onrender.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (5)
🟢list_catalog
List live BotSupply SKUs, credit prices, short descriptions, and what a purchase does not include. Payloads stay behind purchase. recipe.book-table, when listed, is recipe documentation only and does not place a reservation.
Input Schema
{
"type": "object",
"properties": {},
"additionalProperties": false
}🟡open_wallet(label)
Create a wallet and return wallet_id plus api_key once, with balance_credits 0. Same as POST /v1/wallets. This does not look up an existing wallet. Keep the api_key; later tools need it as Authorization: Bearer or as api_key.
Input Schema
{
"type": "object",
"properties": {
"label": {
"type": "string",
"description": "Optional label, 1 to 80 characters. Same field as POST /v1/wallets."
}
},
"additionalProperties": false
}🟢get_balance(api_key)
Return the authenticated wallet id and prepaid credit balance. Same as GET /v1/balance. Does not return the API key.
Input Schema
{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "Wallet API key (bsk_…). Optional when the MCP client sends Authorization: Bearer. The local stdio process also reads BOTSUPPLY_API_KEY."
}
},
"additionalProperties": false
}🟡purchase(sku, api_key)
Buy one live catalog SKU with prepaid credits. Sends { sku } to POST /v1/purchase and returns that JSON, including the pack or recipe payload. Does not place a reservation. recipe.book-table is documentation the buying agent runs itself. An unknown SKU is rejected. Insufficient balance returns an error and does not deduct credits.
Input Schema
{
"type": "object",
"properties": {
"sku": {
"type": "string",
"description": "Live catalog SKU. The field name is sku, not sku_id."
},
"api_key": {
"type": "string",
"description": "Wallet API key (bsk_…). Optional when the MCP client sends Authorization: Bearer. The local stdio process also reads BOTSUPPLY_API_KEY."
}
},
"required": [
"sku"
],
"additionalProperties": false
}🟡create_checkout(credits, wallet_id, api_key)
Start a Stripe Checkout credit top-up. Same as POST /v1/wallets/:id/checkout. Returns the checkout url (open that URL; it keeps Stripe's hosted-page fragment). credits is an integer from 100 to 100000. Credits are applied only after Stripe reports the session paid. Returns the API error when Stripe is not configured.
Input Schema
{
"type": "object",
"properties": {
"credits": {
"type": "integer",
"minimum": 100,
"maximum": 100000,
"description": "Credits to buy. 1 credit = $0.01 USD. Same limits as POST /v1/wallets/:id/checkout."
},
"wallet_id": {
"type": "string",
"description": "Wallet to credit. Defaults to the wallet that owns the API key."
},
"api_key": {
"type": "string",
"description": "Wallet API key (bsk_…). Optional when the MCP client sends Authorization: Bearer. The local stdio process also reads BOTSUPPLY_API_KEY."
}
},
"required": [
"credits"
],
"additionalProperties": false
}Community
Evidence