MCP discovery server for AgentBodega x402-ready paid data tools.
MCP discovery server for AgentBodega x402-ready paid data tools. Exposed over MCP by the agentbodega mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Give agents a live menu of paid, x402-ready tools from AgentBodega.
Everything the assistant can do here goes through one of these:
agentbodega_plan_task — use first when an agent has a plain-language taskagentbodega_search_catalog — use first to find the right paid endpoint. Itagentbodega_get_endpoint — use after search when you know an endpoint key,agentbodega_call_snippet — use after selecting an endpoint to generateagentbodega_payment_guide — use when an agent needs the AgentBodega paymentYou will need one environment variable: AGENTBODEGA_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Among the payments and commerce options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. AgentBodega MCP's toolset — agentbodega_plan_task, agentbodega_search_catalog, agentbodega_get_endpoint and 2 more — is a fair guide to whether it matches your workflow. It is maintained by agentbodegastore; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against AgentBodega MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| agentbodega_plan_task | use first when an agent has a plain-language task |
| agentbodega_search_catalog | use first to find the right paid endpoint. It |
| agentbodega_get_endpoint | use after search when you know an endpoint key, |
| agentbodega_call_snippet | use after selecting an endpoint to generate |
| agentbodega_payment_guide | use when an agent needs the AgentBodega payment |
{
"mcpServers": {
"agentbodega": {
"command": "npx",
"args": ["-y", "@agentbodega/mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| AGENTBODEGA_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.