Integrations

An integration is a connection between your workspace and an external service — Slack, GitHub, an MCP server, an OAuth provider. Integrations live at the workspace level and bring two things into reach at once: tools your agents can call, and events your agents can be triggered by.

What an integration gives you

Connect once and every agent in the workspace can:

• Use the integration as a tool. A connected MCP server registers its capabilities so agents can call them. A connected GitHub App lets agents read repositories, comment on pull requests, and open issues using workspace-scoped credentials.
• React to its events. Once an integration is connected, map specific events (a GitHub pull request, a Slack mention) to fire an agent. The Automation guide covers how triggers are wired.

Connections are workspace-scoped: each integration is granted to agents explicitly, so connecting one doesn't expose it automatically.

Connect from the dashboard

The Integrations page in the sidebar shows everything that's already connected and a tile catalogue of providers to add.

• Slack and GitHub are first-class tiles — click connect and walk through the provider's authorisation in your browser. GitHub's flow includes the App install screen so you can pick which repos to grant.
• MCP servers — Notion, Cloudflare, and a growing catalogue — install with the same one-click flow. For anything not in the catalogue, the Custom MCP server tile takes any OAuth-protected MCP URL and registers Levain as a client automatically.

Connected integrations show a status pill (active, pending, expired) and a Disconnect button. Disconnecting an integration cleanly removes the credentials and any agent access that relied on them.

Credentials stay on the platform

Tokens and credentials for every integration are encrypted at the workspace level. Agents call tools by name; Levain handles the authorisation, refresh, and revocation behind the scenes. Your agent recipe doesn't carry secrets, and rotating an integration is one click in the dashboard.

From the API

You can list connected integrations, fetch available providers, and disconnect from outside the dashboard. The Integrations API reference covers the endpoints. The initial connect flow is dashboard-only because it ends in a provider authorisation page that needs a browser.

Next

• The Tools primitive explains how a connected capability becomes callable for an agent.
• Set up a trigger so events from your integration fire an agent.