## Superhuman integration Superhuman is an email and calendar client built for speed, with an AI assistant called Ask AI layered on top. Agen.co connects to Superhuman through Superhuman's own hosted MCP server as an **Official** connector. Each user authorizes with their own Superhuman Mail account, and agents can only reach the email and calendar data that account already has access to. Prerequisites - A Superhuman Mail account on a paid plan — the MCP server isn't available on Superhuman's entry-level plan. - **Ask AI** enabled on the account. - The Superhuman Mail Chrome extension installed on the browser used to authorize the connection. - On Enterprise or other managed accounts, an admin may need to enable MCP Server access first; not every account requires this. ### Connect Superhuman in Agen.co 1. In the Agen.co portal, go to **Connectors** → **My connectors** and click **Add connector**. 2. In the **Select connector** drawer, search for `Superhuman` and select it. The **Add Superhuman** panel opens. 3. Fill in the field: | Field | Required | Description | | --- | --- | --- | | **Instance Slug** | Yes | Prefixes each imported tool as `slug__tool`, so several instances of the connector can coexist. Prefilled with `superhuman`. Use lowercase kebab-case. You can change it later from the connector's settings. | 4. Click **Connect**. Superhuman opens in a new tab, and the panel shows **Waiting for authorization — complete it in the opened tab…** 5. On the **Connect to Superhuman Mail** screen, sign in with the account's Google or Microsoft login, then approve the requested access. 6. Back in Agen.co, the panel switches to **Select the tools to import from Superhuman.** Every tool is toggled on; turn off any you don't want to import, then click **Add**. The connector is created and its tools imported only when you click **Add**. If you close the panel before that, nothing is saved, even though the Superhuman tab reported success. ### Authorize each user Adding the connector doesn't authorize anyone's tool calls yet. The first time each user's agent calls a Superhuman tool, the call returns an authorization link instead of a result. The user opens the link, signs in, and approves the same way. After that, the user's tool calls run against their own Superhuman Mail account. Once connected, Superhuman appears under **My connectors** with tools spanning: | Area | What it covers | | --- | --- | | **Email search and reading** | Natural-language search across email and calendar, listing and reading threads and messages, reading labels, and reading who opened a sent message and when | | **Drafts** | Creating, updating, reading, listing, discarding, and sending drafts, and checking a draft's send status | | **Thread actions** | Updating a thread's labels, star, trash, and read/done state; trashing a thread; unsubscribing from a sender; and undoing a recently sent message | | **Calendar** | Creating or updating events, and checking availability | | **Reminders** | Creating, listing, and discarding reminders | | **Split inboxes** | Listing the account's split inboxes | | **Accounts** | Linking an account, listing linked accounts, setting the default account, and removing an account | | **Attachments** | Retrieving a message's attachments | | **Personalization** | Updating personalization settings | Enabling the Superhuman connector isn't enough on its own. Tool calls remain denied until you create a [policy](/agen-for-work/policies/overview) that grants access to the specific tools you want to expose. ### Additional resources - [Superhuman Mail MCP Server](https://help.superhuman.com/hc/en-us/articles/46005696690317-Superhuman-Mail-MCP-Server)