Missive MCP server

What the model can do

Missive team inbox: conversations by mailbox, shared label, team, contact email or domain, a conversation's messages, internal comments and drafts, contacts, tasks, users, teams, labels and organizations. Can send or schedule an email, SMS or WhatsApp message, create a draft for review, close, reopen, assign, label, rename or move a conversation, merge two conversations, add an internal post, create a contact, create or update a task, and delete a draft or a post.

Reads

• missive_list_conversationsMissive conversations, most recent activity first: subject, who it is with, assignees, shared labels, team, message count and a link.
• missive_get_conversationOne Missive conversation with its latest messages (sender, date, subject and preview) and the team's internal comments.
• missive_list_contactsContacts in a Missive contact book: name, email, phone, company and title, notes.
• missive_list_tasksMissive tasks the token's user can see, most recent activity first: title, state (todo, in_progress, closed), due date, assignees…
• missive_list_usersPeople in the Missive organizations the token's user belongs to, with their ids (for task and assignee filters).
• missive_list_teamsMissive teams, with their ids for listing a team's conversations.
• missive_list_shared_labelsMissive shared labels (with their full path such as Clients/Globex), with their ids for listing the conversations under a label.
• missive_list_organizationsMissive organizations the token's user belongs to, with their ids (assigning, labelling and team tasks need one when there are several).
• missive_list_conversation_draftsDrafts in one Missive conversation, newest first: id, subject, preview, recipients, author and date.

Acts, when you ask

These change something in Missive. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• missive_add_postAdds an internal post to an existing Missive conversation, seen by the team in the conversation and never sent to the customer.
• missive_create_taskCreates a Missive task, either inside an existing conversation (conversation id) or standalone for a team or for named teammates.
• missive_create_contactCreates a contact in a Missive contact book, with a name and optionally an email, phone, company, job title and notes.
• missive_send_messageSends an email, SMS or WhatsApp message from one of the user's Missive accounts to the named recipients, now or at a scheduled time…
• missive_create_draftCreates a draft email, SMS or WhatsApp message in Missive, as a new conversation or a reply in an existing one…
• missive_update_conversationChanges one Missive conversation for everyone with access to it: close or reopen it, rename it, set its colour, assign or unassign teammates…
• missive_update_taskChanges a Missive task: title, description, state (todo, in_progress, closed), assignees (replaces the list), team or due date.
• missive_merge_conversationsMerges one Missive conversation into another, permanently: the source is marked as replaced and its messages…
• missive_delete_draftPermanently deletes a Missive draft, which also cancels it if it was scheduled to send.
• missive_delete_postPermanently deletes an internal post from a Missive conversation, for everyone.

Connect it

First connect Missive on Dashboard → Connections, then add Memtro to your client once. The Missive tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Missive connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › What conversations are open under the Clients/Acme label?
• › What has anyone at brightwave.co.uk sent us this month?
• › Which tasks are due this week, and who are they assigned to?
• › What did the team say internally about the Northwind contract?
• › Reply to the BigCo thread that the revised quote follows on Friday

Questions

Is this an official Missive MCP server?

No. It is Memtro's MCP server with Memtro's Missive connector behind it: the connector reads Missive through its API with the credentials you connect on Dashboard → Connections, and Missive publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Missive?

Only when you ask, and only what it has been granted: add an internal post to an existing conversation; create a contact in a contact book; create a task, in a conversation or for a team or teammates; send or schedule an email, SMS or WhatsApp message to named recipients, new or as a reply; create a draft message for a person to review and send from Missive; close, reopen, rename, recolour, assign, label or move a conversation; change a task's title, description, state, assignees, team or due date; merge one conversation into another, permanently; delete a draft, or cancel a scheduled send; delete an internal post from a conversation. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Email, calendar and chat

• AgentMail MCP server
• Gmail MCP server
• Google Calendar MCP server
• Slack MCP server
• Outlook Mail MCP server
• Outlook Calendar MCP server