🌐

Kibo Commerce MCP Server

Updated June 2026✓ Official

Kibo Commerce ships an official MCP server hosted directly on your own Kibo tenant, so AI assistants can query and mutate live commerce data — catalog, orders, carts, customers, inventory, pricing, shipping, and site settings — without a custom middleware layer. Built by Kibo Commerce, it is officially maintained and best for API & Web.

by Kibo Commerce

About

Kibo Commerce ships an official MCP server hosted directly on your own Kibo tenant, so AI assistants can query and mutate live commerce data — catalog, orders, carts, customers, inventory, pricing, shipping, and site settings — without a custom middleware layer. The endpoint follows the pattern https://{host}/mcp/admin/{toolCategories} on your tenant host (for example https://t1000000-s12345.sb.usc1.gcp.kibocommerce.com/mcp/admin/), with the tenant identifier and optional site identifier baked into the hostname; tenant-only URLs work for tenant-level operations, while site-scoped calls need the tenant-plus-site form. Because it is a hosted HTTP server there is no package to install: you add a url entry with an Authorization header to claude_desktop_config.json, .cursor/mcp.json, the Windsurf mcp_config.json, or VS Code Copilot settings. Authentication reuses your existing Kibo API credentials two ways: HTTP Basic with a Base64-encoded applicationKey:clientSecret pair from the Kibo Dev Center, or a short-lived JWT obtained from the Kibo OAuth endpoint at home.kibocommerce.com and sent as a Bearer token (roughly one hour, so your client needs refresh handling). The scale is the notable part — the default /mcp/admin/ path exposes over 500 operations, so Kibo lets you filter by appending comma-separated categories named {resource}.{operation}, such as products.read or categories.read,categories.update, which cuts both tool-discovery latency and the token cost of the tool list. Categories span Commerce Runtime (cart, checkout, order, quote, return, wishlist), Customer and B2B accounts, Product Admin (products, variations, price lists, discounts, search merchandizing and synonyms), Location and inventory, Shipping Admin, Pricing Runtime, and Import/Export. A separate documentation MCP server exists for querying Kibo docs. Debug tool calls with npx @modelcontextprotocol/inspector against the same URL.

Unverifiable
not scored

No repository for this entry resolves against the live GitHub API, so there is nothing to verify. It is deliberately left unscored rather than given a number we cannot stand behind.

What could not be measured

These contributed nothing to the score — not a penalty, not a zero. They are why the confidence reads the way it does.

  • Source verificationunknown

    No repository for this entry resolves against the live GitHub API. Without a confirmed source there is nothing to inspect, so this entry is excluded from trust scoring entirely rather than scored on catalog metadata alone.

Frequently Asked Questions

What is Kibo Commerce MCP Server?
Kibo Commerce is an MCP server built by Kibo Commerce. Kibo Commerce ships an official MCP server hosted directly on your own Kibo tenant, so AI assistants can query and mutate live commerce data — catalog, orders, carts, customers, inventory, pricing, shipping, and site settings — without a custom middleware layer. The endpoint follows the pattern https://{host}/mcp/admin/{toolCategories} on your tenant host (for example https://t1000000-s12345.sb.usc1.gcp.kibocommerce.com/mcp/admin/), with the tenant identifier and optional site identifier baked into the hostname; tenant-only URLs work for tenant-level operations, while site-scoped calls need the tenant-plus-site form. Because it is a hosted HTTP server there is no package to install: you add a url entry with an Authorization header to claude_desktop_config.json, .cursor/mcp.json, the Windsurf mcp_config.json, or VS Code Copilot settings. Authentication reuses your existing Kibo API credentials two ways: HTTP Basic with a Base64-encoded applicationKey:clientSecret pair from the Kibo Dev Center, or a short-lived JWT obtained from the Kibo OAuth endpoint at home.kibocommerce.com and sent as a Bearer token (roughly one hour, so your client needs refresh handling). The scale is the notable part — the default /mcp/admin/ path exposes over 500 operations, so Kibo lets you filter by appending comma-separated categories named {resource}.{operation}, such as products.read or categories.read,categories.update, which cuts both tool-discovery latency and the token cost of the tool list. Categories span Commerce Runtime (cart, checkout, order, quote, return, wishlist), Customer and B2B accounts, Product Admin (products, variations, price lists, discounts, search merchandizing and synonyms), Location and inventory, Shipping Admin, Pricing Runtime, and Import/Export. A separate documentation MCP server exists for querying Kibo docs. Debug tool calls with npx @modelcontextprotocol/inspector against the same URL.
Who built Kibo Commerce MCP Server?
Kibo Commerce MCP Server was built by Kibo Commerce.
Is Kibo Commerce MCP Server free?
Yes, Kibo Commerce MCP Server has a free option. This MCP server is free and open-source. Check the GitHub repository for details.
How do I install Kibo Commerce MCP Server?
Kibo Commerce MCP Server has no verified public repository, so there is no confirmed install command for it.
What does Kibo Commerce MCP Server integrate with?
Kibo Commerce MCP Server integrates with Claude Desktop, Cursor, VS Code, Windsurf.
No verified public repositoryVisit Website

