MCP Tools
MCP tools let an admin connect an approved external tool server to Studio. Once connected, selected tools can be made available to Peers and Flow agent steps just like other configured tools.
What this is
An MCP tool connection is a workspace-managed integration for tool servers that your organization trusts. It is useful when a team already has an external tool server and wants Peers or Flows to use the actions it provides.
For protocol details, implementation requirements, and server development guidance, use the Developer Hub.
When to use it
Use an MCP tool when:
- A required action is not available as a built-in Studio tool.
- Your organization already runs a trusted tool server.
- A Peer or Flow needs controlled access to internal systems.
- You want to expose only selected actions to an agent.
Before you start
Make sure:
- The server is trusted by your organization.
- You know the server URL and any required credentials.
- You understand which actions the server exposes.
- You have approval to make those actions available to Peers or Flows.
Set up an MCP tool
- Open Tools in Studio.
- Click Add Tool.
- Select MCP as the tool type.
- Enter a clear display name.
- Enter the server URL and any required authentication details.
- Save the connection.
- Review the discovered tools before assigning them to a Peer or Flow.
Connect the tool to a Peer
- Open the Peer.
- Go to Tools.
- Add the MCP tool.
- Restrict the available actions to only what the Peer needs.
- Test the Peer with a low-risk request.
Use the tool in a Flow
In a Flow, add or configure an agent step and select the actions the agent is allowed to use. Keep the allowed action list narrow so the Flow remains predictable.
Review or test the result
Before rollout:
- Confirm the Peer or Flow can call only the intended actions.
- Test success and failure cases.
- Verify sensitive actions require approval.
- Check that tool errors produce clear user-facing messages.
Troubleshooting
The server does not connect
Check the server URL, credentials, and network access. If the server is managed by another team, confirm it is reachable from Studio.
Unexpected tools appear
Review the discovered tool list and restrict what the Peer or Flow can use. Do not expose broad or destructive actions unless they are protected by approval policies.
Tool calls are slow
Check the external server's availability and latency. A slow tool server will slow down the Peer or Flow that depends on it.