← All integrations

Missive MCP server

42 operations0 webhooks

Team inbox integration for conversations, contacts, drafts, messages, tasks, teams, and analytics reports.

Try Missive with your agent

Connect Missive, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Missive on my account, then run one read-only example and show me the result.

Runs once, when you ask

Missive tools and triggers

Tools are what your agent can do in Missive through Corsair's MCP server. Triggers are the Missive events a routine can start from.

Conversations

  • GetRead-only

    Fetch a conversation by id; a merged old id answers with the current conversation

    conversations.get

  • ListRead-only

    List conversations of one mailbox, shared label, or team, newest activity first

    conversations.list

  • List CommentsRead-only

    List the internal comments of a conversation, newest first

    conversations.listComments

  • List DraftsRead-only

    List the draft messages of a conversation, newest first

    conversations.listDrafts

  • List MessagesRead-only

    List the messages of a conversation, newest first; drafts are excluded

    conversations.listMessages

  • List PostsRead-only

    List the posts of a conversation, newest first

    conversations.listPosts

  • MergeDestructive

    Merge a conversation into a target conversation; the source is marked as replaced

    conversations.merge

  • UpdateWrite

    Silently close, reopen, move, assign, label, recolor, or rename one or more conversations without adding a post

    conversations.update

Responses

  • CreateWrite

    Create one or more saved response templates

    responses.create

  • DeleteDestructive

    Delete one or more saved response templates

    responses.delete

  • GetRead-only

    Fetch a saved response by id

    responses.get

  • ListRead-only

    List saved responses (canned replies) for the authenticated user

    responses.list

Connect Missive to Claude, ChatGPT or Cursor

  1. 1

    Connect Missive in Corsair

    Add your Missive API key once in Corsair. Corsair stores the credential encrypted and makes the Missive API calls for your agent, so it never goes into a prompt or a config file. Connect Missive

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Missive. On a ChatGPT personal plan, connect Missive here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Missive's read and write operations run right away and its 5 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/missive, add the Missive plugin, and connect with an API key. Then call methods like corsair.missive.api.analytics.createReport() from your app. Corsair keeps each tenant isolated.

Yes. Missive requires an API key from your Missive account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Missive, GitHub, Notion, Stripe, and the rest. Trigger Missive from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for team inbox integration for conversations, contacts, drafts, messages, tasks, teams, and analytics reports. Common builds include sync jobs, admin tooling, and agents that call Missive APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Missive API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/missive in the open repo. When Missive ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Missive data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Missive data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Missive on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 5 destructive Missive operations. You can change a link's mode at hub.corsair.dev/me.