Repo Health

Local install

Local/stdio install — runs on your machine, so there is no remote endpoint to verify live. Trust signal below is from the source repo.

Repo recency not yet available for this server.

Quick Info

Install Type
npm
Author
Kibo Commerce
Categories
2
Integrations
4

Related Servers

🌐

Fetch

Web content fetching and conversion for efficient LLM usage. Extract readable content from any URL.

Local
📋

Time

Time and timezone conversion capabilities for AI assistants.

Local
💻

21st.dev Magic

Create crafted UI components inspired by the best 21st.dev design engineers.

Local
🌍

Apify MCP Server

The Apify MCP server gives AI agents access to 6,000+ ready-made cloud scrapers, crawlers, and automation tools on the Apify Store — no infrastructure required. Connect to Apify Actors that extract data from social media platforms (Instagram, TikTok, LinkedIn), search engines (Google, Bing), e-commerce sites (Amazon, eBay), maps (Google Maps), and virtually any website. Each Actor runs in the cloud with managed proxies, browser fingerprinting, and anti-bot bypass built in. Use the Apify MCP server to query Actors by task, stream results directly into your AI context, run custom scraping Actors from your Apify account, and chain multiple data extraction steps in a single workflow. Supports tool filtering to expose only the Actors you need, and integrates with Apify's RAG web browser Actor for retrieval-augmented generation use cases.

Auth required
🌍

Browserbase MCP Server

Browserbase MCP and Stagehand MCP are the same server under two names, and this catalog lists both because people search for both — this page is the platform view, /servers/stagehand covers the natural-language automation layer that runs inside it. What Browserbase supplies is the browser itself: a headless Chrome session running in Browserbase's cloud rather than on the machine your agent is on, which is the reason to use it at all. The session is a real, addressable browser with its own residential-proxy and stealth configuration and a recorded replay you can watch afterwards, so an agent's browsing survives being run from a datacenter IP, and a failed run is debuggable after the fact instead of being a black box. Nothing renders on the developer's machine, so a long-running agent is not tied to a desktop staying awake. Browserbase's recommendation is the hosted server at https://mcp.browserbase.com/mcp over streamable HTTP — they operate it and absorb the model inference that the instruction-following tools require. Clients without HTTP transport connect via npx mcp-remote https://mcp.browserbase.com/mcp. Self-hosting installs @browserbasehq/mcp-server-browserbase from npm and needs BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID from your dashboard. Six tools are exposed — start and end for session lifecycle, navigate, act, observe and extract — and they are documented in detail on the Stagehand entry, because the act/observe/extract trio is Stagehand's model rather than Browserbase's. One thing to know before self-hosting: the browserbase/mcp-server-browserbase repository was archived on 2026-07-20 and its README now says it is kept for historical reference and should not be read as representative of the current production service. The npm package still installs and the star count on this page belongs to that archived repo; the hosted endpoint is the path Browserbase actually maintains.

Local

Sponsored

Better Stack

Free Plan

Get alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.

Start monitoring free →