Built-in connectors

A reference of the integrations that ship with Odeus. All connectors run over the Model Context Protocol (MCP) and become available to the assistant in chat, agents, and workflows once you connect your account.

Odeus ships roughly 148 tools across 22 service families. The connectors fall into three groups.

Productivity & developer tools

These let the assistant read information and take actions in common SaaS tools:

Service	Examples of what it can do
Slack	Read channels and threads, post messages
Notion	Read and update pages and databases
Linear	Read and create issues and projects
Jira	Search the backlog, read and create issues
GitHub	Read repositories, issues, and pull requests
HubSpot	Look up contacts and CRM records

Google Workspace

Deep coverage across Google's productivity suite (around 10 services), including:

• Gmail — read and draft email
• Calendar — check availability, read and create events
• Drive — browse and read files
• Docs — read and edit documents
• Sheets — read and update spreadsheets

Note: Knowledge Hub also offers Google Drive sync, which mirrors a Drive folder into a knowledge source for retrieval. That is separate from the Drive connector, which lets the assistant browse and act on files live.

Microsoft 365

Coverage across roughly 6 Microsoft 365 services, including:

• Outlook — mail and calendar
• OneDrive — files
• SharePoint — browse only (read access; not synced into the Knowledge Hub)
• Teams — messages

Connecting a tool

1. Choose the service you want to connect.
2. Sign in with your own account (OAuth).
3. Grant the requested permissions.

Odeus stores the credentials encrypted and refreshes access tokens automatically. See connections for details on authentication and token handling.

Adding your own MCP server

If you need a tool that isn't built in, you can attach your own remote MCP server by URL — and even attach one per message — to bring its tools into Odeus without any local setup. See the introduction for an overview.