# PlentyONE MCP connector

The PlentyONE connector brings your PlentyONE accounts, contacts, addresses and address options to Claude, ChatGPT, Cursor and Microsoft Copilot through one governed endpoint, so each person works inside their own access with every action logged.

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

## Facts

| | |
| --- | --- |
| Application | PlentyONE |
| Category | Ecommerce |
| AI tools | 874 |
| 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 PlentyONE is connected

- Find every delivery address for the Müller account
- Which contacts have no billing address on file?
- List address options added to wholesale accounts this week

## Connect PlentyONE in Elaichi

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

1. Open Connections, choose Add connection, and pick PlentyONE.
2. Optionally set Share with, then press Connect.
3. Paste a PlentyONE API key. One person generates a token in PlentyONE 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 PlentyONE tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## PlentyONE 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.

## PlentyONE 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`.

## PlentyONE 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.

## PlentyONE 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.

## PlentyONE 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 PlentyONE 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 PlentyONE 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 PlentyONE through Elaichi

### Catch the account up after a call

Sales. Ask for a customer's contacts and addresses in PlentyONE before you dial, then add the new contact relation once the call is done.

### Check a customer's delivery address in seconds

Support. Pull up every address on a PlentyONE account while the customer is still on the line, and correct the one that is wrong.

### Clean up delivery addresses before dispatch

Logistics. Find PlentyONE addresses missing a house number or a phone number and fix them in bulk before parcels go out.

### Keep billing addresses matched to the right contact

Finance. Review which contacts are linked to a billing address in PlentyONE and update the relation when a customer's accounts team changes.

### Link store addresses to point of sale

Retail. Create or update the point of sale relation for a PlentyONE address when a new store opens or an existing one moves.

### Standardize how addresses are labeled

Operations. List the address option types in PlentyONE, add the ones your team is missing, and retire the ones nobody uses.

## Elaichi vs Zapier MCP vs Composio for PlentyONE

All three can connect PlentyONE 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 PlentyONE tools | Allow or restrict single PlentyONE 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 PlentyONE 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 PlentyONE to Claude?

Connect PlentyONE in Elaichi by pasting your PlentyONE API key, which takes about a minute. 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 as the endpoint. Sign in with your Elaichi account and PlentyONE is ready to use.

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

Yes. The PlentyONE connection in Elaichi is reached through the same endpoint, https://api.elaichi.ai/mcp, from Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect PlentyONE once and every client gets it.

### What can an AI agent actually do with my PlentyONE data?

An agent can look up the contacts and addresses on a PlentyONE account, add a new address or contact relation, update a phone number or a delivery address, and fix address details in bulk. It can also manage the address option types and point of sale relations your PlentyONE setup uses. Short, concrete asks such as find every delivery address for this account work better than long sentences.

### Does connecting PlentyONE give the AI access to everything in my account?

No. Every call to PlentyONE runs inside the access of the person who signed in to Elaichi, so an agent sees the accounts, contacts and addresses that person can already reach. Elaichi can narrow that access further with roles and restrictions, and it can never widen it.

### Can my team share one PlentyONE connection?

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

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

Yes. Restrictions in Elaichi work per action, so you can allow reading PlentyONE addresses while restricting deleting or bulk updating them, and you set a restriction on a role or on one person. A restricted PlentyONE tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

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

Offboarding a person in Elaichi ends their access to PlentyONE at once, from every client they used. A shared PlentyONE connection keeps working for everyone else on the team. If you disconnect PlentyONE in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.

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

Yes. PlentyONE 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 PlentyONE?

Yes. Both let Claude, ChatGPT or Cursor use PlentyONE. 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 PlentyONE call.

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

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 PlentyONE: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 874 PlentyONE tools

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

