# Gambio MCP connector

The Gambio connector brings your store's categories, addresses, category images and country zones into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, where each person works inside their own access and every change is logged.

Source: https://elaichi.ai/connectors/gambio/

## Facts

| | |
| --- | --- |
| Application | Gambio |
| Category | Ecommerce |
| AI tools | 199 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Gambio is connected

- List the Gambio categories that changed this week.
- Show every product in the Winter sale category.
- Update the billing address for Müller GmbH to Hauptstrasse 12.

## Connect Gambio in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Gambio.
2. Optionally set Share with, then press Connect.
3. Paste a Gambio API key. One person generates a token in Gambio and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Gambio tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Gambio MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Gambio MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Gambio MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Gambio MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Gambio MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Gambio to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Gambio tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Gambio through Elaichi

### Reshape the category tree before a season

Merchandising. Create the new seasonal categories, move subcategories under them and update dozens of categories in one pass instead of clicking through the Gambio admin one at a time.

### Fix a customer address after a call

Customer service. Look up the address on file, correct the street or postcode the customer just gave you and confirm it back to them while they are still on the line.

### Refresh category images and icons in bulk

Content. Swap out dated category images and icons across the whole storefront in one request, and clear the ones that no longer belong.

### Pull every product in a category

Marketing. Ask for the full list of products sitting in a category to build a campaign, a newsletter block or a landing page without exporting a spreadsheet.

### Clean up stale and duplicate addresses

Operations. Find addresses that are duplicated or incomplete, decide which to keep and remove the rest, with every deletion recorded against the person who made it.

### Check country zones and address formats

Store admin. See which zones a country is split into and which address format Gambio applies, so checkout and shipping settings match the markets you actually serve.

## Elaichi vs Zapier MCP vs Composio for Gambio

All three can connect Gambio to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Gambio tools | Allow or restrict single Gambio tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Gambio call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Gambio to Claude?

Connect Gambio in Elaichi by pasting your Gambio API key, since Gambio connects with an API key and there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and Claude can start working with your Gambio categories and addresses.

### Does Gambio work with ChatGPT and Cursor as well as Claude?

Yes. Once Gambio is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Gambio once and every client picks it up.

### What can an AI agent actually do with my Gambio store?

An agent can list, search, create, update and delete Gambio categories, move subcategories around, update category images and icons in bulk and show which products sit in a category. It can also look up, create, correct and remove customer addresses, and check country zones and address formats. Short, concrete asks such as "show the subcategories under Outdoor" work better than long paragraphs.

### Does connecting Gambio give the AI access to my whole store?

No. Every call into Gambio runs as the person who signed in, so an agent can only reach what that person's Gambio API key already allows. Elaichi can narrow that access further with roles and restrictions, and it never widens it.

### Can my team share one Gambio connection?

Yes. One person connects Gambio with the store's API key and shares the connection with a team, and nobody else ever handles the credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every category or address change.

### Can I stop an agent from deleting or changing things in Gambio?

Yes. Restrictions in Elaichi apply per action, so you can restrict deleting Gambio categories or addresses for a role or for one person while leaving lookups open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it whatever the prompt says.

### What happens to a Gambio connection when someone leaves?

Offboarding a person in Elaichi ends their access to Gambio at once, across every client they used. A shared Gambio connection keeps working for everyone else on the team. If you want the store gone entirely, disconnecting Gambio once in Elaichi removes it from every client.

### Does the Gambio MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Gambio is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Gambio?

Yes. Both let Claude, ChatGPT or Cursor use Gambio. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Gambio call.

### How is Elaichi different from Composio for Gambio?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Gambio: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 199 Gambio tools

Every tool below is callable through https://api.elaichi.ai/mcp once Gambio is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Gambio address formats** (List). Get Address Formats. Get all address formats or a single address format.
- **Delete a Gambio address by ID** (Delete). Delete Address. Remove an address record from the system. This method will always return success even if the address record does not exist (due to internal architecture decisions, which strive to avoid unnecessary failures).
- **Get single Gambio address by ID** (Get). Get Address (Single). Get a single address record through a GET requets. This method supports all the GET parameters that are mentioned in the "Introduction" section of this documentation.
- **Update a Gambio address by ID** (Update). Update Address. Update an existing address record by providing new data. You do not have to provide the full presentation of the address in the JSON string of the request, rather just the fields to be updated. The address ID will be taken from the URI of the request so it is not required that it is included withing the request JSON.
- **List all Gambio addresses** (List). Get Addresses (Multiple). Get multiple address records through a GET request. This method supports all the GET parameters that are mentioned in the "Introduction" section of this documentation.
- **Create a Gambio address** (Create). Create Address. Create an address record for a customer in the system.
- **Delete a Gambio category by ID** (Delete). Delete Categories. Removes multiple category records from the database, provided a comma-seperated list of IDs to delete. The id may be a comma-separated list of IDs to delete several records at once.
- **List all Gambio categories** (List). Get Categories (Multiple). Get multiple category records through a GET request. This method supports all the GET parameters that are mentioned in the "Introduction" section of this documentation.

