Missive MCP connector
Connect Missive to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot, or any MCP client can read shared inbox conversations, look up contacts, draft replies, and pull up saved responses, each person within their own Missive access, every action logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Summarize open Missive conversations labeled Billing from this week.
Working in Missive with Elaichi
-
List all Missive users
-
List all Missive teams
-
List all Missive organizations
How to connect Missive to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Missive 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.
Missive 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.
Missive 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.
Missive 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.
Missive 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 Missive 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 Missive through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Missive is logged.
-
Support
Catch up on a thread before replying
Ask for the full Missive conversation, every message and every internal comment, and get a short summary of where it stands and who last touched it.
-
Support
Draft a reply from a saved response
Have the agent find the right Missive response for the situation, adapt it to the customer's question, and leave it as a draft in the conversation for a person to check and send.
-
Sales
Update a contact after a call
Tell the agent what changed and it updates the Missive contact, new title, new number, new company, without anyone opening the contact book.
-
Sales
Find every conversation with an account
Ask for all Missive conversations involving a contact or a domain and get the history laid out in order, ready for a handover or a renewal call.
-
Operations
Pull attachments out of a shared inbox
Ask for the invoices or signed forms sitting in a Missive conversation and the agent downloads the attachments so they can be filed or forwarded.
-
Team leads
Set up labels for a new project
Describe the shared labels a new campaign or client needs and the agent creates them in Missive, or renames the old ones, so the team sorts mail the same way from day one.
Try asking
- “Summarize open Missive conversations labeled Billing from this week.”
- “Which Missive teams have the most unassigned conversations?”
- “Find the Missive contact behind yesterday's escalated conversation.”
What connecting Missive gets you
6 screens from Elaichi, each doing one job for your Missive account.
Ask Elaichi to work across your apps.
Summarize open Missive conversations labeled Billing from this week.
Which Missive teams have the most unassigned conversations?
Find the Missive contact behind yesterday's escalated conversation.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Missive conversations, get answers.
Plain language questions answered from live Missive conversations, contacts and shared labels.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Missive.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
32 Missive tools ready without custom code.
Conversations, messages, comments, contacts, labels and teams, each with listed methods.
Toolboxes
Every team gets its own Missive toolbox.
Support, sales and operations each work from a toolbox scoped to them.
Shared connections
Teammates use Missive without seeing credentials.
See who connected each Missive account and how many teams and members share it.
Audit log
Answer who touched which Missive conversation.
Append-only log of when, who, what happened, type and resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Missive digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch conversations
Missive
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
Missive
Queued
Automations
A schedule drafts your Missive digest.
Conversations are fetched, grouped, drafted by an agent, approved, then posted back to Missive.
Missive health
Refreshed 4 minutes ago · every 15 minutes · from the conversations collection
Conversations
1,284 ↓ 12%
Messages
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 AMER 27%
Sales 21%
Success 18%
Collections and dashboards
Missive numbers computed, not asked for.
Four metrics, 14 days of conversations created, and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Missive
All three can connect Missive 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 Missive tools | Allow or restrict single Missive 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 Missive 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.
Missive tools for your AI agents
32 tools are ready to call through Elaichi's MCP endpoint the moment you connect Missive, 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 Missive to Claude?
In Elaichi, choose Missive and paste in a Missive API key, which you create in Missive under your account settings; 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 the endpoint https://api.elaichi.ai/mcp. Sign in as yourself and Missive is available in Claude within a few minutes.
Does Missive work with ChatGPT and Cursor as well as Claude?
Yes. Once Missive is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Missive once and every client you use picks it up.
What can an AI agent actually do with my Missive data?
With Missive connected, an agent can read shared inbox conversations, their messages and internal comments, look up and update contacts, download attachments, find saved responses, create drafts, and create or rename shared labels. It can also list users, teams, and organizations so it knows who handles what. Missive has a lot of actions, so short, specific asks such as "summarize the thread with Acme from this week" work better than long instructions.
Can I stop an agent from deleting or changing things in Missive?
Yes. In Elaichi, restrictions on the Missive connection work per action, so you can allow reading conversations and contacts while restricting draft deletion, contact updates, or label changes. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.
What happens to a Missive connection when someone leaves?
Offboarding that person in Elaichi ends their access to Missive through every AI client at once. If the Missive connection was shared with a team, it keeps working for everyone else on the team. And if you ever want Missive gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client at the same time.
Does the Missive MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Missive 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 Missive?
Yes. Both let Claude, ChatGPT or Cursor use Missive. 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 Missive call.
How is Elaichi different from Composio for Missive?
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 Missive: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Missive 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