MCP integrations

Connect Missive AI to Notion, Linear, Attio, Stripe, and custom MCP servers.

MCP integrations connect Missive's AI assistant to external tools. Add one, and the assistant can work with your docs, tickets, CRM records, or billing data without leaving Missive.

How to add MCP integrations

1. Go to Settings > Integrations.

2. Open the MCP category.

3. Pick an MCP integration, or choose Custom MCP.

4. Click Add top-right corner of the popup.

To open Settings, click your avatar at the top of the sidebar, then Settings (or press ⌘,).

Available MCP integrations

Missive includes four built-in MCP integrations, plus support for custom MCP servers:

Integration	Best for	Typical jobs
Notion	Internal docs, wikis, project notes	Search pages, read docs, update pages, query databases, leave comments
Linear	Product work and bug tracking	Find issues, create issues, update projects, add comments
Attio	CRM and revenue workflows	Search records, create notes, update tasks, review meetings and emails
Stripe	Billing and payments	Look up customers, inspect invoices, manage subscriptions, create payment links
Custom MCP	Internal tools, help centers, or services Missive does not list built in	Search docs, read records, run provider-specific tools, connect your own workflows

Notion

Use Notion MCP when your team stores SOPs, onboarding checklists, product specs, or meeting notes in Notion.

Official docs: Notion MCP docs

Capabilities

• Search workspace content and open matching pages

• Create, update, move, and duplicate pages

• Create databases, update data sources, and query structured content

• Create and update views

• Read and write comments, and look up people and teams

Some search and query tools require Notion AI and specific Notion plans. Check Notion's docs before rolling this out to your whole team.

Example

Ask Missive AI:

Search Notion for our onboarding checklist, fetch the latest version, and draft a reply to this customer with the exact steps they need to follow.

Linear

Use Linear MCP when support conversations turn into bugs, feature requests, or product work.

Official docs: Linear MCP docs

Capabilities

• Finding issues, projects, and comments

• Creating issues, projects, and comments

• Updating issues, projects, and comments

Example

Ask Missive AI:

Create a Linear issue from this conversation, include the customer impact and reproduction steps, then draft a reply telling the customer we logged it.

Attio

Use Attio MCP when you want Missive AI to pull CRM context into a conversation or log follow-up work back into Attio.

Official docs: Attio MCP docs

Capabilities

• Search records, open them, create them, and update them

• Create notes and search note content

• Create tasks and update them

• Search meetings and call recordings, then open the underlying content

• Search emails and read their contents

• Look up workspace members, teams, and the connected user

Attio auto-approves reads and asks for confirmation before writes in its own MCP flow.

Example

Ask Missive AI:

Find this sender in Attio, summarize the last two meetings and notes, then draft a follow-up that reflects the current deal stage.

Stripe

Use Stripe MCP when customers ask about invoices, subscriptions, refunds, payment links, or failed charges.

Official docs: Stripe MCP docs

Capabilities

• View account details and current balance

• Look up customers and create new ones

• Create invoices and invoice items, finalize invoices, and review invoice history

• Review, update, and cancel subscriptions

• Create and review products, prices, and coupons

• Create payment links and inspect payment activity

• Create refunds and manage disputes

• Search Stripe resources and Stripe documentation

An organization admin must enable MCP access in the Stripe Dashboard before users can connect it.

Example

Ask Missive AI:

Look up this customer's Stripe record, list their active subscriptions and unpaid invoices, and draft a billing reply that explains what is still due.

Custom MCP server

Use Custom MCP when the integration you want is not already listed in Missive.

Only connect MCP integrations from developers you trust. Missive does not control which tools an integration exposes or what it does with the data it receives.

When you add a custom MCP integration, Missive asks for:

• Server URL: the https:// endpoint for the MCP integration

• Authentication: how Missive should authenticate to it

Authentication options

• No authentication: Use this for public or internally trusted MCP integrations that do not require credentials.

• Bearer Token: Paste a static token. Missive sends it when calling the integration.

• OAuth 2.0: Missive opens an authorization flow after you add the integration. If the provider requires it, add a client ID and client secret under Advanced settings.

Missive's built-in MCP integrations use OAuth 2.0. Custom MCP integrations can use any of the three authentication options above.

For example, if your team publishes documentation on a platform that offers an MCP integration, you can connect that documentation to Missive as a custom MCP integration. Missive can then use your help center, internal docs, or product documentation as context when replying to users. GitBook is one example: MCP servers for published docs. You can test this with Missive's own documentation by adding https://missiveapp.com/docs/~gitbook/mcp as a no-auth MCP integration.

Related

• Assistant

• Setting up AI

• Integrations