Connect MCP Servers
Connect a Model Context Protocol Server over stdio, SSE, or HTTP
MCP tools are configured in Capabilities > Tools > Create Tool > MCP Server. Before saving, use Fetch Tool List to check whether the server is reachable and which tools it exposes.
Transports
| Transport | Required connection fields | Use case |
|---|---|---|
stdio | command, args, env | Talk to a local command or container process |
sse | url, optional headers | Connect to an SSE MCP endpoint |
http | url, optional headers | Connect to an HTTP MCP endpoint |
- Fill in the tool name and description.
- Select the transport type and fill in the connection info.
- Select Fetch Tool List and confirm the tool names, descriptions, and JSON Schema parameters.
- Save and run a test in the tool list.
Security Boundaries
- Do not write private Tokens into public documents or share them with teams that do not need them.
- Use HTTPS and minimal headers for remote MCP endpoints.
- Restrict the source of
stdiocommands and avoid building commands from untrusted input. - MCP call timeouts default to
60seconds; failures are recorded in the Agent or Workflow run trace.
Common Errors
Fetch tool list failed usually means the command does not exist, the process exited, the URL is unreachable, the protocol type does not match, or the headers are invalid. Confirm the connection error in the server logs first, then reload the tool in Clouisle.
How is this guide?