# agentbodegastore/agentbodega [Health: Active]

**Category:** 🔗 Aggregators  
**Repository:** https://github.com/agentbodegastore/agentbodega  
**GitHub Stars:** 4  
**npm Downloads (last month):** 288  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/agentbodegastore-agentbodega

## Description
AgentBodega MCP gives agents a live catalog of 65 x402-payable HTTP tools across search, public data, social media, status checks, media conversion, and agent-readiness checks. No API keys; install with npx -y @agentbodega/mcp.

## Tools
Capabilities this server exposes over MCP:

- **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

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "agentbodega": {
    "command": "npx",
    "args": ["-y","@agentbodega/mcp"]
  }
}
```

## Documentation

## What agentbodegastore/agentbodega does

The agentbodegastore/agentbodega MCP server gives agents a live directory of AgentBodega HTTP endpoints. The catalog covers areas including social-media research, real-estate searches, service and cloud status checks, domain and launch-readiness audits, agent-discoverability checks, x402 inspection, directory packaging, and hosted artifacts. The listed resources are payable through the x402 model.

Its role is discovery and request preparation rather than execution. An agent can compare available routes, review prices, inspect required fields and response formats, and receive an example request. The server does not make the paid HTTP request on the agent’s behalf.

## How it works

At runtime, the package makes outbound HTTPS requests to AgentBodega’s hosted service. It reads the live catalog, x402 discovery document, L402 discovery document, and OpenAPI contract. This means endpoint information comes from the current hosted service rather than from a fully bundled static catalog.

A typical workflow starts with a plain-language task or a catalog search. After an endpoint is identified, the agent can retrieve its detailed contract and generate an editable request. Generated calls contain an `X-PAYMENT` placeholder and notes about x402 verification. L402 information is available as a discovery and payment-handoff surface; it should not be treated as usable payment execution unless the live document identifies a configured issuer.

## Setup and configuration

The agentbodegastore/agentbodega package can run through `npx`:

```bash
npx -y @agentbodega/mcp
```

For Claude Desktop, configure an MCP server with `npx` as the command and `-y @agentbodega/mcp` as its arguments. Remote clients that support Streamable HTTP can connect to `https://agentbodega.store/mcp`; an SSE endpoint is also available at `https://agentbodega.store/mcp/sse`.

`AGENTBODEGA_BASE_URL` optionally changes the service base URL. If it is not set, the package uses `https://agentbodega.store`. The repository also provides an agent skill file that can be downloaded directly from GitHub.

## Tools and capabilities

The agentbodegastore/agentbodega tools support this sequence:

- `agentbodega_plan_task` sends a plain-language task to the free planner and returns a suggested route, alternatives, inputs, examples, and payment handoff notes.
- `agentbodega_search_catalog` searches the live directory by text, category or department, tag, and maximum USD price.
- `agentbodega_get_endpoint` returns a selected endpoint’s method, URL, price, inputs, schemas, examples, and description.
- `agentbodega_call_snippet` creates editable curl and JavaScript requests with payment placeholders.
- `agentbodega_payment_guide` explains x402 discovery, settlement, L402 status, and the blockchain-only balance policy.

The server also exposes `agentbodega://catalog`, `agentbodega://x402`, `agentbodega://l402`, and `agentbodega://openapi` resources.

## Limitations and notes

The package does not fetch payment challenges, settle payments, or execute paid endpoints. Agents must use the returned contract and snippets to perform any later HTTP call themselves. Its runtime behavior depends on outbound HTTPS access to the hosted AgentBodega service. The repository itself contains the MCP package, while the hosted API runs separately at AgentBodega’s domain. It does not run install scripts, spawn shells, bundle dependencies, or execute paid calls.

_Full upstream README: https://allmcps.com/mcp/agentbodegastore-agentbodega/readme_