Connect with agent
How a generated MCP server connects to your Tuix agent, and to any other MCP-compatible agent.
A generated MCP server is a standard, standalone Streamable HTTP MCP server. Nothing ties it exclusively to Tuix AI Agents: it also connects to your Tuix agent automatically and can be called by any other MCP-compatible agent.
Connect with your Tuix agent
Once a server reaches Deployed on an application's MCP Servers tab, it is automatically attached to that application's agent. There is no separate "connect" step: the agent can call its tools on the very next message.
Connect with external agents
Any MCP-compatible client that supports Streamable HTTP can connect directly to the generated server's URL. For example, with the Claude Code CLI:
If the endpoints you exposed use security, pass the credential your API
expects as a Bearer token, exactly as your API would receive it directly.
The generated server also accepts a static x-api-key header for endpoints
that authenticate that way. Send the key as x-api-key, and set
Authorization: Bearer none:
Most other MCP clients that support remote, Streamable HTTP servers accept the same shape through a JSON configuration instead of a CLI command, along these lines (check your client's own documentation for the exact field names):
Convert to stdio
Some agents, notably Claude Desktop, only speak the older stdio transport
and cannot call a Streamable HTTP server directly. Bridge the two with
mcp-remote, which runs locally
over stdio and forwards to your remote MCP server over HTTP: