Helpdesk
CM Mobile Service Cloud MCP connector
Connecting CM Mobile Service Cloud to Elaichi lets Claude, ChatGPT, Cursor, or any MCP client read your conversations, customers, orders, calls, and agent presence, and send messages or create records, all inside each person's own access.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect CM Mobile Service Cloud to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect CM Mobile Service Cloud once
-
Open Connections, choose Add connection, and pick CM Mobile Service Cloud.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a CM Mobile Service Cloud API key. One person generates a token in CM Mobile Service Cloud and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect CM Mobile Service Cloud to 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.
Connect CM Mobile Service Cloud to 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 today. The plugin directory lives at chatgpt.com/plugins.
Connect CM Mobile Service Cloud to 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.
Connect CM Mobile Service Cloud 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.
Use cases
What teams do with CM Mobile Service Cloud through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Catch up on a customer's open conversations
Ask for everything a customer has said across chat, WhatsApp, and email in CM Mobile Service Cloud before you reply, then send the answer from the same chat window.
-
Support
Reply to a waiting customer in plain language
Draft a reply, check it against the conversation history, and send it as a message in CM Mobile Service Cloud without switching screens.
-
Sales
Create a customer and an order after a call
When a call closes with a yes, add the new customer and their order to CM Mobile Service Cloud straight from your notes, with the order details filled in.
-
Order desk
Find an order and read its line items
Look up a customer's orders and order details in CM Mobile Service Cloud to answer where is my order questions without opening three tabs.
-
Team leads
See who is available right now
Check agent presence and recent voice calls in CM Mobile Service Cloud to spot a queue building up or a shift that is short-staffed.
-
Customer success
Spot your highest value customers
Pull customer lifetime figures from CM Mobile Service Cloud alongside recent conversations to decide who deserves a proactive check-in this week.
Try asking
- “Show open conversations from the last 24 hours.”
- “Which customers placed orders this week?”
- “Summarize voice call volume by agent presence today.”
AI tools
CM Mobile Service Cloud tools for your AI agents
14 tools are ready to call through Elaichi's MCP endpoint the moment you connect CM Mobile Service Cloud, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting CM Mobile Service Cloud gets you
6 screens from the product, each doing one job for your CM Mobile Service Cloud account.
The agent
Ask about conversations, get real answers.
Type a question in plain language and read live CM Mobile Service Cloud records.
- conversations
- orders
- customers
- messages
Ask Elaichi to work across your apps.
Show open conversations from the last 24 hours.
Which customers placed orders this week?
Summarize voice call volume by agent presence today.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor, one endpoint.
Reach CM Mobile Service Cloud over OAuth from any MCP client, no SDK required.
Copy the endpoint
Tool catalog
14 CM Mobile Service Cloud tools, ready now.
Conversations, orders, customers, presence and voice, covered without writing custom code.
- List all CM Mobile Service Cloud conversations
- Create a CM Mobile Service Cloud message
- Create a CM Mobile Service Cloud order
- List all CM Mobile Service Cloud orders
Toolboxes
Every team gets its own toolbox.
Support sees conversations, fulfilment sees orders, each toolbox scoped to one team.
- Support
- Fulfilment
- Customer Success
- Voice Operations
Shared connections
Share the connection, never the credential.
One person connects CM Mobile Service Cloud, teams and members work through it safely.
- Support EMEA
- Support APAC
- Fulfilment
- Voice Operations
Audit log
Answer who touched which conversation.
Every call is logged with time, person, action, type and resource.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, a digest ships.
Conversations are fetched, grouped, drafted by an agent, approved, then posted back.
CM Mobile Service Cloud digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch conversations
CM Mobile Service Cloud
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 Michael Brennan
Approve Deny -
Post the digest
CM Mobile Service Cloud
Queued
Collections and dashboards
Helpdesk numbers arrive before you ask.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
CM Mobile Service Cloud health
Refreshed 4 minutes ago · every 15 minutes · from the conversations collection
Conversations
1,284 ↓ 12%
Orders
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Conversations created
Last 14 days
By team
Share of activity
Support EMEA 34%
Support APAC 27%
Fulfilment 21%
Voice Operations 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect CM Mobile Service Cloud to Claude?
Connect CM Mobile Service Cloud in Elaichi by pasting the API key from your CM Mobile Service Cloud account, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. That is the whole setup. There is no OAuth application to register and no client ID or secret to generate.
Does CM Mobile Service Cloud work with ChatGPT and Cursor as well as Claude?
Yes. Once CM Mobile Service Cloud 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 CM Mobile Service Cloud once and every client uses it.
What can an AI agent actually do with my CM Mobile Service Cloud data?
With CM Mobile Service Cloud connected, an agent can read conversations, look up customers and their lifetime value, list orders and order details, check agent presence and voice calls, and search across all of it. It can also send a message in a conversation, create a customer, create an order, and register a call event. It can only do these things for the person who signed in, using that person's own access.
Does connecting CM Mobile Service Cloud give the AI access to every customer and conversation?
No. Access to CM Mobile Service Cloud follows the person who connected it, so the agent sees the conversations, customers, and orders that person's CM Mobile Service Cloud account already allows and nothing more. Elaichi can narrow that access further with restrictions, and it can never widen it beyond what CM Mobile Service Cloud itself permits.
Can I stop an agent from sending messages or creating orders in CM Mobile Service Cloud?
Yes. Restrictions in Elaichi work per action, so you can allow reading CM Mobile Service Cloud conversations and customers while blocking sending messages, creating customers, or creating orders. A blocked action is never shown to Claude, ChatGPT, or any other client at all, so no prompt can reach it.
What happens to a CM Mobile Service Cloud connection when someone leaves?
Offboarding a person in Elaichi ends their access to CM Mobile Service Cloud at once, across every client they used. If they were part of a shared CM Mobile Service Cloud connection, it keeps working for everyone else on the team. Disconnecting CM Mobile Service Cloud once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client in one step.
Put CM Mobile Service Cloud in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.