# Commslayer MCP connector

Connect Commslayer to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot, and any MCP client can read, open, update, and reply to Commslayer conversations and contacts as the signed-in person, with every call logged.

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

## Facts

| | |
| --- | --- |
| Application | Commslayer |
| Category | Ticketing |
| AI tools | 78 |
| 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 Commslayer is connected

- Summarize the last five messages in the conversation with Acme Corp.
- Draft a reply to every open conversation labeled billing.
- Which contacts have more than one open conversation this week?

## Connect Commslayer in Elaichi

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

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

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

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

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

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

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

### Catch up on a conversation before replying

Support. Ask for the full message history of a Commslayer conversation and get a plain summary of what the customer has said so far.

### Draft a reply and leave it for review

Support. Have the agent write a draft on a Commslayer conversation so a person can read it, edit it, and send it themselves.

### Find every open conversation for one account

Customer success. Search a customer's contact in Commslayer and pull up their open conversations ahead of a renewal call.

### Label and link related conversations

Support leads. Apply labels across a batch of Commslayer conversations and relate duplicates so one thread holds the whole story.

### Open a conversation from a handoff

Sales. When a prospect raises a support question, create a new Commslayer conversation and attach the contact so the support desk picks it up with context.

### Keep contact records clean

Operations. Find outdated or duplicate contacts in Commslayer, update the right one, and remove the stale one without opening the app.

## Elaichi vs Zapier MCP vs Composio for Commslayer

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

Connect Commslayer in Elaichi by pasting your Commslayer API key. 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. Sign in with your Elaichi account and Commslayer conversations and contacts are available in Claude.

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

Yes. Once Commslayer is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent. You connect Commslayer once and every client uses it.

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

It can list and search Commslayer conversations and contacts, read the messages in a conversation, write a draft reply, send a message, mark a conversation read, update its details, and apply labels. It can also create new conversations and contacts, link related conversations, and tidy contact records. Short, concrete asks, such as summarizing one conversation, work better than long instructions.

### Does connecting Commslayer give the AI access to every inbox?

No. Every call runs as the person who signed in, so the agent sees only the Commslayer accounts, conversations, and contacts that person can already open. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Commslayer already allows.

### Can my team share one Commslayer connection?

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

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

Yes. Restrictions in Elaichi work per action, so you can restrict deleting contacts or drafts in Commslayer for a role or for one person while leaving reading and drafting open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

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

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

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

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

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

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

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

## All 78 Commslayer tools

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

