MCP servers (workspace-wide)

The Model Context Protocol (MCP) is an open standard for exposing tools to AI agents. Connect an MCP server once at the workspace level and its tools become available to agents in the workspace. MCP servers are managed in Settings → MCP Servers.

Prerequisites

An MCP server you want to connect (hosted by a provider, or your own).
Any credentials that server requires (for example, an OAuth token or API key — some servers need none).

Server types

When adding a server, you pick a transport type:

Type	Transport	Use when
HTTP	Streamable HTTP (the server’s `/mcp` endpoint)	The server supports modern Streamable HTTP.
SSE	Legacy HTTP + Server-Sent Events (`/sse` + `/messages`)	The server only supports the older SSE transport.
STDIO	A local command the runtime launches	Running a command-line MCP server (needs a command and optional args).

Providers

Network (HTTP/SSE) servers can be added through three providers:

Custom — point directly at any MCP server URL you control.
Smithery — connect a server from the Smithery registry (authentication is optional; some servers like Notion work without it).
Composio — connect a Composio-backed MCP server.

How to connect

Open MCP Servers
Go to Settings → MCP Servers and click Add Server.
Pick the type and provider
Choose HTTP, SSE, or STDIO, then the provider (Custom, Smithery, or Composio) and enter its connection details.
Authenticate if required
Supply any token or API key the server needs. Some servers need none.
Manage tools
Use Manage tools to select which of the server’s tools are exposed to agents.

What agents can do

Tools from a connected MCP server appear alongside the agent’s other tools. Which ones an agent actually uses also depends on the agent’s capabilities and the tools you’ve enabled.

Managing servers

Search, edit tool selections, or delete a server (after confirmation) from Settings → MCP Servers.
Per-app connections (Gmail, GitHub, Trello, Jira, etc.) are handled separately through the Composio app library.