MCP integrations are available on the Teams plan. If your workspace is on a lower tier, the Integrations page will show an upgrade prompt. Only owners and admins can add or remove servers.
Looking to message Genie from WhatsApp, Slack, or Microsoft Teams instead? That’s a different kind of connection, managed from the same Integrations page — see Genie on WhatsApp, Slack, and Teams.
Open the integrations page
Click the account row at the bottom of the workspace sidebar, choose Workspace settings, then open Integrations.Add a preset integration
Genie includes one-click presets for the most popular tools. Preset connections have their server URL, transport, and authentication type pre-configured — you just authorise and go.1
Click Add server
On the Integrations page, click the Add server button in the Connected servers section header.
2
Pick a service
A dialog (or bottom drawer on mobile) shows all available preset integrations. Click the tile for the service you want to connect.
3
Set a display name
The form pre-fills a display name (for example, “Linear”). The name becomes the tool prefix used by the AI — for example,
linear__create_issue. Edit it if you need to distinguish multiple connections to the same service.4
Connect the server
Click Connect server. For OAuth-based integrations, a second Authorize button appears on the server row — click it to start the OAuth flow and grant Genie access to your account. For Bearer token integrations, paste your API token into the Bearer token field before clicking Connect server.
5
Confirm the connection
After a successful OAuth authorisation, Genie redirects you back to the Integrations page with a confirmation banner. Tools from the connected server become available to all workspace members on their next conversation turn.
Available preset integrations
Add a custom server
If the tool you need is not in the preset list, you can connect any MCP-compatible server manually.1
Click Add server
Open the Add server dialog from the Integrations page.
2
Choose Other
Scroll to the bottom of the preset grid and click the Other tile labelled “Configure manually”.
3
Fill in the server details
Complete the form:
- Display name — a label for this server. It becomes the tool prefix (for example,
mycrm__get_contacts). - Server URL — the full URL of the MCP endpoint.
- Description (optional) — a note for your team about what this server does.
- Transport — choose Streamable HTTP (recommended for all servers built after March 2025) or SSE for older legacy servers.
- Authentication — choose the auth type that matches your server (see below).
4
Connect the server
Click Connect server. If you chose OAuth2, click Authorize on the server row that appears to complete the OAuth flow. If you chose Bearer token, you will have already entered the token in the form.
Connect any REST API
If a service has no MCP server, ask Genie AI in the workspace chat to connect it — “Connect our Shopify shop” or “Connect our internal orders API”. Genie AI writes down the API’s operations (for example List orders and Create order) and asks you for the API key on a card of its own, so the key never passes through the model. The result is a custom API integration, listed with a Custom API badge, and each of its operations is available in three places:- as a step in the Genie Agents editor — under Your integrations in the add-step list, one row per operation such as Shop · List orders. Its inputs appear as ordinary fields, with the raw JSON still available under Advanced;
- as a tool of Genie AI itself, so “List my open orders” works in chat;
- through the Genie MCP Server, for external clients.
Authentication types
- OAuth 2.1
- Bearer token
- None
Most preset integrations use OAuth 2.1. When you click Authorize, Genie discovers the service’s authorisation server, dynamically registers a client, and completes the flow with PKCE. The resulting token is stored encrypted at the workspace level and refreshed automatically. No manual token management is required.If an OAuth connection expires or is revoked, click Re-authorize on the server row to restart the flow without losing your configuration.
Shared vs. personal connections
Most connectors are still one shared connection for the whole workspace — an admin connects it once, and every member’s tools use that same credential, as described above. A few connectors need a personal account instead, because a shared credential wouldn’t make sense there — Microsoft 365, Gmail, and Google Drive, for example, each need to reach one person’s own mailbox or files rather than something shared. For those, an admin still adds the connector itself for the workspace, but each member then connects their own account from their side, and Genie’s AI acts using that member’s own connected account whenever it’s that member talking to it, not a shared one. If you haven’t connected your own account yet, that connector simply isn’t available to you until you do — Genie never falls back to someone else’s connected account. If someone leaves the workspace, their personal connection is removed along with their membership. Only you can see that your own account is connected in a way that exposes your credentials; admins can see whether a connector is connected or not, but never the credential itself, even for connectors you’ve personally connected. An owner or admin can switch a connector between shared and per-member later, from its Edit form (“Who signs in”) — no need to remove it and add it again. Switching direction never carries an existing credential across: everyone connected under the old setting needs to (re)connect under the new one.Sync your own mailbox
Every member can mirror their own Outlook or Gmail mailbox into the knowledge base, so Genie AI can answer from their mail. Open Settings → Integrations and find the My mailbox card: it has one row per mailbox, each showing its state and the next step — Connect your account (an owner or admin has to add the integration first if it isn’t there), Start syncing, Pause, Resume, Try again after a failed run, or Stop. Genie AI can show the same state, and starts, pauses or stops a sync only when you press the card it offers.- Only your own mail, last 90 days. A sync reads the mailbox of whoever started it, never someone else’s, and begins 90 days back. Mail folders aren’t copied — every message becomes one document on a single shelf, and a message you move between folders stays the same document.
- Private to you. The mail lands in your own personal access area: other members never see it, not even that it exists. The workspace’s owners and admins can still read it. If you leave the workspace, your area is held rather than opened to others.
- Not everything is knowledge. Newsletters and mailing lists, automated mail, calendar invitations and no-reply senders are skipped before anything is read, and show as Not knowledge in the sync’s file list. Junk, Deleted Items, Drafts and similar folders are never read.
- Stopping keeps what was filed. The mail already read stays in your area; starting again files it a second time.
- Time and cost, up front. Before you start, the row says how many messages it will read, roughly how long that takes and what the import and each following month cost in credits. While it runs, it shows what is left, when it should be done and what the sync has cost so far. If a mailbox is too large to count completely, the figures say at least.
Manage connected servers
Each connected server appears as a row in the Connected servers list, with a plain-language status — connected, ready, not connected yet, not working, per-member, or paused — instead of raw connection details. If the status is just a sign-in away, a Connect button sits right on the row rather than in a menu. From the row you can:- Enable / Disable — temporarily turn a server off without removing it. Disabled servers do not provide tools to the AI.
- Authorize / Re-authorize — (OAuth servers only) start or restart the OAuth flow.
- Edit — change the display name, description, or bearer token.
- Remove — permanently disconnect the server and delete its credentials.
Security
Encrypted at rest
All credentials — bearer tokens and OAuth tokens — are encrypted at rest. They are never returned to the browser after they are saved.
Audit trail
Every add, update, rotation, and removal of an MCP server is recorded in the workspace activity log, giving owners and admins a complete record of credential changes.
Role-based access
Only owners and admins can add, edit, or remove servers. Members and editors can use the tools exposed by connected servers but cannot read or modify credentials.
Related pages
Genie on WhatsApp, Slack, and Teams
Message Genie directly from your phone or team chat.
Genie MCP Server
Let an external AI client like Claude Desktop or Cursor call Genie’s own tools.
