For the complete documentation index, see llms.txt. This page is also available as Markdown.

Connecting an AI app

Install the Missive app in Claude or ChatGPT, or add it as a custom connector in any MCP client, then approve the permissions it asks for.

Connecting takes two steps: add Missive in your AI app, then approve the request in Missive.

Missive is listed in both Claude's and ChatGPT's directories, so there you only need to find it and click connect. Other clients need the server URL.

Server URL: https://mcp.missiveapp.com

Missive issues no API key and no client secret for MCP. Authorization happens in your browser.

Before you start, make sure an admin has enabled MCP access in every organization you belong to. Otherwise the approval screen will refuse the request and name the organizations blocking it.

Step 1: Add Missive in your AI app

In Claude and ChatGPT, install the official Missive app from their directory. In other clients, look for Connectors, Custom connectors, MCP servers, or Integrations, then add a remote server and paste the URL above.

  1. Open Settings > Connectors.

  2. Click Browse, then search for Missive.

  3. Click Missive.

  4. Click Connect to Claude.

Claude opens a browser window on Missive's authorization screen. Continue to step 2.

  1. In ChatGPT, open the plugin directory and search for Missive.

  2. Click Missive, then connect it.

  3. ChatGPT sends you to Missive's authorization screen. Continue to step 2.

There's no URL to paste. If the Missive plugin isn't available to you, you can still add https://mcp.missiveapp.com as a custom connector under Settings > Apps & Connectors, where your ChatGPT plan allows it.

Point the client at https://mcp.missiveapp.com as a remote MCP server over HTTP.

Missive registers your client automatically the first time it connects, so there is nothing to create in Missive beforehand. The client must support OAuth with PKCE and must send the resource parameter defined in the MCP specification. Most current clients do. Older ones fail to connect, and there is no workaround. See the FAQ.

Missive's MCP server is stateless and doesn't support SSE connections.

Step 2: Approve the request in Missive

Your browser lands on Missive's Authorize access screen. If you're logged out, you'll be asked to log in first. You cannot create a new Missive account during this flow, so sign up separately if you don't have one yet.

The screen shows the app requesting access and the permissions it asked for.

1

Choose the permissions to grant

Every requested permission is checked by default. Uncheck anything you'd rather not give away.

Unchecking is a real restriction, not a preference. A permission you don't grant removes the matching capabilities from the app entirely, and the app can't ask for them later without going through this screen again. See Permissions and scopes for what each one covers.

Grant at least one permission, or Approve stays disabled.

2

Verify the redirect URL

Under Verify redirect URL, Missive shows the exact address it will send you back to after approval, and asks you to check I recognize and trust this URL.

Read it. This is what stops a malicious site from talking you into handing over access to your email. If the address doesn't belong to the app you're connecting, click Deny access.

3

Approve

Click Approve. Missive sends you back to the app, and a notice tells you that you can close the window.

If nothing seems to happen, check that your browser isn't blocking pop-ups.

The app is now connected and appears in Settings > Login & Security > Connected apps.

Changing permissions later

There's no way to edit an app's permissions after the fact. To change them, revoke the app and connect it again with a different selection.

Reconnecting an app you've already authorized replaces the old access. You won't end up with two live grants for the same app.

Last updated