- **List all Commslayer account** (List). The token's account. The account the token belongs to, with its time zone. Any token may read it, whatever its scopes.
- **List all Commslayer conversations** (List). List conversations. Retrieve a paginated list of conversations. Token scope: conversations:read. Paged with a cursor (page[after] / meta.next_cursor), up to 100 per page.
- **Create a Commslayer conversation** (Create). Create conversation. Create a new conversation. Useful for routing inbound contact form submissions (e.g. Typeform, custom forms) into Commslayer. You can identify the contact by contact_id or by contact_email. When using contact_email, the contact will be found by email or created automatically. Optionally include a message object to create an initial message in the same request. Token scope: conversations:write. Required: conversation.
- **Get single Commslayer conversation by ID** (Get). Get conversation. Retrieve a specific conversation by ID. Pass id_type=display_id to look up by the display ID shown in the UI and webhook payloads. Token scope: conversations:read. Required: id. id is the conversation id.
- **Update a Commslayer conversation by ID** (Update). Update conversation. Update a conversation's status, assignee, or attributes. Pass id_type=display_id to look up by the display ID shown in the UI and webhook payloads. Token scope: conversations:write. Required: id, conversation. id is the conversation id.
- **Create a Commslayer conversation read** (Create). Mark conversation as read. Mark the conversation as read for every agent, as if each of them had opened it. Call it after your integration answers a customer, so the reply doesn't leave the conversation unread in the team's inbox. A later customer message makes it unread again. Pass id_type=display_id to look up by the display ID shown in the UI and webhook payloads. Token scope: conversations:write. Required: conversation_id.
- **List all Commslayer conversation messages** (List). List messages. Retrieve messages in a conversation. Token scope: messages:read. Required: conversation_id. Paged with a cursor (page[after] / meta.next_cursor), up to 100 per page.
- **Create a Commslayer conversation message** (Create). Send message. Send a new message in a conversation. Defaults to outgoing (agent) messages. You can create incoming messages (from the contact) by setting message_type to incoming. This works on any inbox type and is useful for routing external messages (e.g. from Make.com, Zapier, or contact form submissions) into conversations. Files. Token scope: messages:write. Required: conversation_id, message.
- **List all Commslayer conversation drafts** (List). Get draft. Retrieve the conversation's current unsent reply draft. Token scope: drafts:read. Required: conversation_id.
- **Create a Commslayer conversation draft** (Create). Create or replace draft. Write an unsent reply draft on the conversation. The agent sees it in the reply box, edits it and sends it like any other reply, so use this when a human should review the reply instead of sending it with the messages endpoint. A conversation holds one draft. Writing replaces whatever draft is there, including one Commslayer generated. Drafts written here do not count towards the account's AI drafts quota. Token scope: drafts:write. Required: conversation_id, draft.
- **Delete a Commslayer conversation draft by ID** (Delete). Delete draft. Remove the draft this API wrote. A draft that an earlier write replaced becomes the conversation's draft again, so deleting undoes the write rather than clearing the history. A draft Commslayer generated itself is not removable and returns 409. Token scope: drafts:write. Required: id. id is the conversation_id.
- **List all Commslayer conversation relations** (List). List relations. List all relations for a conversation. Relations link conversations together with types like triggered_by, duplicate_of, related_to, or follows_up. Required: conversation_id. Paged with a cursor (page[after] / meta.next_cursor), up to 100 per page.
- **Create a Commslayer conversation relation** (Create). Create relation. Create a relation linking this conversation to another conversation. Required: conversation_id, relation.
- **Delete a Commslayer conversation relation by ID** (Delete). Delete relation. Delete a relation between conversations. Required: id, conversation_id. id is the conversation_relation id.
- **Commslayer contacts search** (Search). Search contacts. Search for contacts by email, phone number, or identifier. Returns matching contacts without pagination. Token scope: contacts:read.
- **List all Commslayer contacts** (List). List contacts. Retrieve a paginated list of contacts. Token scope: contacts:read. Paged with a cursor (page[after] / meta.next_cursor), up to 100 per page.
- **Create a Commslayer contact** (Create). Create contact. Create a new contact. Token scope: contacts:write. Required: contact.
- **Get single Commslayer contact by ID** (Get). Get contact. Retrieve a specific contact by ID. Token scope: contacts:read. Required: id. id is the contact id.
- **Update a Commslayer contact by ID** (Update). Update contact. Update a contact's information. Token scope: contacts:write. Required: id, contact. id is the contact id.
- **Delete a Commslayer contact by ID** (Delete). Delete contact. Permanently erase a contact and the personal data linked to it: conversations, messages, notes, CSAT responses, customer profiles, synced Shopify customers and orders, and customer-portal auth records. Intended for GDPR right-to-erasure and similar data-removal requests. This cannot be undone. Token scope: contacts:delete. Required: id. id is the contact id.
- **List all Commslayer labels** (List). List labels. Retrieve all labels in the account. AI-related fields (ai_enabled, ai_prompt, ai_settings) are included in the response. Token scope: labels:read. Paged with a cursor (page[after] / meta.next_cursor), up to 100 per page.
- **Create a Commslayer label** (Create). Create label. Create a new label. AI-related fields (ai_enabled, ai_prompt, ai_settings, inbox_ids) can also be set. Token scope: labels:write. Required: label.
- **Get single Commslayer label by ID** (Get). Get label. Retrieve a single label by ID. Token scope: labels:read. Required: id. id is the label id.
- **Update a Commslayer label by ID** (Update). Update label. Update a label. AI-related fields (ai_enabled, ai_prompt, ai_settings, inbox_ids) can also be updated. Token scope: labels:write. Required: id, label. id is the label id.
- **Delete a Commslayer label by ID** (Delete). Delete label. Delete a label. Token scope: labels:write. Required: id. id is the label id.
- **List all Commslayer webhooks** (List). List webhooks. Retrieve all configured webhooks. Token scope: webhooks:manage. Paged with a cursor (page[after] / meta.next_cursor), up to 100 per page.
- **Create a Commslayer webhook** (Create). Create webhook. Create a new webhook endpoint. Token scope: webhooks:manage. Required: webhook.
- **Get single Commslayer webhook by ID** (Get). Get webhook. Retrieve a specific webhook. Token scope: webhooks:manage. Required: id. id is the webhook id.
- **Update a Commslayer webhook by ID** (Update). Update webhook configuration. Token scope: webhooks:manage. Required: id, webhook. id is the webhook id.
- **Delete a Commslayer webhook by ID** (Delete). Delete webhook. Delete a webhook. Token scope: webhooks:manage. Required: id. id is the webhook id.
- **Create a Commslayer webhook test** (Create). Test webhook. Send a test payload to the webhook endpoint. Token scope: webhooks:manage. Required: webhook_id.
- **Create a Commslayer webhook secret rotation** (Create). Rotate webhook secret. Generate a new secret for webhook signature verification. Token scope: webhooks:manage. Required: webhook_id.
- **List all Commslayer webhook delivery logs** (List). Get delivery logs. Retrieve recent webhook delivery logs. Token scope: webhooks:manage. Required: webhook_id.
- **List all Commslayer portals** (List). List portals. Retrieve a paginated list of active help center portals. Token scope: help_center:read. Paged with a cursor (page[after] / meta.next_cursor), up to 100 per page.
- **Create a Commslayer portal** (Create). Create portal. Create a new help center portal. Token scope: help_center:write. Required: portal.
- **Get single Commslayer portal by ID** (Get). Get portal. Retrieve a specific portal by slug. Token scope: help_center:read. Required: id. id is the portal slug.
- **Update a Commslayer portal by ID** (Update). Update portal. Update a portal's configuration. Token scope: help_center:write. Required: id, portal. id is the portal slug.
- **List all Commslayer portal categories** (List). List categories. Retrieve categories for a portal. Token scope: help_center:read. Required: portal_slug. Paged with a cursor (page[after] / meta.next_cursor), up to 100 per page.
- **Create a Commslayer portal category** (Create). Create category. Create a new category in a portal. Token scope: help_center:write. Required: portal_slug, category.
- **Get single Commslayer portal category by ID** (Get). Get category. Retrieve a specific category. Token scope: help_center:read. Required: id, portal_slug. id is the portal_categorie id.
- **Update a Commslayer portal category by ID** (Update). Update category. Update a category's details. Token scope: help_center:write. Required: id, portal_slug, category. id is the portal_categorie id.
- **Delete a Commslayer portal category by ID** (Delete). Delete category. Delete a category and nullify its articles' category references. Token scope: help_center:write. Required: id, portal_slug. id is the portal_categorie id.
- **List all Commslayer portal articles** (List). List articles. Retrieve articles for a portal. Content is not included in list responses for performance. Token scope: help_center:read. Required: portal_slug. Paged with a cursor (page[after] / meta.next_cursor), up to 100 per page.
- **Create a Commslayer portal article** (Create). Create article. Create a new article in a portal. Token scope: help_center:write. Required: portal_slug, article.
- **Get single Commslayer portal article by ID** (Get). Get article. Retrieve a specific article with full content. Token scope: help_center:read. Required: id, portal_slug. id is the portal_article id.
- **Update a Commslayer portal article by ID** (Update). Update article. Update an article's content or metadata. Token scope: help_center:write. Required: id, portal_slug, article. id is the portal_article id.
- **Delete a Commslayer portal article by ID** (Delete). Delete article. Delete an article. Token scope: help_center:write. Required: id, portal_slug. id is the portal_article id.
- **List all Commslayer response examples** (List). List response examples. Retrieve a paginated list of AI training response examples (question/answer pairs). Token scope: ai_training_responses:read. Paged with a cursor (page[after] / meta.next_cursor), up to 100 per page.
- **Create a Commslayer response example** (Create). Create response example. Create a new AI training response example. Token scope: ai_training_responses:write. Required: response_example.
- **Get single Commslayer response example by ID** (Get). Get response example. Retrieve a single response example by ID. Token scope: ai_training_responses:read. Required: id. id is the response_example id.
- ...and 28 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
