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

# Managing connected apps

See which AI apps have access to your Missive account, what they can do, when they last used it, and how to revoke them.

Every AI app you've authorized is listed in **Settings** > **Login & Security** > **Connected apps**.

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

You may be asked for your password when you open **Login & Security**. That's expected.

## What the list shows

| Column            |                                                                              |
| ----------------- | ---------------------------------------------------------------------------- |
| **App**           | The app that connected, with its icon.                                       |
| **Scopes**        | The [permissions](/docs/ai/mcp/server/permissions.md) you granted it.        |
| **Last IP used**  | The IP address of the most recent request. Click it to look up its location. |
| **Last used**     | When the app last called Missive. Updates every few minutes, not instantly.  |
| **Authorized on** | When you approved it.                                                        |

Check this list occasionally. An app you forgot about still holds whatever you granted it, and **Last used** is the quickest way to spot access you no longer need.

## Revoking an app

1. Go to **Settings** > **Login & Security** > **Connected apps**.
2. Click the **...** menu on the app's row.
3. Click **Revoke access**, then confirm.

Access stops immediately. The app can't read anything, send anything, or refresh its way back in. To use it again, connect it from scratch and approve a fresh request.

Revoke anything you don't recognize, then change your Missive password.

## Reconnecting an app

Authorizing an app you've already connected replaces the previous access rather than adding to it. You'll always see one row per app.

This is also how you change permissions, since there's no way to edit them in place. Revoke the app, connect it again, and check a different set of boxes on the way through.

## When access expires

Access lasts **30 days**, after which the app has to be authorized again. Apps that support silent renewal handle this in the background and you won't notice. Others will ask you to approve again, and you'll see the same authorization screen.

Two other things end access early:

* **You revoke the app**, as above.
* **An admin turns off MCP** for one of your organizations. Every connected app for every member of that organization stops working right away. See [Admin controls](/docs/ai/mcp/server/admin.md).

## Related

* [Connecting an AI app](/docs/ai/mcp/server/connect.md)
* [Permissions and scopes](/docs/ai/mcp/server/permissions.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 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/connected-apps.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.