Superconductor Docs

Missive

Connect Missive so agents can search your team inbox, reply to conversations, and keep them organized.

The Missive connector in Workspace Settings, for searching and replying to conversations and managing labels, tasks, and calendar events, with a Connect button

The Missive MCP server lets agents work in your Missive inbox, so they can read what customers wrote and reply while they work on related tickets.

For use cases and example prompts, see Missive for AI coding agents.

What is Missive?

Missive is a team inbox that brings email, SMS, WhatsApp, and other channels into one place, so teammates can share, assign, and discuss conversations.

What agents can do

Once you connect Missive, agents can:

  • Search conversations across your accounts and read full threads
  • Reply to conversations and start new ones
  • Add labels, internal notes, and tasks, and assign or close conversations
  • Look up contacts, teammates, and canned responses
  • Check your calendars, and create, update, or delete events

Agent changes in Missive take effect right away, without Missive's in-app confirmation. If you approve Send messages, agents can send messages as you. To review every reply first, uncheck it so agents can only write drafts.

Setup

Missive connects by signing in with your Missive account. There's no API key to create, and its MCP server doesn't accept Missive API tokens.

A Missive admin has to turn on MCP access first.

Go to Workspace Settings → Connectors (or a project's Connectors page) and click Connect on the Missive card (or Connect another to add another account).

Step 1: who the connection is for

Choose Me or Workspace as the owner, then choose which agents can use the connection. The default is Me, with My personal assistants selected. Enable Agents in projects separately and choose In all projects, including future ones or In some projects. Anyone with access to those projects can use the connection, including in sessions they launch themselves. See connection options for what each choice means.

Click Continue.

Step 2: sign in with Missive

Click Continue to Missive. Uncheck any permissions you don't want agents to have; Missive won't give them those tools. Check I recognize and trust this URL, then click Approve, and you land back on the Connectors page with Missive connected.

Agents then act in Missive as whoever signed in, in every Missive organization that person belongs to. If you enable Agents in projects, anyone with access to those projects can use that account — so sign in with an account whose permissions you're happy to share.

To change permissions later, disconnect and connect again with a different selection. Connect each Missive account only once: connecting it again ends its earlier connection, which then shows Reconnect needed.

Reconnecting and disconnecting

If an account connection stops working, the Connectors page shows a Reconnect needed badge on it, and agents run without Missive.

To fix it, click Manage next to the connection, then Reconnect Missive, and sign in again. You can only reconnect a personal connection you own; for someone else's, Superconductor tells you who to ask.

Disconnect also revokes Superconductor's access at Missive. If Missive doesn't confirm the revocation, Superconductor tells you to remove Superconductor from Settings → Login & Security → Connected apps in Missive to finish the job.

When to use it

Ask agents to use Missive when a ticket starts from a customer email, or when you want replies written or your inbox triaged. For example:

Find this week's Missive conversations about the checkout timeout, summarize what customers reported, and fix the bug in this repo.
Draft a reply in Missive to the latest email about the CSV export bug saying the fix ships Friday. Leave it as a draft for me to review.
Add a task to each unanswered refund request in Missive from this week, with an internal note saying who should reply.
Summarize this week's conversations in our Support team inbox in Missive by theme, for our weekly report.

On this page