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.
- Connects with an API key
- Free 14-day trial
- No credit card
Summarize the last five messages in the conversation with Acme Corp.
Working in Commslayer with Elaichi
-
List all Commslayer account
-
List all Commslayer conversations
-
Get single Commslayer conversation by ID
How to connect Commslayer to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Commslayer 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.
Commslayer 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.
Commslayer 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.
Commslayer 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.
Commslayer 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 Commslayer 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 Commslayer through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Commslayer is logged.
-
Support
Catch up on a conversation before replying
Ask for the full message history of a Commslayer conversation and get a plain summary of what the customer has said so far.
-
Support
Draft a reply and leave it for review
Have the agent write a draft on a Commslayer conversation so a person can read it, edit it, and send it themselves.
-
Customer success
Find every open conversation for one account
Search a customer's contact in Commslayer and pull up their open conversations ahead of a renewal call.
-
Support leads
Label and link related conversations
Apply labels across a batch of Commslayer conversations and relate duplicates so one thread holds the whole story.
-
Sales
Open a conversation from a handoff
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.
-
Operations
Keep contact records clean
Find outdated or duplicate contacts in Commslayer, update the right one, and remove the stale one without opening the app.
Try asking
- “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?”
What connecting Commslayer gets you
6 screens from Elaichi, each doing one job for your Commslayer account.
Ask Elaichi to work across your apps.
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?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about any Commslayer conversation in plain language.
Get answers from live Commslayer conversations, contacts, and labels without opening the inbox.
Copy the endpoint
AI apps
One endpoint brings Commslayer to every MCP client.
Claude, ChatGPT, and Cursor reach Commslayer through one governed endpoint, no SDK, no shared key.
Tool catalog
78 Commslayer tools, ready without writing code.
Conversations, messages, drafts, contacts, labels, and relations, covered from the first day.
Toolboxes
Every team gets its own Commslayer toolbox.
Support, success, and sales each see the Commslayer tools their work needs.
Shared connections
Share a Commslayer connection, never the API key.
Teammates work through a connection you own without ever seeing the credential.
Audit log
Know who touched every Commslayer conversation.
Every call lands in an append-only log with who, what, when, and which record.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Commslayer digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch conversations
Commslayer
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
Commslayer
Queued
Workflows
A schedule starts the work, a person approves.
Open Commslayer conversations are fetched, grouped, drafted into a digest, approved, and posted back.
Commslayer health
Refreshed 4 minutes ago · every 15 minutes · from the conversations collection
Conversations
1,284 ↓ 12%
Contacts
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 Americas 27%
Customer success 21%
Sales 18%
Collections and dashboards
Commslayer health, computed on a schedule, no prompting.
Conversations created over 14 days and a breakdown by team, with no model in the math.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Commslayer tools for your AI agents
78 tools are ready to call through Elaichi's MCP endpoint the moment you connect Commslayer, 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 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 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.
Put Commslayer 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