Connectors & MCP Guide

How Odeus connects to external tools through native MCP connectors and remote MCP servers

Overview

Odeus connects to external tools and services through the Model Context Protocol (MCP). Connectors give your agents and chats live, governed access to systems like Slack, Notion, GitHub, Google Workspace, and Microsoft 365 — so you can read and act on data without leaving the conversation.

There are two ways tools reach Odeus:

• Native connectors — connectors maintained by Odeus that ship as MCP tools. These cover the most common business systems.
• Remote MCP servers — connect any MCP-compatible server by URL. You can also attach your own MCP per message for one-off use.

Odeus ships roughly 148 native tools across 22 service families: connector tools (Slack, Notion, Linear, Jira, GitHub, HubSpot), Google Workspace (10 services), and Microsoft 365 (6 services).

What's available

Connector family	Examples
Productivity & messaging	Slack, Notion, Linear, Jira, GitHub, HubSpot
Google Workspace	Gmail, Calendar, Drive, Docs, Sheets, Slides, and more (10 services)
Microsoft 365	Outlook Email, Outlook Calendar, Excel, Teams, Planner, SharePoint (browse-only)

SharePoint is available as a browse-only connector — Odeus can read SharePoint content as a live tool, but it does not sync SharePoint into your Knowledge Hub. For Knowledge Hub ingestion, see Google Drive sync below.

Connecting an account

Go to **Settings → Integrations** in your Odeus workspace.



Choose the connector you want and click **Connect**. Most connectors use OAuth — you'll sign in with your account and grant Odeus access. Credentials are encrypted at rest, and tokens are refreshed automatically.



In a chat, mention the connector with `@` and ask for what you need, e.g. `@Slack list channels` or `@GitHub show my open pull requests`.

Connecting a remote MCP server

You can connect any MCP-compatible server by URL:

1. Go to Settings → Integrations and choose Add MCP server.
2. Enter the server URL and complete any authentication the server requires.
3. The server's tools become available to your chats and agents.

You can also attach a per-message MCP for one-off use — useful when you want a server's tools for a single request without adding it permanently to your workspace.

Using connectors

In chat

Mention a connector with @ in any conversation:

• @Slack send a message to #general saying "Standup in 5 minutes"
• @HubSpot find contacts at Acme Corp
• @Google Calendar create a meeting tomorrow at 2pm

In agents

Give an agent access to connectors so it can act on your behalf:

1. Open your agent in the Agents builder.
2. In the tools section, add the connectors the agent should use.
3. The agent can then call those tools automatically while responding.

In workflows

Connectors can be used inside workflow steps so automated runs can read and act on external systems as part of a multi-step flow. See the Workflows documentation for node details.

Sync vs connectors

There is an important distinction between syncing content into the Knowledge Hub and using a connector as a live tool:

• Google Drive sync mirrors a Drive folder into your Knowledge Hub so its documents are indexed for RAG retrieval and citations. This is the only file-sync source currently available.
• Connectors (Slack, Notion, Microsoft 365, SharePoint browse, etc.) are live tools — Odeus reads and acts on them at request time. They do not ingest content into the Knowledge Hub.

OneDrive and Dropbox sync are not currently available. Microsoft 365 and SharePoint are reachable as connectors (SharePoint browse-only), not as Knowledge Hub sync sources.

Best practices

• Use filters and limits when asking for data to keep responses focused and fast.
  • Prefer specific IDs over names when referencing resources for reliability.
  • Grant connectors only the access they need.

Troubleshooting

Issue	Possible cause	Solution
Authentication failed	Expired or revoked credentials	Open the connector in Settings → Integrations and reconnect
Action not available	Connector not connected or scopes not granted	Confirm the connector is connected and required scopes are granted
Data not found	Insufficient permissions or wrong ID	Verify your access in the source system and check the resource ID
Microsoft "approval required"	Tenant admin consent not yet granted	See Microsoft Integrations: Permissions & Admin Approval

Support

• Contact [email protected] for technical assistance.
• Visit the Help Center for tutorials and guides.