Missive MCP Server

An MCP (Model Context Protocol) server that interfaces with the Missive API, enabling Claude to manage email conversations, contacts, and team collaboration.

Prerequisites

• Node.js 18+
• Missive account with Productive plan (required for API access)
• Missive API token

Installation

npm install
npm run build

Modes

The server runs in two modes: stdio for local single-user use, and remote for hosted multi-user deployments.

Stdio Mode (Local)

Set the MISSIVE_API_TOKEN environment variable:

export MISSIVE_API_TOKEN="your_api_token_here"
npm start

To get your API token: open Missive, go to Settings > API, click “Create a new token”.

Add to your Claude Desktop configuration (claude_desktop_config.json):

{
  "mcpServers": {
    "missive": {
      "command": "/path/to/node",
      "args": ["/path/to/missive-mcp/dist/index.js"],
      "env": {
        "MISSIVE_API_TOKEN": "your_api_token_here"
      }
    }
  }
}

Important: Use the full path to node (run which node to find it). Claude Desktop has a restricted PATH and may not find node otherwise.

Remote Mode (Hosted)

Runs an HTTP server with OAuth. Each user provides their own Missive PAT through a browser-based authorization flow.

export ENCRYPTION_KEY="$(openssl rand -hex 32)"
export BASE_URL="https://missive-mcp.example.com"
npm run remote

Point MCP clients at {BASE_URL}/mcp. The server handles OAuth automatically:

1. Client discovers endpoints via /.well-known/oauth-authorization-server
2. Client registers dynamically via /register
3. User is redirected to a form to paste their Missive API token
4. Server validates the token, encrypts and stores it, issues OAuth tokens
5. Client uses bearer tokens to call /mcp

PATs are encrypted at rest with AES-256-GCM. OAuth tokens expire after 1 hour (refresh tokens last 30 days).

Tools

Reference Data

Conversations

Messages