Skip to main content
MCP (Model Context Protocol) is an open standard for connecting AI agents to external tools and services. Each MCP server exposes a set of callable functions — tools — that agents can use during a conversation. Examples: GitHub operations, ClickUp task management, database queries, calendar access, custom internal APIs.

​
Adding an MCP server

Click Add MCP Server and configure both the staging and production stages:

​
Transport types

​
Staging vs Production stages

Each MCP server has two stages with independent URLs and credentials:
  • Staging — used during agent development and testing
  • Production — used when the agent goes live
This lets you point agents at a test MCP server during development without risking production data. Toggle the active stage per server independently.
Agents always use whichever stage is currently marked active on the MCP server. You don’t need to update agents when you switch a server from staging to production.

​
Health check

Studio periodically checks the server’s availability. A green indicator means the server is reachable. A red indicator means the server is down or unreachable — agents using this server may fail to call its tools.

​
Credentials

If the MCP server requires authentication (API key, bearer token, etc.), enter the credentials when configuring the server. They’re stored as secrets and injected at runtime via the $secretRef pattern.

​
Using MCP servers in agents

Once registered here, MCP servers appear under MCP Tools during agent creation. See MCP Tools for how to assign them to agents.

​
Next steps

MCP Tools in Agent Creation

Add registered MCP servers to an agent.