- **List all PlentyONE account address contact relations** (List). List address contact relations. Lists the address contact relations.
- **Create a PlentyONE account address contact relation** (Create). Create address contact relations. Creates an address contact relation.
- **PlentyONE account address contact relations bulk update** (Update). Update address contact relations. Updates an address contact relation.
- **Delete a PlentyONE account address contact relation by ID** (Delete). Delete address contact relation. Deletes an address contact relation. The ID of the address contact relation must be specified.
- **Get single PlentyONE account address contact relation by ID** (Get). Get address contact relation. Gets an address contact relation. The ID of the address contact relation must be specified.
- **List all PlentyONE account address option types** (List). List address option types. Lists the address option types.
- **Create a PlentyONE account address option type** (Create). Create address option type. Creates an address option type.
- **Delete a PlentyONE account address option type by ID** (Delete). Delete address option type. Deletes an address option type. The ID of the option type must be specified.
- **Get single PlentyONE account address option type by ID** (Get). Get address option type. Gets an address option type. The ID of the address option type must be specified.
- **Update a PlentyONE account address option type by ID** (Update). Update address option type. Updates an address option type. The ID of the option type must be specified.
- **Delete a PlentyONE account address option by ID** (Delete). Delete address option by option ID. Deletes an address option. The ID of the option must be specified.
- **Get single PlentyONE account address option by ID** (Get). Get address option. Gets an address option. The ID of the option must be specified.
- **Update a PlentyONE account address option by ID** (Update). Update address option. Updates an address option. The ID of the option must be specified.
- **PlentyONE account address options bulk delete** (Delete). Delete address option by addressId. Deletes an address option. The ID of the address must be specified.
- **List all PlentyONE account address options** (List). List address options. Lists address options. The ID of the address must be specified.
- **Create a PlentyONE account address option** (Create). Create address option. Creates an address option. The ID of the address must be specified.
- **PlentyONE account address options bulk update** (Update). Update address option by addressId. Updates an address option. The ID of the address must be specified.
- **List all PlentyONE account address pos relations** (List). List address POS relations. Lists the address POS relations.
- **Create a PlentyONE account address pos relation** (Create). Create address POS relation. Creates an address POS relation.
- **Delete a PlentyONE account address pos relation by ID** (Delete). Delete address POS relation. Deletes an address POS relation. The ID of the address POS relation must be specified.
- **Get single PlentyONE account address pos relation by ID** (Get). Get address POS relation. Gets an address POS relation. The ID of the address POS relation must be specified.
- **Update a PlentyONE account address pos relation by ID** (Update). Update address POS relation. Updates an address POS relation. The ID of the address POS relation must be specified.
- **List all PlentyONE account address related data** (List). Get address data by addressId. Gets the address data by the address ID. The ID of the address must be specified.
- **Get account address relation type application by ID** (Get). List address relation types. Lists address relation types. The application and the language must be specified. Possible applications: contact order warehouse pos
- **List all PlentyONE account address relation types** (List). List address relation types. Lists the address relation types.
- **Create a PlentyONE account address warehouse relation** (Create). Create address warehouse relation. Creates an address warehouse relation.
- **Delete a PlentyONE account address warehouse relation by ID** (Delete). Delete address warehouse relation. Deletes an address warehouse relation. The ID of the relation must be specified.
- **Update a PlentyONE account address warehouse relation by ID** (Update). Update address warehouse relation. Updates an address warehouse relation. The ID of the relation must be specified.
- **List all PlentyONE account addresses** (List). Get addresses. Get all available addresses
- **Create a PlentyONE account address** (Create). Create address. Creates an address.
- **Delete a PlentyONE account address by ID** (Delete). Delete address. Deletes an address. The ID of the address must be specified.
- **Get single PlentyONE account address by ID** (Get). Get address. Gets an address. The ID of the address must be specified.
- **Update a PlentyONE account address by ID** (Update). Update address. Updates an address. The ID of the address must be specified.
- **PlentyONE account batch delete bulk delete** (Delete). Delete Batch of Companies. Deletes multiple companies based on their IDs. The IDs of the companies must be specified.
- **List all PlentyONE account contact access data login URL** (List). Get login URL. Gets the URL to login as the given contact. The ID of the contact must be specified.
- **Account contact access data new password bulk update** (Update). Send password link for contact. Sends an email to a contact with a link to change the password. The ID of the contact must be specified.
- **Account contact access data set password bulk update** (Set). Update password for contact. Updates the password for a contact. The ID of the contact must be specified.
- **Account contact access data unblock user bulk update** (Unblock). Unblock contact. Unblocks a contact to allow this contact to log in again. The ID of the contact must be specified.
- **Create a PlentyONE account contact account** (Create). Create company for existing contact. Creates a company for an existing contact. The ID of the company must be specified. An account is equivalent to a company.
- **Delete a PlentyONE account contact account by ID** (Delete). Delete company of the contact. Deletes a company of the contact. The ID of the contact and the ID of the company must be specified. An account is equivalent to a company.
- **Get single PlentyONE account contact account by ID** (Get). Get company of the contact. Gets a company of the contact. The ID of the contact and the ID of the company must be specified. An account is equivalent to a company.
- **Update a PlentyONE account contact account by ID** (Update). Update company. Updates a company. The ID of the contact and the ID of the company must be specified. An account is equivalent to a company.
- **List all PlentyONE account contact address primary** (List). Get primary or last created addresses of contact. Gets primary or last created addresses of the contact. The ID of contact must be specified.
- **PlentyONE account contact address type primary bulk update** (Update). Set contact address per address type as primary address. Sets a contact address per address type as the primary address. The ID of the contact, the ID of the address and the ID of the address type must be specified. A primary address can also be defined when you create or update a contact address.
- **Account contact address type reset primary bulk update** (Update). Reset contact primary address. Resets the primary address of the contact. The ID of the contact, the ID of the address and the ID of the address type must be specified.
- **Create a PlentyONE account contact address** (Create). Create address for existing contact. Creates an address for a specific contact. The ID of the contact must be specified. When creating an address, the system checks for duplicates. If the system finds a duplicate, this address will be assigned to the contact data record.
- **Delete a PlentyONE account contact address by ID** (Delete). Delete address of the contact. Deletes an address of the contact. The ID of the contact and the ID of the address must be specified.
- **Update a PlentyONE account contact address by ID** (Update). Update address of the contact. Updates an address of the contact. The ID of the contact and the ID of the address must be specified. When updating an address, the system checks for duplicates if the address has more than one relation. If the system finds a duplicate, this address will be assigned to the contact data record. The update replaces the address: send name1, or name2/name3, together with the changed fields.
- **Get single PlentyONE account contact address by ID** (Get). List addresses that are linked with contacts. Lists addresses of the contact. The ID of the contact must be specified. If you specify page and itemsPerPage, you will get a paginated result. Otherwise you will get an array.
- **PlentyONE account contact anonymize bulk update** (Update). Anonymize contact. Anonymizes the contact by the given ID.
- ...and 824 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
