Skip to main content
Glama
listbee-dev

listbee-mcp

Official
by listbee-dev
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoHTTP port (http mode only)8080
LISTBEE_API_KEYNoListBee API key. Optional — omit to start in bootstrap-only mode.
LISTBEE_BASE_URLNoAPI base URLhttps://api.listbee.so

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
bootstrap_startA

Step 1 of 2. Emails an OTP and returns a single-use bootstrap_token plus the account_id. Token TTL 10 min. Flow: bootstrap_start → bootstrap_verify. No API key required.

When to use: Kicking off a new seller account. The human will receive a 6-digit OTP by email; bring the code back and call bootstrap_verify.

Tips:

  • Human interaction required: ask for their email, then tell them to check inbox

  • bootstrap_token expires in 10 minutes — call bootstrap_verify promptly

  • Disposable email domains are blocked

Note: This action requires human intervention. You cannot complete it yourself.

bootstrap_verifyA

Step 2 of 2. Verifies the OTP, issues the first API key (shown once — store immediately), and returns Stripe onboarding URL. Hand the Stripe URL to the human; poll bootstrap_poll until ready.

When to use: The human pasted the OTP. Call this once with bootstrap_token + otp_code to mint the API key.

Tips:

  • Store the api_key IMMEDIATELY — it is shown once and cannot be recovered

  • After receiving the key, restart this MCP session with the key to unlock all tools

  • After 5 failed OTP attempts the bootstrap_token is invalidated — call bootstrap_start again

  • Hand the stripe_onboarding_url to the human; poll bootstrap_poll every 30s until ready=true

Note: This action requires human intervention. You cannot complete it yourself.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored across 2 tools

Disambiguation5/5

bootstrap_start and bootstrap_verify have clearly distinct roles: one initiates the flow by sending an OTP, the other completes it by verifying the OTP and issuing credentials. No overlap.

Naming Consistency5/5

Both tools follow the bootstrap_verb pattern consistently, making the flow's stages immediately recognizable.

Tool Count3/5

Only 2 tools are provided, which is thin even if the server is scoped solely to account bootstrapping. The description hints at additional tools unlocked after bootstrap, suggesting the set here is intentionally minimal but still feels incomplete.

Completeness2/5

The bootstrap flow itself is fully covered (start → verify), but for a server named listbee-mcp, one would expect tools for managing listings, orders, payments, etc. The surface is severely incomplete for the implied domain.

Maintenance

ActivitySlowing
ResponsivenessSyncing

Resources