MCP server
The ListBee MCP server exposes the ListBee API as tools any MCP-compatible AI client can call. Once configured, your AI assistant can create listings, check orders, and manage your account without leaving the conversation.
Install
No global install required. npx fetches and runs the package on demand.
Configure Claude Desktop
Add the server to your claude_desktop_config.json:
The config file is located at:
Restart Claude Desktop after editing the config. The ListBee tools appear automatically in the tool selector.
Configure Cursor
Add to .cursor/mcp.json in your project root, or to the global ~/.cursor/mcp.json:
Available tools
Each tool maps directly to a ListBee API endpoint.
Tool parameters
create_listing
update_listing
All fields are optional. Only the fields you provide are updated.
list_listings / list_orders
Example conversation
Once the MCP server is configured, you can ask Claude directly:
Create a listing called “SQL Performance Guide”, price $29, deliverable at https://my-bucket.s3.amazonaws.com/sql-guide.pdf
Claude will call create_listing and return:
Done. Your listing is live at: https://buy.listbee.so/xp6wq2dk
Environment variable
The server requires LISTBEE_API_KEY in its environment. You can also set it in your shell profile and omit the env block in the config:
Get your API key at console.listbee.so.
Common errors
Limitations
- No webhook management — the MCP server does not expose webhook CRUD. Use the API directly or the Python SDK.
- No account signup — the server assumes an existing API key. Create accounts via the API.
- No Stripe connection — connecting Stripe requires the API directly. Use
POST /v1/account/stripe-key. - Read-only orders — you can list and get orders, but cannot create or modify them (orders are created by buyer checkout).
Next steps
- Claude Code skill — an alternative integration for Claude Code that doesn’t require MCP.
- Agent onboarding flow — the canonical pattern for agents selling on ListBee.