Claude, ChatGPT, Codex, Cursor
Claude Code, Codex and Cursor connect with an API key; claude.ai and ChatGPT connect as a connector through “Allow”. After that the assistant works with your data in plain language: it finds, counts and suggests fixes.
Sales and customers department one of the departments in your AI company
MCP server and API for your online store
An MCP server lets an AI assistant read and change data in your software. The Elbuz MCP server gives Claude, ChatGPT, Codex or Cursor access to products, customers and orders with one employee’s permissions, and you approve every change in Pulse.
- MCP
- Claude
- ChatGPT
- Codex
- Cursor
- API v2
- Webhooks
What is an MCP server?
One standard for every AI assistant, with no separate integration for each.
MCP (Model Context Protocol) is an open standard that lets AI assistants plug into software. The MCP server is the software side of that plug: it tells the assistant which data and actions exist and carries out its requests. The assistant asks the Elbuz MCP server, the server answers with the data one employee is allowed to see, and any change comes back to you for approval: assistant ↔ MCP ↔ Elbuz.
- TransportStreamable HTTP: JSON-RPC requests over POST
- Sign-inan API key, or OAuth with an “Allow” screen
- Toolsdescribe, search, read, aggregate, create, update, run an action, search the help
- No deletingthe assistant cannot remove anything
Your AI assistant works with your store
An MCP server for ecommerce: your assistant gets access to Elbuz data without any development.
Catalog audit
Counts products without images, descriptions or prices, category by category.
Clean reference data
Finds duplicate attributes or manufacturers and suggests merging each pair.
Copy and edits
Writes short product descriptions — every edit waits for your “Accept”.
Safe by design: employee permissions and Pulse
The assistant sees only what one employee is allowed to see, and its changes go to Pulse first.
- A key on behalf of an employeethe assistant or app sees only what that employee is allowed to see
- Data scopelimits customers and documents the same way as in the app windows
- A new key is “Read only”writing has to be allowed separately
- Changes go through Pulseeach one arrives as “before → after” and waits for approval; only management can switch on “Act on its own”
What you can ask for
A few tasks the assistant does from a plain-language request.
- Find products without imagesby category
- Merge duplicate attributespair by pair
- Write short descriptionswith your “Accept”
- Order reportfor the day or the week
- Customers without follow-upthe list and tomorrow’s follow-ups
- Check stockwithout changing any data
API v2 for developers
An ecommerce API: your website, CMS or accounting system exchanges products, customers and orders with Elbuz.
API v2
Catalog, price lists, customers, documents, deals and the organizer — with one employee’s permissions; Bearer key, a limit of 120 requests per minute per key (MCP included), and changes read with a cursor so nothing is missed.
Website orders
POST /api/v2/orders/sync takes orders in batches of up to 100; a retry after a dropped connection does not create a duplicate (Idempotency-Key). OpenCart 3 has a ready-made module.
Webhooks
Elbuz notifies your server about changes to customers, documents and Pulse requests — in batches of up to 100; if your server is down, delivery is retried up to five times (six attempts in total).
What happens to the orders in Elbuz — order management.
Questions about the MCP server and the API
What is an MCP server?
MCP (Model Context Protocol) is an open standard that lets an AI assistant connect to software and work with its data. The MCP server is the software side: it tells the assistant which data and actions exist and carries out its requests. The Elbuz MCP server gives access to the catalog, price lists, customers, documents, deals and emails: you write in plain language, and the assistant finds, counts and suggests changes.
What is the difference between MCP and an API?
An API is an interface for programs: your website or accounting system exchanges data with Elbuz through requests described in the documentation. MCP is a layer for AI assistants: the assistant itself works out which data exists and what it can do with it, and acts on your instructions. In Elbuz both run under the same employee permissions and the same Pulse.
Which AI assistants can I connect?
Claude, ChatGPT, Codex and Cursor. Claude Code, Codex and Cursor connect with an API key; claude.ai and ChatGPT connect as a connector: no key needed, you just sign in to Elbuz and click “Allow” (OAuth).
Can the AI assistant break something in my store?
Not without your approval. The assistant works with the permissions of the employee the key was issued for, and a new key is created as “Read only”. If writing is allowed, every change waits for your approval in Pulse as “before → after” by default. Only management can switch on “Act on its own”, and a safeguard puts the key back into “Ask” mode after too many changes in an hour. The MCP server has no delete tool.
How do I send orders from my website to Elbuz through the API?
Your website, CMS or accounting system sends new orders and their updates with a POST /api/v2/orders/sync request, in batches of up to 100. New ones become “Customer order” documents, and orders already loaded are recognized and updated, so there are no duplicates.
What are the API limits?
120 requests per minute per key, and MCP assistant requests made with the same key count toward that limit. Orders are accepted in batches of up to 100; webhooks arrive in batches of up to 100, retried up to five times (six attempts in total) if your server is down. A key sees and changes only what its employee’s permissions allow.
What else your AI company can do
14 days free
Connect your AI assistant to Elbuz
Ready-made AI employees already work in your AI company — and with MCP your own assistant joins them. €50 on your balance after sign-up and 14 days to try it.