product / mcp server
MCP 2.0 is live
your store, ready for every agent
One MCP server for your whole commerce stack, on the same GraphQL contract as your storefront. Your customers’ AI assistants search, quote, order and return: signed in as them, within what they allowed.
Reorder last month’s sparkling water for the Utrecht warehouse. Same quantities.
Ready to order 3 lines for your company to the Utrecht warehouse, € 486.20 excl. VAT. This order will need approval. Shall I place it?
Yes, place it.
Placed. An approver at your company has to release it before it ships.
use cases
what you build on it
One server, many ways to sell. Your customers bring their own assistants, and you build your own channels on the same tools.
your shop, in the assistant they already use
Customers shop from Claude, ChatGPT or Copilot, at their desk or on the road. Voice works just as well as chat: the assistant calls the same tools, on the same account.
voice · in the car
“Order two more boxes of the A4 paper for the office, same as last time.”
“Two boxes of A4 copy paper, to the office address, € 58.90 excl. VAT. Shall I place it?”
“Yes.”
why one server
one contract, every channel
The MCP server sits on Evolve’s GraphQL contract, the same one your storefront uses. Whatever runs behind it, every channel gets the same prices, stock, promotions and rules.
channel
storefront
Your web shop, built on Evolve.
channel
AI shopping assistant
Chat on your storefront, acting through these same MCP tools.
channel · this page
your customers’ assistants
Claude, ChatGPT, Copilot and others, through the MCP server.
one GraphQL contract
same prices · same stock · same promotions · same approval rules
the patchwork
one MCP server per vendor
- The agent has to stitch vendors together itself, every time.
- Prices, stock and rules can drift from what your storefront shows.
- Swap a vendor and the agent’s tools change with it.
evolve
one MCP server on one contract
- Evolve combines the vendors, so the agent asks for what the customer wants.
- The same answers as your storefront and your AI shopping assistant.
- Swap a vendor and nothing changes for the agent.
compose your stack
any stack, the same tools
Pick the vendors behind your shop. The agent keeps calling the same tools, with the same inputs and the same answers. Only who answers changes.
Showing packages that ship in the framework today. Integrations proven in projects plug into the same contract.
| what the agent calls | answered by |
|---|---|
| get_products | searchAlgolia |
| get_product | catalogcommercetools |
| cart_line_items_add | cartcommercetools |
| get_checkout | checkoutcommercetools |
| order_place | orderscommercetools |
| order_pay | paymentAdyen |
| content_search | contentStoryblok |
tool contract unchangedsame 97 tools, same names, same shapes
86 integrations, one contract38 in the framework, 41 proven in projects, 7 on the roadmap
- Commerce engines
- Search & discovery
- Payments
- Content management
- Product content & media
- Address, company & tax
- Shipping & returns
- all integrations
control
every action, under control
Agents can do everything your shop can: catalogue, carts, orders, quotes, returns and company management. But customers decide which of it their assistant may use, and your approval rules always apply. Try it.
80of 97 tools
available
what may the assistant use?
Not signed in? Guests get Shopping only. Approvals and roles still apply to signed-in customers, whatever they allow.
Shopping
allowed- get_cartGet the current cart.
- cart_line_items_addAdd products to the cart.
- cart_line_items_updateChange quantities in the cart.
- cart_line_items_removeRemove lines from the cart.
- cart_bundle_addAdd a main product and its chosen extras as a bundle.
- cart_discount_code_addApply a discount code.
- cart_discount_code_removeRemove a discount code.
- get_checkoutWhat checkout needs, including whether the order will need approval.
- get_business_unit_addressesA company’s saved addresses, to pick shipping or billing.
- cart_set_shipping_addressSet where the order ships to.
- cart_set_billing_addressSet the invoice address.
- cart_set_shipping_methodChoose the shipping method.
- cart_set_payment_methodChoose how the order will be paid. Takes no money.
- cart_set_purchase_order_numberSet the buyer’s PO number for order and invoice.
- cart_set_vat_numberRecord the VAT number of the ordering company.
- cart_set_delivery_preferenceShip complete or split, and the requested delivery date.
- cart_set_delivery_slotChoose when the cart is delivered.
- cart_set_pickup_pointChoose where the cart is collected.
- cart_set_delivery_remarksA note for whoever delivers the goods.
- get_cartsThe company’s saved carts.
- cart_create_namedCreate a named cart and switch to it.
- cart_set_currentChoose which cart is the current one.
- cart_renameRename a cart.
- cart_deleteDelete a cart.
- cart_changes_acknowledgeMark the cart’s changes as seen by the buyer.
- cart_merge_undoUndo the cart merge that signing in made.
- cart_payment_removeRemove a reserved payment, such as a gift card.
confirm before commit
Tools that place, pay, cancel or change something instruct the agent to get the customer’s explicit yes first.
no double orders
Placing the same order twice returns the same order. A retrying agent can’t buy twice.
approvals stay approvals
Orders above your rules wait for an approver, and a buyer can never approve their own order.
get started
one URL, every assistant
Customers paste your server URL into the assistant they already use. They sign in on your shop and choose there what it may do. No client IDs, secrets or API keys to hand out.
try it on the Evolve B2B demo shop
https://mcp.azure-tst.evolve.labdigital.nl/mcp- 01add the server URLOne click in Claude, a few steps in ChatGPT and Copilot.
- 02sign in on the shopWith the account the customer already has.
- 03choose what it may useShopping, Account, Ordering and Company, one switch each.
no client ID, no secret
The server supports dynamic client registration and Client ID Metadata Documents, so every client that follows the MCP authorization spec connects straight away. Clients are public and secured with PKCE: there is never a secret to issue, store or rotate.
- dynamic client registration
- client ID metadata documents
- PKCE S256
- no client secrets
Or go to Settings › Connectors › Add custom connector and paste the server URL. Works in claude.ai, the desktop app and on mobile.
Any other client that follows the MCP authorization spec, such as VS Code or Cursor, connects the same way.
on the roadmap
what’s next: commerce you can tap
Today, agents answer in text. With MCP Apps, Evolve renders real interface right inside the conversation: pick a variant, set a quantity, approve an order. Same components, same rules as your storefront.
- product configurator
- variants, bundles, volume prices
- cart and checkout
- delivery slots, PO numbers
- approvals
- approve or reject in one tap
Show me the sparkling water in crates, and what 10 crates would cost.
questions
Your customers and their agents. It’s a sales channel, like your storefront and your apps, not a developer tool.
With every integration Evolve supports, in any combination. The tools sit on Evolve’s GraphQL contract, not on a vendor API, so we don’t bolt on vendors’ own MCP servers. Swap a vendor underneath and the agent doesn’t notice.
Yes. Prices, stock, roles and approval rules come from the same backend as your storefront. An agent can never do more than the customer who signed in, and orders above your rules still wait for an approver.
MCP Apps are coming soon. Everything you build on MCP 2.0 today carries over.
MCP 2.0 is stateless: no sessions and no session store, so any instance can answer any request. Run it in containers next to your storefront, and trace every tool call with OpenTelemetry.
Yes. By default every client that follows the MCP authorization spec may connect. An optional allowClient hook lets you admit only the clients you choose.
