MCP Connections

Connect your business systems so agents can work with them — with you deciding exactly which tools each agent may use.

MCP (Model Context Protocol) is an open standard for connecting AI systems to external tools and data. In yeos, an MCP connection links your organization to a server — Slack, GitHub, your CRM, or any MCP-compatible system — and turns its capabilities into tools your agents can use.

Once a connection is set up, yeos discovers the tools the server offers. Each discovered tool can be enabled or disabled at the connection level, and every agent only gets the tools you explicitly enable for it. During a run, the agent calls those tools like any other — and every call appears in the run trace.

This is how yeos reaches beyond your uploaded documents without giving up control: your systems stay where they are, access is scoped per agent, and every interaction is visible and logged.

First-Party Connectors

yeos ships ready-made connectors with guided sign-in for common business systems. Connect them in a few clicks — no server details required.

Slack — read and work with channels and messages

Atlassian (Jira & Confluence via Rovo) — issues, projects, and pages

Gmail — search, read, and draft email

GitHub — repositories, issues, and pull requests

HubSpot — CRM contacts, companies, and deals

Microsoft 365 — mail, calendar, Teams, and files via dedicated connectors

Connect Any MCP Server

Beyond the first-party connectors, org admins can connect any MCP-compatible server by entering its URL and choosing how to authenticate.

Supported transports

Streamable HTTP — the current MCP standard, recommended for new connections

SSE (Server-Sent Events) — supported for servers that still use the older transport

Authentication options

None — for servers that need no authentication

API key header — a custom header name and secret value

Bearer token — a static token sent as an Authorization header

OAuth 2.0 — full authorization-code, client-credentials, or refresh-token flows; yeos refreshes tokens automatically

Enabling Tools per Agent

Connections make tools available; agents only use what you enable for them.

Enabling Tools per Agent

After connecting, yeos lists every tool the server offers. You can enable or disable individual tools at the connection level — a disabled tool is invisible to all agents.

In the agent configuration, you pick which MCP tools this specific agent may use. An agent never sees tools that are not enabled for it.

During a run, MCP tool calls show up in the agent trace like any other tool call, and results flow into the answer with the same traceability.

Security Guarantees

Connections are HTTPS-only — plain HTTP servers are rejected.

Private and internal network addresses are blocked, so an MCP connection cannot be pointed at internal infrastructure.

Requests run with timeouts and response-size limits to keep agent runs responsive.

Credentials are stored per connection and never shown to agents — agents see tools, not secrets.

Setting Up a Connection

1

Open your organization settings as an admin and go to MCP connections.

2

Pick a first-party connector and sign in, or add a custom server with its URL, transport, and authentication.

3

Test the connection — yeos verifies it and discovers the available tools.

4

Enable the tools you want to offer, then select them in the configuration of each agent that should use them.

Common Questions

Who can manage MCP connections?

Organization admins create, test, update, and delete connections. Workspace members use the resulting tools through agents, subject to what is enabled.

Why doesn't my agent see a tool from a connected server?

Check two levels: the tool must be enabled on the connection, and it must be selected in that agent’s configuration. Both are required.

Can I connect a server that runs inside our private network?

No — for security, yeos only connects to publicly reachable HTTPS endpoints and blocks private network addresses. Expose an MCP server through a secure public endpoint if you need it.

What happens when a token expires?

For OAuth 2.0 connections, yeos refreshes tokens automatically. If a refresh fails or credentials are revoked, tool calls report a clear connection error and an admin can re-authenticate the connection.