Support MCP endpoint

Connect

Streamable HTTP, JSON-RPC 2.0, protocol revision 2025-06-18. The server is stateless: no session id is issued, so a single self-contained tools/call works with no handshake.

https://commerce-bots.com/api/mcp

Server identity: commerce-bots-support v1.0.0.

Try it

curl -sS https://commerce-bots.com/api/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

curl -sS https://commerce-bots.com/api/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call",
       "params":{"name":"search_integrations",
                 "arguments":{"platform":"shopify","limit":3}}}'

Tools

7 of the 8 tools are deterministic reads of published data — no model involved, so they are fast, free, and cannot invent an answer.

• search_integrations

  Search the commerce-bots directory of commerce MCP servers. Returns entries with their observed tools, auth model and verification date. Deterministic read of published data.

• get_integration

  Full published record for one integration by id, including which tools were observed as readable vs writable and when that was last verified.

• check_compatibility

  Check whether two or more integrations can be composed in one agent: tool-name collisions, combined context cost, and the documentation each one needs.

• get_setup_docs

  The setup checklist and required documentation links for one integration.

• get_service_info

  commerce-bots' own plans, rate limits, monthly quotas and contact addresses. Use this instead of guessing pricing.

• submit_support_request

  Send a question or issue to a human at commerce-bots. Use when the answer is not in the published data. Include an email address if a reply is wanted.

• report_data_issue

  Report an inaccuracy in a directory entry. Include a link to the evidence — vendor docs, a changelog entry, or a release note. Corrections backed by a source are applied quickly.

Model-backed

• ask_support

  Ask the commerce-bots support assistant a free-text question. Answers come only from published directory data and documentation; the assistant says so when something is not covered rather than guessing. This tool consumes model capacity and is rate-limited more tightly than the others.

Limits

• Anonymous: 20 requests/minute, bucketed by a one-way hash of your IP address.
• ask_support: additionally capped per hour, and it shares a global daily ceiling with the website's chat widget. When that ceiling is reached it returns an explicit "email us" reply rather than a degraded answer.
• Sending a valid cbk_ API key as Authorization: Bearer raises every ceiling.

What the data means

Every record describes what our harness observed against a live endpoint on the lastVerified date included in the response. Records do not assert that an integration is production-ready, stable, or recommended — we cannot verify that, so we do not claim it, and neither should an answer built on this data. Fields we could not verify are empty rather than guessed.

Found something wrong? Call report_data_issue with a link to the vendor's own docs, changelog, or release notes. Corrections backed by a source are applied quickly.

Error semantics

A tool that ran but could not satisfy the request — an unknown integration id, for instance — returns isError: true inside a successful JSON-RPC result. Protocol-level error codes are reserved for genuine protocol faults (malformed JSON, unknown method, bad params), so a normal "not found" never looks like a transport failure worth retrying.