> For the complete documentation index, see [llms.txt](https://missiveapp.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://missiveapp.com/docs/ai/mcp/server/faq.md).
# MCP server FAQ
Common questions and connection problems with Missive's MCP server.
## Setup
What's the MCP server URL?
`https://mcp.missiveapp.com`
That's all you need. There's no API key, no client ID, and no client secret to create. Your AI app registers itself automatically, and you authorize it in the browser.
Which AI apps work with it?
Any MCP client that supports remote servers over HTTP with OAuth. Claude and ChatGPT both do, and so do most current MCP clients.
Missive requires the `resource` parameter from the MCP specification, which some older clients don't send. Those clients can't connect. See [My AI app can't connect](#my-ai-app-cant-connect).
Do I need an AI provider or AI credits?
No. The MCP server has nothing to do with Missive's own AI features.
The model doing the work lives in the app you connected, so that vendor bills you for it. You don't need an [AI provider](/docs/ai/setup.md) set up in Missive, and MCP doesn't consume [Missive AI credits](/docs/ai/overview.md#two-ways-to-connect).
Can I connect more than one app?
Yes. Connect as many as you like, each with its own permissions. They're all listed in **Settings** > **Login & Security** > **Connected apps**.
Is this the same as MCP integrations?
No, they're opposites.
[MCP integrations](/docs/ai/mcp/integrations.md) let Missive's own assistant reach out to Notion, Linear, Stripe, and similar tools while you work inside Missive. The MCP server lets outside apps reach into your Missive data.
They're configured in different places and don't affect each other.
## Troubleshooting
Missive says MCP access is disabled for my organization
An admin hasn't turned it on. Ask an owner or admin of the organizations named in the message to enable it under **Settings** > **Organizations** > **Overview** > **MCP server**.
If the message names an organization you barely use, you still need it enabled there. A connected app can reach data from every organization you belong to, so Missive requires all of them to allow MCP. See [Admin controls](/docs/ai/mcp/server/admin.md#multiple-organizations).
My AI app can't connect
Work through these in order:
1. **Check the URL.** It's `https://mcp.missiveapp.com`, added as a remote or custom connector.
2. **Check that MCP is enabled** in every organization you belong to. See above.
3. **Check your plan.** MCP requires the current Productive or Business plan.
4. **Check your pop-up blocker.** Authorization happens in a browser window, and blockers sometimes swallow it.
5. **Update your AI app.** Missive requires a security parameter that older MCP clients don't send. If an outdated client fails with a target or resource error, updating it is the only fix.
The Approve button is greyed out
Either no permissions are checked, or the screen is still loading. Grant at least one permission to continue.
If you check **I recognize and trust this URL** and clicking **Approve** just shakes the box, the permission list is empty.
Nothing happened after I clicked Approve
A pop-up should have opened to finish the handoff. Check whether your browser blocked it, allow pop-ups for Missive, and start again from your AI app.
The authorization request expired
Requests are valid for a few minutes. Start the connection again from your AI app rather than reloading the Missive page.
My app stopped working after a while
Access lasts 30 days. Apps that renew silently keep working, and others ask you to authorize again.
If it stopped sooner, either the app was revoked in **Connected apps**, or an admin turned off MCP for one of your organizations.
I'm getting rate limit errors
Missive allows 60 requests per minute and 600 per hour per user, shared across every app you've connected. A few individual actions like sending and updating drafts have tighter limits of their own.
Normal chat use doesn't come close. Hitting the limit usually means an app is looping, so wait a minute and check what it was doing.
## Security
What can a connected app actually see?
Exactly what you can see in Missive, limited further by the [permissions](/docs/ai/mcp/server/permissions.md) you granted, across every organization you belong to. It can't reach anything you couldn't open yourself.
Can an app send email as me?
Only if you granted **Send messages**. Withhold it and the app can still write drafts for you to review, but it can't deliver anything.
Actions taken over MCP run immediately, without Missive's in-app confirmation step. Your AI app's own approval prompt is the only checkpoint, so set it to ask before running tools.
Why does Missive ask me to confirm a redirect URL?
It's the one check only you can make. Missive can verify that an app is who it claims to be at a technical level, but not that it's the app *you* meant to connect.
A malicious site can start an authorization request and try to have your access sent to an address it controls. Reading that address is what stops it. If it doesn't belong to the app you're connecting, click **Deny access**.
Can an admin see or control what I connect?
No. Admins turn MCP on or off for the whole organization, and that's the extent of it. They can't see your connected apps, restrict which apps you use, or limit the permissions you grant.
Turning MCP off does disconnect every app for every member at once.
How do I cut off access immediately?
Revoke the app in **Settings** > **Login & Security** > **Connected apps** using the **...** menu. Access stops at once, and the app can't renew it.
If you don't recognize a connected app, revoke it and change your Missive password.
## Related
* [MCP server](/docs/ai/mcp/server.md)
* [Connecting an AI app](/docs/ai/mcp/server/connect.md)
* [Permissions and scopes](/docs/ai/mcp/server/permissions.md)
* [Admin controls](/docs/ai/mcp/server/admin.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://missiveapp.com/docs/ai/mcp/server/faq.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.