Skip to content

Helpdesk

Missive MCP connector

Connect Missive to Elaichi and Claude, ChatGPT, Cursor, 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.

  • 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 Missive to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Missive once

  1. Open Connections, choose Add connection, and pick Missive.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Missive API key. One person generates a token in Missive 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.

missive
Missive
Acquire
Ada
Atomicwork
CM Mobile Service Cloud
Crisp
2

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 Missive to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Missive to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Missive to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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 Missive to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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 Missive 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 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.”

See all 32 Missive tools below

AI tools

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.

See it in Elaichi

What connecting Missive gets you

6 screens from the product, each doing one job for your Missive account.

The agent

Ask about Missive conversations, get answers.

Plain language questions answered from live Missive conversations, contacts and shared labels.

  • conversations
  • messages
  • contacts
  • shared labels

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 or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Missive.

One governed MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

32 Missive tools ready without custom code.

Conversations, messages, comments, contacts, labels and teams, each with listed methods.

  • List all Missive users
  • List all Missive teams
  • List all Missive organizations
  • List all Missive conversations
ElaichiTools
Tool Action Description
List all Missive users List List users in organizations the authenticated user belongs to in Missive. Returns fields such as id, me, email, name, and avatar_url for each user.
List all Missive teams List List teams in Missive for a specific organization using organization. Returns team id, name, organization, active_members, and observers.
List all Missive organizations List List organizations the authenticated user is part of in Missive. Returns id and name for each organization in the response.
List all Missive conversations List Returns a list of conversations visible to the authenticated user in the Missive account. It must be filtered by the mailbox, shared label, or team. Each conversation includes its unique ID, subject, creation date, latest message subject, participants (users and external authors), message and attachment counts, associated organization and team details, the timestamp of the last activity, and direct URLs to access the conversation within Missive.
Get single Missive conversation by ID Get Get a specific conversation in Missive using id. May return a different id if the conversation was merged. Returns fields including latest_message_subject, organization, users, messages_count, and web_url.

Toolboxes

Every team gets its own Missive toolbox.

Support, sales and operations each work from a toolbox scoped to them.

  • Support
  • Sales
  • Success
  • Operations
ElaichiToolboxes
Name Source template Tools Created

Support toolbox

Missive · conversations and comments

Missive starter 18 Mar 4, 2026

Sales toolbox

Missive · contacts and inbound replies

9 Mar 2, 2026

Success toolbox

Missive · account conversations and labels

24 Feb 27, 2026

Operations toolbox

Missive · teams and shared labels

Missive starter 6 Feb 19, 2026

Finance toolbox

Missive · billing conversations and attachments

31 Jan 30, 2026

Leadership toolbox

Missive · volume and response reporting

12 Jan 22, 2026

Shared connections

Teammates use Missive without seeing credentials.

See who connected each Missive account and how many teams and members share it.

  • Support EMEA
  • Support AMER
  • Sales
  • Success
ElaichiConnections
Connection Scope Status Access
MI

Missive (Support EMEA)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
MI

Missive (Support AMER)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
MI

Missive (Sales)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
MI

Missive (Success)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
MI

Missive (Billing)

Connected by Clara Nowak

Personal • Active Not shared
MI

Missive (Operations)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Answer who touched which Missive conversation.

Append-only log of when, who, what happened, type and resource.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Missive Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Missive Conversations Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Missive Conversations List Toolbox

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 drafts your Missive digest.

Conversations are fetched, grouped, drafted by an agent, approved, then posted back to Missive.

Missive digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch conversations

    Missive

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Missive

    Queued

Collections and dashboards

Missive numbers computed, not asked for.

Four metrics, 14 days of conversations created, and a team breakdown, refreshed on schedule.

Missive health

Refreshed 4 minutes ago · every 15 minutes · from the conversations collection

Live

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%

FAQ

Frequently asked questions

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, 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.

Does connecting Missive give the AI access to every shared inbox?

No. Every request runs as the person who signed in, so an agent sees only the Missive conversations, contact books, and teams that person already has access to in Missive. Elaichi can narrow that further with restrictions, but it can never widen it beyond what the person could do in Missive themselves.

Can my team share one Missive connection?

Yes. One person connects Missive in Elaichi and shares the connection with a team, and nobody else ever sees or handles the Missive API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every Missive conversation read or contact updated.

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 blocking draft deletion, contact updates, or label changes. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt, however worded, can reach it.

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, and every other client at the same time.

Put Missive in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.