> 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/admin.md).

# Admin controls

Turn Missive's MCP server on or off for your organization, and understand what it means for members who belong to more than one.

MCP access is off by default. An organization owner or admin has to turn it on before any member can connect an AI app.

## Enabling MCP access

1. Go to **Settings** > **Organizations** and pick your organization.
2. On the **Overview** tab, find **MCP server**.
3. Turn on **Enable MCP access**.

{% hint style="info" %}
To open Settings, click your avatar in the bottom-left corner of the sidebar, then **Settings** (or press <kbd>⌘,</kbd>).
{% endhint %}

Members can connect right away. There's nothing to distribute: they add `https://mcp.missiveapp.com` in their own AI app and approve the request. See [Connecting an AI app](/docs/ai/mcp/server/connect.md).

Only **owners and admins** see this setting. Regular members don't.

{% hint style="info" %}
MCP requires the current **Productive** or **Business** plan. On a legacy plan, the toggle refuses to turn on and Missive tells you to get in touch. [See pricing](https://missiveapp.com/pricing).
{% endhint %}

## What you're turning on

Members who connect an app can reach, through that app, everything they can already reach in Missive. Turning MCP on doesn't widen anyone's access. It changes where that access can be used from.

Each member decides individually whether to connect anything, which app to connect, and which [permissions](/docs/ai/mcp/server/permissions.md) to grant it. As an admin you cannot:

* Restrict which AI apps members connect
* Limit which permissions members grant
* Enable MCP for some members and not others
* See or manage another member's connected apps

It's a single organization-wide switch. If that's too blunt for your security posture, leave it off.

## Multiple organizations

A connected app acts as the member, and a member's access spans every organization they belong to. There's no way to scope an app to one organization. So Missive requires that **every** organization a member belongs to has MCP enabled. One organization with it off blocks that member completely, even for their work in organizations that allow it.

A member in this situation sees a message on the authorization screen naming the organizations that are blocking them, and asking them to contact an admin there.

The practical effect: your decision to leave MCP off also applies to your members' other organizations, including personal ones and those belonging to clients or partners. Members who need MCP will have to ask each of those organizations to enable it.

## Turning MCP access off

Turning off **Enable MCP access** immediately disconnects every app connected by every member of the organization. It isn't a pause. Existing access is destroyed, and nothing can renew it.

If you turn it back on later, members have to connect their apps again from scratch.

Use this if you need to cut off access quickly across the whole organization. To cut off a single app for a single person, that person revokes it from [their own connected apps list](/docs/ai/mcp/server/connected-apps.md#revoking-an-app).

## Related

* [MCP server](/docs/ai/mcp/server.md)
* [Permissions and scopes](/docs/ai/mcp/server/permissions.md)
* [Managing connected apps](/docs/ai/mcp/server/connected-apps.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/admin.md?ask=<question>&goal=<endgoal>
```

`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.