create_mcp_server
Register an external MCP server for an agent over HTTP or stdio, configure authentication and timeouts, and enable the agent to discover and call its tools.
Instructions
Register an external MCP server for an agent. Use http (Streamable HTTP) or stdio (local development). Authentication: none; bearer with config.vault_secret_id; api_key with vault_secret_id and optional api_key_header; tunnel uses platform authentication. timeout controls connection and tool discovery; call_timeout_ms controls each tool call (1000–120000 ms, default 30000). Timed-out calls are not retried automatically. Read zihin://schemas/mcp_resource_config for headers and defaults_from_context.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"agent_id": "<agent_id>",
"name": "<name>",
"endpoint": "<endpoint>"
},
"name": "create_mcp_server"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | MCP server name | |
| config | No | Additional configuration: vault_secret_id, headers, connection timeout and per-tool call_timeout_ms | |
| agent_id | Yes | Agent UUID | |
| endpoint | Yes | Endpoint URL or stdio command | |
| transport | No | Transport type | http |
| auth_method | No | Authentication method; OAuth is not yet supported for this external-server configuration | none |
| description | No | Server description | |
| integration_id | No | Optional registered integration link; see list_integrations. With tunnel authentication, destination access requires an active integration grant. For other authentication methods, the link is informational. |