# Malomo MCP connector

The Malomo connector brings orders, customers, tracking lookups, order events and webhooks into Claude, ChatGPT, Cursor and any MCP client, so your team can find a shipment or update a record by asking, inside their own Malomo access.

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

## Facts

| | |
| --- | --- |
| Application | Malomo |
| Category | Ecommerce |
| AI tools | 21 |
| Authentication | Connects with an API key |
| Needs your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | Yes |

## What you can ask once Malomo is connected

- Which Malomo orders shipped this week without tracking updates?
- Show customers with more than two Malomo orders open.
- Create a Malomo order for customer 4821.

## Connect Malomo in Elaichi

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

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

## Connect Malomo to 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.

## Connect Malomo to 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 today. The plugin directory lives at chatgpt.com/plugins.

## Connect Malomo to 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.

## Connect Malomo 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

Only Read is granted by default, which is not enough to call a Malomo tool. 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. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Malomo through Elaichi

### Find the order behind a tracking code

Support. A customer pastes a tracking code into a chat. Look the order up in Malomo by tracking code, order number or your own reference, and see where it is before you reply.

### Catch the customer record up after a call

Support. When a shopper changes their email or phone during a delivery call, update their Malomo customer record right away so the next shipping notification reaches them.

### Log what happened to a shipment

Operations. Record an order event in Malomo when a carrier confirms a redelivery or a package is reshipped, so the tracking page tells the customer the full story.

### Review the day's shipments in one list

Operations. Pull the list of Malomo orders, ask which ones have stalled or thrown an exception event, and hand the short list to whoever calls the carrier.

### See how shoppers use tracking pages

Marketing. List customer events in Malomo to see who opened tracking pages or notifications, then decide which post-purchase messages deserve another look.

### Keep other systems in step with Malomo

Ecommerce. Create or update a Malomo webhook so your help desk or warehouse tool hears about new orders and delivery events without anyone rekeying them.

## Frequently asked questions

### How do I connect Malomo to Claude?

Connect Malomo in Elaichi first, which means pasting the API key from your Malomo account into the connection form; 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 to Elaichi when Claude asks, and Malomo orders and customers are available in your next conversation.

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

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

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

An agent connected to Malomo can list and look up orders by order number, tracking code or your own reference, create and update orders and customers, and read the events attached to each order or customer. It can also add an order event, such as a reshipment note, and create or manage the webhooks that tell your other systems about Malomo activity. In practice that means asking where a shipment is, fixing a customer's contact details, or pulling the list of orders with delivery problems, all in plain language.

### Does connecting Malomo give the AI access to every order and customer?

Access follows the Malomo API key used for the connection, so the AI can see and change only what that key already allows in Malomo. Elaichi can narrow that further, for example to reading orders but never deleting them, and it can never widen it beyond what Malomo itself permits. Every call is recorded in an audit log that names the person who made it.

### Can my team share one Malomo connection?

Yes. One person connects Malomo in Elaichi with the API key, then shares the connection with a team, and nobody else ever handles or sees that key. Each teammate still signs in to Elaichi as themselves, so the audit log shows exactly who looked up which Malomo order or changed which customer.

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

Yes. Restrictions in Elaichi apply per action, so you can allow reading Malomo orders and customers while blocking deletion, updates or webhook changes. A blocked action is never shown to Claude, ChatGPT or any other client at all, so no prompt, however worded, can reach it.

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

Offboarding that person in Elaichi ends their access to Malomo at once, from every client they used. If they had shared a Malomo connection with a team, it keeps working for everyone else. When you eventually want the connection gone, disconnecting Malomo once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.

## All 21 Malomo tools

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

- **List all Malomo orders** (List). List malomo orders with optional filters. Returns: id, alternate_id, email, number, customer, shipments, created_at, updated_at, meta. Filter by alternate_id, tracking_code, number, or customer_email.
- **Get single Malomo order by ID** (Get). Get a single malomo order by id. Returns: id, alternate_id, email, number, customer, shipments, created_at, updated_at, meta. Required: id.
- **Create a Malomo order** (Create). Create a new order in malomo. Returns: id, alternate_id, email, number, customer, shipments, created_at, updated_at, meta.
- **Update a Malomo order by ID** (Update). Update a malomo order by id. Returns: id, alternate_id, email, number, customer, shipments, created_at, updated_at, meta. Required: id. The shipments field must be a complete list — any existing carrier/tracking_code pairs not included will be removed.
- **Delete a Malomo order by ID** (Delete). Delete a malomo order by id. Returns an empty 204 response on success. Required: id.
- **List all Malomo customers** (List). List customers in malomo. Returns: id, email, first_name, last_name, phone_number, created_at, updated_at.
- **Get single Malomo customer by ID** (Get). Get a single malomo customer by id. Returns: id, email, first_name, last_name, phone_number, created_at, updated_at. Required: id.
- **Create a Malomo customer** (Create). Create a new customer in malomo. Returns: id, email, first_name, last_name, phone_number, created_at, updated_at.
- **Update a Malomo customer by ID** (Update). Update an existing malomo customer by id. Returns: id, email, first_name, last_name, phone_number, created_at, updated_at. Required: id.
- **Delete a Malomo customer by ID** (Delete). Delete a malomo customer by id. Returns an empty 204 response on success. Required: id.
- **Create a Malomo webhook** (Create). Create a new Malomo webhook to receive event notifications. Returns: id, active, topic, url, created_at, updated_at.
- **List all Malomo webhooks** (List). List all Malomo webhooks. Returns: id, active, topic, url, created_at, updated_at.
- **Get single Malomo webhook by ID** (Get). Get a single Malomo webhook by id. Returns: id, active, topic, url, created_at, updated_at. Required: id.
- **Update a Malomo webhook by ID** (Update). Update an existing Malomo webhook by id. Returns: id, active, topic, url, created_at, updated_at. Required: id.
- **Delete a Malomo webhook by ID** (Delete). Delete a Malomo webhook by id. Returns an empty 204 response on success. Required: id.
- **Get single Malomo orders by alternate ID by ID** (Get). Get a malomo order by its alternate ID. Returns: id, alternate_id. Required: alternate_id.
- **Get single Malomo orders by tracking code by ID** (Get). Get malomo orders by tracking code. Returns: tracking_code. Required: tracking_code.
- **Get single Malomo orders by number by ID** (Get). Get malomo orders filtered by order number or customer email. Returns: number, customer_email.
- **List all Malomo order events** (List). List all events for a specific order in malomo. Returns: id, order_id. Required: order_id.
- **Create a Malomo order event** (Create). Create a new event for a specific order in malomo. Returns: id, order_id. Required: order_id.
- **List all Malomo customer events** (List). List events for a malomo customer. Returns a collection of event records including id. Required: customer_id.