- **Create a Gambio category** (Create). Create Categories. Creates new categories in the system by taking an array of categories. It is also possible to provide a single GXCategory ressource, to create a single entry. Send a JSON array to create several categories at once.
- **Gambio categories bulk update** (Update). Update Category (Multiple). Use this method to update multiple existing category records. It takes an array of GXCategory Objects, updating them based on their id property. The request body is a JSON array of records. Returns {affected: [...], errors: [...]}.
- **Get single Gambio category by ID** (Get). Get Categories (Single). Get a single category record through a GET request. This method supports all the GET parameters that are mentioned in the "Introduction" section of this documentation.

- **Update a Gambio category by ID** (Update). Update Category. Use this method to update an existing category record. Take a look in the POST method for more detailed explanation on every resource property.

- **Gambio categories search** (Search). Search Categories. Body: {"search": &lt;condition&gt;}; the condition combines match, like, range, in, greater, lower, must (AND) and should (OR) operations on database table and column names (see the body schema).
- **List all Gambio category changes** (List). Change history of categories for a given date: returns {modified: [...], deleted: [{id, date}]} for records modified or deleted at the given date (Gambio types `changed` / `modified` / `deleted` as dates; whether it means on or since that date is unconfirmed). Send exactly one of changed (modified + deleted), modified or deleted.

- **List all Gambio category children** (List). Get Category Children. Get multiple or a single sub category records of a given category through a GET request. This method supports all the GET parameters that are mentioned in the "Introduction" section of this documentation.
- **Delete a Gambio category icon by ID** (Delete). Delete Category Icon. Removes the category icon file from the server. This method will always provide a successful response even if the image file was not found. The id is file name of the icon to delete (sent as filename).
- **List all Gambio category icons** (List). Get Category Icons. Returns a list of all category icon files which exists in the servers filesystem through a GET request.
- **Gambio category icons bulk update** (Update). Rename an image file on the server. Body: {oldFilename, newFilename}.
- **Delete a Gambio category image by ID** (Delete). Delete Category Image. Removes the category image file from the server. This method will always provide a successful response even if the image file was not found. The id is file name of the image to delete (sent as filename).
- **List all Gambio category images** (List). Get Category Images. Get a list of all category image files which exists in the server's filesystem through a GET request.
- **Gambio category images bulk update** (Update). Rename an image file on the server. Body: {oldFilename, newFilename}.
- **List all Gambio category products** (List). Get Category Products. Get multiple product records of an specified category through a GET request. Using the `recursive` query parameter allows you to receive the products from the sub categories.
- **Get single Gambio country by ID** (Get). Get Countries (Single). Get a single country. This method is currently limited to only fetching a single country resource so make sure that you provide the country ID in the request URI.
- **List all Gambio country zones** (List). Get Countries Zones. Get a single countrys zones. This method is currently limited to only fetching a single countrys zone resource so make sure that you provide the country ID in the request URI.
- **List all Gambio currencies** (List). Get all available currencies. Returns a collection of currencies. Uses Gambio REST API v3 (Gambio GX 4.1 or newer).
- **Get single Gambio currency by ID** (Get). Get a specific currency. Returns a single currency based in the provided ID. Uses Gambio REST API v3 (Gambio GX 4.1 or newer).
- **List all Gambio customer addon values** (List). Get all available customer addon values. Returns a collection of customer addon values. Uses Gambio REST API v3 (Gambio GX 4.1 or newer).
- **Gambio customer addon values bulk delete** (Delete). Delete all customer addon values. Deletes all addon values of a specified customer. Uses Gambio REST API v3 (Gambio GX 4.1 or newer).
- **Create a Gambio customer addon value** (Create). Create a new customer addon value. Creates a single or multiple new customer addon values based on the request body. Uses Gambio REST API v3 (Gambio GX 4.1 or newer). The request body is a JSON array of records.
- **Gambio customer addon values bulk update** (Update). Update an existing customer addon value. Updates a single or multiple customer addon value based on the request body. Uses Gambio REST API v3 (Gambio GX 4.1 or newer). The request body is a JSON array of records.
- **Get single Gambio customer addon value by ID** (Get). Get a specific customer addon value. Returns a single customer addon value based in the provided ID. Uses Gambio REST API v3 (Gambio GX 4.1 or newer).
- **Delete a Gambio customer addon value by ID** (Delete). Delete multiple customer addon values. Deletes one or more customer addon values based on the provided keys. Uses Gambio REST API v3 (Gambio GX 4.1 or newer). The id may be a comma-separated list of IDs to delete several records at once.
- **List all Gambio customer changes** (List). Change history of customers for a given date: returns {modified: [...], deleted: [{id, date}]} for records modified or deleted at the given date (Gambio types `changed` / `modified` / `deleted` as dates; whether it means on or since that date is unconfirmed). Send exactly one of changed (modified + deleted), modified or deleted.

- **Delete a Gambio customer group by ID** (Delete). Delete Customer Groups. Removes a customer groups record from the system. This method will always return success even if the customer group does not exist.
- **Get single Gambio customer group by ID** (Get). Get customer groups. Get multiple or a single customer groups record through the GET method
- **Update a Gambio customer group by ID** (Update). Updates CustomerGroup entity. Use this method if you want to update an existing customer groups record. Send the full record (names, settings, configurations); missing objects make Gambio fail with HTTP 500.
- **Create a Gambio customer group** (Create). Create CustomerGroups. This method enables the creation of a new CustomerGroups into the system.
- **List all Gambio customer memos** (List). Get all available customer memos. Returns a collection of customer memos. Uses Gambio REST API v3 (Gambio GX 4.1 or newer).
- **Gambio customer memos bulk delete** (Delete). Delete all customer memos. Deletes all memos of a specified customer. Uses Gambio REST API v3 (Gambio GX 4.1 or newer).
- **Create a Gambio customer memo** (Create). Create a new customer memo. Creates a single or multiple new customer memos based on the request body. Uses Gambio REST API v3 (Gambio GX 4.1 or newer). The request body is a JSON array of records.
- **Gambio customer memos bulk update** (Update). Update an existing customer memo. Updates a single or multiple customer memo based on the request body. Uses Gambio REST API v3 (Gambio GX 4.1 or newer). The request body is a JSON array of records.
- **Get single Gambio customer memo by ID** (Get). Get a specific customer memo. Returns a single customer memo based in the provided ID. Uses Gambio REST API v3 (Gambio GX 4.1 or newer).
- **Delete a Gambio customer memo by ID** (Delete). Delete multiple customer memos. Deletes one or more customer memos based on the provided IDs. Uses Gambio REST API v3 (Gambio GX 4.1 or newer). The id may be a comma-separated list of IDs to delete several records at once.
- **Delete a Gambio customer by ID** (Delete). Delete one or more customers. The id may be a comma-separated list of customer IDs.
- **List all Gambio customers** (List). List customers. Filter with type=guest or type=registree, search with q, sort with sort and trim the response with fields.
- **Create a Gambio customer** (Create). Create a customer (registered or guest). Send a new address inline or the addressId of an existing address. Set isGuest to true for a guest account; registered customers need a password. Required: gender, firstname, lastname, email and an address object (street, houseNumber, postcode, city, countryId, zoneId); registered customers also need password. Send a JSON array to create several.
- **Gambio customers bulk update** (Update). Update Customers (Multiple). Use this method to update multiple existing customer records. It takes an array of GXCustomer Objects, identified by their id property. The request body is a JSON array of records. Returns {updated: [...], errors: [...]}.

- **Get single Gambio customer by ID** (Get). Get a single customer record by ID.
- **Update a Gambio customer by ID** (Update). Update Customer. This method will update the information of an existing customer record. You will need to provide all the customer information with the request (except from password and customer id). Also note that you only have to include the "addressId" .
- **Gambio customers search** (Search). Search Customers. Body: {"search": &lt;condition&gt;}; the condition combines match, like, range, in, greater, lower, must (AND) and should (OR) operations on database table and column names (see the body schema).
- ...and 149 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
