Introduction to Integrations

Integrations connect Odeus to the tools your team already uses. Instead of switching between apps to look something up or take action, you can do it directly from your conversation, agents, and workflows.

What can you do with integrations?

• Look up a contact in HubSpot while drafting a follow-up email
• Search a Jira backlog and create a new issue based on what you find
• Read a Notion page or post an update to a Linear project
• Send a Slack message to your team after generating a report
• Browse and act on files in Google Workspace, Microsoft 365, and GitHub

How it works

Odeus integrates with external tools through the Model Context Protocol (MCP). Odeus ships a large set of built-in MCP connectors — including Slack, Notion, Linear, Jira, GitHub, and HubSpot, plus deep Google Workspace (Gmail, Calendar, Drive, Docs, Sheets, and more) and Microsoft 365 (Outlook, OneDrive, SharePoint browse, Teams, and more) coverage — adding up to roughly 148 tools across 22 service families.

You connect a service once by signing in with your own account. Odeus stores the credentials securely and refreshes access tokens automatically, so your connections keep working without re-authenticating each time. See the connections page for how authentication and token handling work.

Adding your own MCP servers

Beyond the built-in connectors, you can attach your own remote MCP servers to bring additional tools into Odeus. These run as remote endpoints (no local setup) and become available alongside the built-in connectors once added.

Note: Knowledge Hub also offers Google Drive sync, which mirrors a Drive folder into a knowledge source for retrieval (RAG). That is distinct from an MCP connector, which lets the assistant read and take live actions in a tool. Other providers such as Microsoft 365, SharePoint, Slack, and Notion are available as browse/action connectors via MCP rather than as synced knowledge sources.

Where integrations show up

Once connected, integration tools are available to the assistant in:

• Chat — the assistant can call connected tools to fetch information or take an action (with confirmation gates for actions that change data)
• Agents — attach tools to a custom agent so it can use them on every run
• Workflows — agent nodes in a workflow can use connected tools as part of an automation

To learn more about authentication and token refresh, see the connections page.