Genie supports the Model Context Protocol (MCP), an open standard that lets AI assistants call tools in external services. When you connect an MCP server to your workspace, every member can use those tools inside any project — without each person setting up their own credentials. A single workspace-level connection covers your whole team.Documentation Index
Fetch the complete documentation index at: https://docs.genie-app.de/llms.txt
Use this file to discover all available pages before exploring further.
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.
Open the integrations page
In the workspace sidebar, click Settings, then click Manage in the Integrations section — or go directly to Settings → Integrations from the settings page.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.Click Add server
On the Integrations page, click the Add server button in the Connected servers section header.
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.
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.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.
Available preset integrations
| Service | Server URL | Transport | Auth |
|---|---|---|---|
| Linear | https://mcp.linear.app/sse | SSE | OAuth2 |
| GitHub | https://api.githubcopilot.com/mcp/ | HTTP | OAuth2 |
| Notion | https://mcp.notion.com/mcp | HTTP | OAuth2 |
| Atlassian | https://mcp.atlassian.com/v1/sse | SSE | OAuth2 |
| Asana | https://mcp.asana.com/sse | SSE | OAuth2 |
| Sentry | https://mcp.sentry.dev/mcp | HTTP | OAuth2 |
| Stripe | https://mcp.stripe.com | HTTP | Bearer token |
| Cloudflare | https://docs.mcp.cloudflare.com/sse | SSE | OAuth2 |
Add a custom server
If the tool you need is not in the preset list, you can connect any MCP-compatible server manually.Choose Other
Scroll to the bottom of the preset grid and click the Other tile labelled “Configure manually”.
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).
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.
Manage connected servers
Each connected server appears as a row in the Connected servers list. 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.