Connections

Learn how connections work in Odeus — how you authenticate to an integration, how credentials are stored, and how connected tools become available in chat, agents, and workflows.

What are connections?

A connection is a saved authentication link between Odeus and an external tool. When you connect a service such as Google Workspace, Microsoft 365, Slack, or HubSpot, Odeus stores the credentials needed to interact with that service through its MCP connector.

Each connection belongs to the user who created it. Actions are performed with your own access rights, and your credentials are stored encrypted.

How authentication works

Most integrations authenticate with OAuth, the industry-standard protocol for secure authorization. When you connect via OAuth:

1. You're redirected to the service's login page (e.g. Google, Microsoft, Slack)
2. You sign in with your own account
3. You grant permissions for Odeus to access specific data
4. Tokens are stored encrypted and refreshed automatically

OAuth connections always act with your permissions. If you can't access a calendar or repository in the source tool, an assistant using your connection can't access it either.

Odeus handles token refresh for you, so connections keep working without you having to re-authenticate on every use.

---

Connection ownership

Connections are user-based. This means:

• You see and use the connections you created.
• Actions are performed using your access rights and permissions.
• Your credentials are stored encrypted and are never exposed to other users.

When you authorize Odeus to access a tool on your behalf, that authorization stays yours — it isn't handed to other users.

---

Where connected tools are available

Once a connection is in place, the integration's tools can be used by the assistant in:

• Chat — the assistant calls connected tools to fetch information or take actions. Actions that change data go through a confirmation gate before they run.
• Agents — attach tools from your connections to a custom agent so it can use them on every run.
• Workflows — agent nodes can use connected tools as part of an automation.

---

Bringing your own MCP server

In addition to the built-in connectors, you can attach your own remote MCP server to add its tools to Odeus. These run as remote endpoints (no local install), and once added they appear alongside the built-in connectors for the assistant to use.

---

Summary

Feature	OAuth connection	Your own MCP server
User-owned	✅	✅
Credentials stored encrypted	✅	✅
Automatic token refresh	✅	Depends on the server
Available in chat/agents/workflows	✅	✅
Confirmation gate on actions	✅	✅

Understanding how connections work helps you build secure, reliable automations. Connect each service with your own account, and Odeus keeps the tokens fresh so your integrations stay available across chat, agents, and workflows.