MCP tools connect to your server over one of two transports. The transport must match what your MCP server implements — a mismatch causes connection or discovery failures.
| Transport | Description |
|---|
| streamable-http | HTTP-based streaming MCP (recommended for new deployments) |
| sse | Server-Sent Events transport for MCP over HTTP |
| Field | Detail |
|---|
| Server URL | Full HTTPS URL to your MCP endpoint |
| Transport | streamable-http or sse |
| Credential | Optional Bearer or API key if the endpoint is protected |
| Use streamable-http when | Use sse when |
|---|
| Your MCP SDK/docs specify streamable HTTP | Your server only exposes SSE |
| You want modern MCP defaults | Migrating an existing SSE MCP gateway |
- Valid TLS certificate (HTTPS).
- CORS and network access allow Chatevo’s execution environment to reach the URL.
- Tool list and schemas exposed per MCP spec so Chatevo can register them with the model.
- Save the MCP tool with the correct transport.
- Open Test a tool and run a discovered tool.
- Check execution logs for connection errors vs parameter errors.
