> 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.md). # MCP server Connect Claude, ChatGPT, or any other MCP client to Missive and work with your conversations, contacts, and calendar from outside Missive. Missive runs an MCP server at `https://mcp.missiveapp.com`. Connect an AI app to it, and that app can search your conversations, look up contacts, check your calendar, draft replies, and send them, without you opening Missive. This is the opposite of [MCP integrations](/docs/ai/mcp/integrations.md), which bring outside tools into Missive's own assistant. {% hint style="info" %} The MCP server is off by default. An organization admin has to [turn it on](/docs/ai/mcp/server/admin.md) before anyone in the organization can connect. {% endhint %} ## What you can do with it Ask your AI app things like: > What did the customer in the Acme thread ask for, and has anyone replied yet? > Find every unanswered conversation labeled Billing from this week and summarize them. > Draft a reply to the last message in this thread, then put it in my drafts so I can review it. > Am I free Thursday afternoon? Book a 30 minute call with Sam if I am. The app sees exactly what you see in Missive, across every organization and account you belong to. It cannot reach anything you couldn't already open yourself. ## What it does not do **It doesn't use Missive AI.** The model doing the thinking is the one in the app you connected, so you pay that vendor, not Missive. You don't need an [AI provider](/docs/ai/setup.md) connected, and MCP use doesn't draw down [Missive AI credits](/docs/ai/overview.md#two-ways-to-connect). **It doesn't act on its own.** Nothing happens unless you ask for it in a chat. **It isn't the REST API.** For building an integration, use the [REST API](/docs/advanced-features/integrations/build-your-own.md) instead. MCP is for chatting with your data. ## Requirements | | | | ---------------- | ---------------------------------------------------------------------------------------------------- | | **Plan** | Current **Productive** or **Business** plan. Legacy plans need an upgrade. | | **Organization** | An admin must [enable MCP access](/docs/ai/mcp/server/admin.md) in every organization you belong to. | | **AI app** | Any MCP client that supports remote servers with OAuth, such as Claude or ChatGPT. | {% hint style="warning" %} If you belong to more than one organization, **every** one of them has to have MCP enabled. A single organization with it turned off blocks you entirely. See [Admin controls](/docs/ai/mcp/server/admin.md#multiple-organizations). {% endhint %} ## How it works {% stepper %} {% step %} ### You add Missive in your AI app Paste `https://mcp.missiveapp.com` as a custom connector. See [Connecting an AI app](/docs/ai/mcp/server/connect.md). {% endstep %} {% step %} ### Missive asks you to approve A browser window opens on Missive's authorization screen listing the permissions the app asked for. You choose which to grant, confirm the address you're being sent back to, and click **Approve**. {% endstep %} {% step %} ### The app gets its own limited access The app only receives the permissions you checked. Anything you left unchecked is invisible to it, down to the individual tools it can call. {% endstep %} {% step %} ### You stay in control Every connected app is listed in **Settings** > **Login & Security** > **Connected apps**, with the permissions it holds and when it last used them. Revoke any of them at any time. {% endstep %} {% endstepper %} ## Next steps * [Connect an AI app](/docs/ai/mcp/server/connect.md) * [Permissions and scopes](/docs/ai/mcp/server/permissions.md) * [Manage connected apps](/docs/ai/mcp/server/connected-apps.md) * [Admin controls](/docs/ai/mcp/server/admin.md) * [MCP server FAQ](/docs/ai/mcp/server/faq.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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://missiveapp.com/docs/ai/mcp/server.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.