# 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. Source: https://elaichi.ai/connectors/cmmobileservicecloud/ ## Facts | | | | --- | --- | | Application | CM Mobile Service Cloud | | Category | Helpdesk | | AI tools | 14 | | 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 CM Mobile Service Cloud is connected - Show open conversations from the last 24 hours. - Which customers placed orders this week? - Summarize voice call volume by agent presence today. ## Connect CM Mobile Service Cloud in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick CM Mobile Service Cloud. 2. Optionally set Share with, then press Connect. 3. 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which CM Mobile Service Cloud tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect CM Mobile Service Cloud 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 CM Mobile Service Cloud 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 CM Mobile Service Cloud 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 CM Mobile Service Cloud 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 CM Mobile Service Cloud 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 CM Mobile Service Cloud through Elaichi ### Catch up on a customer's open conversations Support. 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. ### Reply to a waiting customer in plain language Support. Draft a reply, check it against the conversation history, and send it as a message in CM Mobile Service Cloud without switching screens. ### Create a customer and an order after a call Sales. 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. ### Find an order and read its line items Order desk. 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. ### See who is available right now Team leads. 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. ### Spot your highest value customers Customer success. Pull customer lifetime figures from CM Mobile Service Cloud alongside recent conversations to decide who deserves a proactive check-in this week. ## 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 my team share one CM Mobile Service Cloud connection? Yes. One person connects CM Mobile Service Cloud in Elaichi and shares the connection with a team, so nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so every message sent or order created in CM Mobile Service Cloud is logged under the name of the person who asked for it. ### 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. ## All 14 CM Mobile Service Cloud tools Every tool below is callable through https://api.elaichi.ai/mcp once CM Mobile Service Cloud is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all CM Mobile Service Cloud conversations** (List). Retrieve conversations from CM's Agent Inbox helpdesk system, optionally filtered by email address, order number, or conversation identifier. Returns: guid. All filter parameters are optional. - **Create a CM Mobile Service Cloud message** (Create). Send a message via a custom channel in cm Mobile Service Cloud. Returns a 201 Created response with no documented response body. Required: ChannelAccountExternalIdentifier, ConversationExternalIdentifier, MessageExternalIdentifier, RelationExternalIdentifier, RelationName, Content, Attachments. - **Create a CM Mobile Service Cloud order** (Create). Create or update orders in CM Mobile Service Cloud by submitting an orders array. Reusing an existing order_number updates the order instead of creating a new one. Returns: orders. Required: orders. - **List all CM Mobile Service Cloud orders** (List). List orders for a customer in CM Mobile Service Cloud. Returns: order_number, list_view, email_address, phone_number, revenue, old_revenue, profit, old_profit, order_date, is_first_order, webstore_url, name. At least one of $EmailAddress or $PhoneNumber is required. - **CM Mobile Service Cloud voip register event** (Action). Register a VoIP event in cm to signal call lifecycle changes such as Answered, Disconnected, or Transfer. Returns the registered event including Id, EventType, PhoneNumber, PhoneExtension, Direction, PhoneReferrer, and Context with FilterField and FilterValue. Required: api_key, Id, EventType, PhoneNumber, PhoneExtension, Direction. - **List all CM Mobile Service Cloud presence** (List). Check presence for a specific written channel in cm. Returns: Online or Offline, indicating whether at least one agent connected to the channel within the web store is online. Required: Channel. - **List all CM Mobile Service Cloud voice** (List). List Voice queue and workforce status from cm Agent Inbox for a specific webstore. Returns: webStoreOpen, activeAgents, availableAgents, numberOfQueuedCalls, longestWaitingQueuedCallDateTime, longestWaitingQueuedCallInSeconds. Required: referrer. - **List all CM Mobile Service Cloud customers** (List). Get customer information in CM Mobile Service Cloud by email, phone, or custom filter. Returns: name, email_address, phone_number, customer_since, total_spent, order_count, panel_view. At least one of email_address or phone_number is required. - **Create a CM Mobile Service Cloud customer** (Create). Create or update customer lifetime data in CM by submitting a customers array. Each customer record includes email_address, customer_since, order_count, currency, total_revenue, and last_order_date. Returns an empty 201 response on success. Required: customers. - **List all CM Mobile Service Cloud order details** (List). Get detailed information about a specific order in CM for display in the Agent Inbox sidebar. Returns: display_as, caption, data. Required: id (the order_number from the order list). - **CM Mobile Service Cloud search search** (Search). Search for customers and orders in CM matching an agent's search expression. Returns matching customers (email_address, name, phone_number, order_count, total_spent) and orders (email_address, order_number, order_date, revenue, name). Required: expression. - **List all CM Mobile Service Cloud custom panel** (List). List custom panel items for a customer in CM. Returns: id, description, custom_field. At least one of email_address, phone_number, or external_identifier is required. - **Get single CM Mobile Service Cloud custom panel by ID** (Get). Get custom panel details for a specific item in CM. Returns: display_as, caption, data. Required: id. - **List all CM Mobile Service Cloud customer lifetime** (List). Retrieve customer lifetime data (total orders and revenue) for a specific customer by email in CM. Returns: email_address, customer_since, order_count, currency, total_revenue, last_order_date. Required: email_address.