RepZio MCP connector
The RepZio connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent look up products, orders, customers, and ship-to addresses in RepZio, write new orders and line items, and keep product sets current, with each person working inside their own RepZio access.
- Connects with an API key
- Free 14-day trial
- No credit card
Show me RepZio orders created this week
Working in RepZio with Elaichi
-
List all RepZio misc
-
RepZio misc list 2
-
Get single RepZio shipto by ID
How to connect RepZio to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
RepZio MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
RepZio MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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.
RepZio MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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.
RepZio MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
RepZio MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect RepZio to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with RepZio through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in RepZio is logged.
-
Sales
Write the order right after the showroom visit
A rep reads out what the buyer picked, and the agent creates the RepZio order, adds the line items, and picks the right ship-to address before the rep leaves the building.
-
Sales
Check stock and pricing before quoting
Ask what a product costs, what the minimum is, and what else sits in the same product set, and get the answer from the RepZio catalog while the buyer is still on the phone.
-
Sales operations
Pull every order from this week's show
List the RepZio orders written over the show dates, grouped by rep and by account, so the recap is ready Monday morning without exporting anything by hand.
-
Merchandising
Keep the catalog current for the season
Add new RepZio products, update prices and descriptions on existing ones, and build the product sets reps will show on the floor, all from one conversation.
-
Customer service
Answer a retailer asking about their order
Look up the RepZio order by number, read back the line items and the ship-to address, and add a missing item if the retailer asks for one.
-
Operations
Get orders moving to the ERP
Update the export status on RepZio orders once they have been sent downstream, so nobody re-keys an order or pushes the same one twice.
Try asking
- “Show me RepZio orders created this week”
- “Which shiptos have no orders this quarter?”
- “Summarize order totals by team for last month”
What connecting RepZio gets you
6 screens from Elaichi, each doing one job for your RepZio account.
Ask Elaichi to work across your apps.
Show me RepZio orders created this week
Which shiptos have no orders this quarter?
Summarize order totals by team for last month
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about RepZio orders in plain language.
Three starter prompts pull answers from live RepZio orders, shiptos and customers.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach RepZio.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
80 RepZio tools arrive ready to call.
Orders, shiptos, merges and misc records, with no custom code to write.
Toolboxes
Every team gets its own RepZio toolbox.
Curate one toolbox per team and scope it to the work they do.
Shared connections
Reps use RepZio without seeing credentials.
The connections table shows who connected each account and which teams share it.
Audit log
Every RepZio order change has a name.
When, who, what happened, type and resource, in an append only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
RepZio digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch orders
RepZio
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
RepZio
Queued
Automations
A schedule drafts your RepZio order digest.
Six steps fetch orders, group them, draft a digest, await approval, post back.
RepZio health
Refreshed 4 minutes ago · every 15 minutes · from the orders collection
Orders
1,284 ↓ 12%
Shiptos
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Orders created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales North America 27%
Customer service 21%
Operations 18%
Collections and dashboards
RepZio order health, counted not guessed.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for RepZio
All three can connect RepZio 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.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over RepZio tools | Allow or restrict single RepZio 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 RepZio 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
RepZio tools for your AI agents
80 tools are ready to call through Elaichi's MCP endpoint the moment you connect RepZio, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect RepZio to Claude?
Connect RepZio in Elaichi first, which means pasting your RepZio API key into the connection form, since RepZio connects with an API key rather than a sign-in screen. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi once, and RepZio is available from then on.
Does RepZio work with ChatGPT and Cursor as well as Claude?
Yes. Once RepZio 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 RepZio once and every client you use picks it up.
What can an AI agent actually do with my RepZio data?
With RepZio connected, an agent can look up products and pricing, list and read orders, find a customer's ship-to addresses, create new orders and add line items, and add or update products and product sets. RepZio has a large set of actions, so the agent searches for the right one as it works, and short concrete asks such as "list orders for Acme from last week" work better than long paragraphs.
Does connecting RepZio give the AI access to every order and every account?
No. Every request runs under the RepZio API key of the person who connected, so the agent can only see the orders, products, and customers that key already reaches in RepZio. Elaichi can narrow that further by restricting specific actions for a role, but it can never widen access beyond what RepZio itself allows.
Can I stop an agent from deleting or changing things in RepZio?
Yes. Restrictions in Elaichi work per action, so you can allow reading RepZio orders and products while restricting creating orders, removing line items, or changing product records. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, or any other client cannot run it, whatever the prompt says.
What happens to a RepZio connection when someone leaves?
When you offboard a person in Elaichi, their access to RepZio through every client ends at once. If they were using a shared RepZio connection, it keeps working for everyone else on the team. If you want RepZio gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client together.
Does the RepZio MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. RepZio 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 RepZio?
Yes. Both let Claude, ChatGPT or Cursor use RepZio. 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 RepZio call.
How is Elaichi different from Composio for RepZio?
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 RepZio: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put RepZio in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot