Skip to main content
Glama

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

NameRequiredDescriptionDefault
nameYesMCP server name
configNoAdditional configuration: vault_secret_id, headers, connection timeout and per-tool call_timeout_ms
agent_idYesAgent UUID
endpointYesEndpoint URL or stdio command
transportNoTransport typehttp
auth_methodNoAuthentication method; OAuth is not yet supported for this external-server configurationnone
descriptionNoServer description
integration_idNoOptional registered integration link; see list_integrations. With tunnel authentication, destination access requires an active integration grant. For other authentication methods, the link is informational.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.2.4
    • changedInput schema / properties / agent_id / description
      Previous value: -"UUID do agente"New value: +"Agent UUID"
    • changedInput schema / properties / auth_method / description
      Previous value: -"Método de autenticação (oauth ainda não disponível)"New value: +"Authentication method; OAuth is not yet supported for this external-server configuration"
    • changedInput schema / properties / config / description
      Previous value: -"Configuração adicional (vault_secret_id, headers, timeout de conexão, call_timeout_ms por chamada de tool)"New value: +"Additional configuration: vault_secret_id, headers, connection timeout and per-tool call_timeout_ms"
    • changedInput schema / properties / description / description
      Previous value: -"Descrição do server"New value: +"Server description"
    • changedInput schema / properties / endpoint / description
      Previous value: -"URL do endpoint ou comando stdio"New value: +"Endpoint URL or stdio command"
    • addedInput schema / properties / integration_id
      Added value: +{
      +  "description": "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.",
      +  "format": "uuid",
      +  "type": "string"
      +}
    • changedInput schema / properties / name / description
      Previous value: -"Nome do MCP server"New value: +"MCP server name"
    • changedInput schema / properties / transport / description
      Previous value: -"Tipo de transporte"New value: +"Transport type"
  2. Changed2 schema fields changedv2.2.3
    • changedInput schema / properties / auth_method / description
      Previous value: -"Método de autenticação"New value: +"Método de autenticação (oauth ainda não disponível)"
    • changedInput schema / properties / auth_method / enum
      Previous value: -[
      -  "none",
      -  "bearer",
      -  "api_key",
      -  "tunnel",
      -  "oauth"
      -]New value: +[
      +  "none",
      +  "bearer",
      +  "api_key",
      +  "tunnel"
      +]
  3. Changed1 schema field changedv2.2.2
    • changedInput schema / properties / config / description
      Previous value: -"Configuração adicional (vault_secret_id, headers, timeout)"New value: +"Configuração adicional (vault_secret_id, headers, timeout de conexão, call_timeout_ms por chamada de tool)"
  4. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare it as a non-destructive, non-idempotent write, whereas the description carries the real behavioral burden: authentication prerequisites per mode (vault_secret_id, api_key_header, tunnel platform auth), the split between connection-level timeout and per-call call_timeout_ms with its 1000–120000 ms bounds and 30000 ms default, and the explicit warning that timed-out calls are not retried automatically.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose leads, then transport, auth, and timing details follow in tight clause-per-topic form with no filler. Parenthetical clarifications ('Streamable HTTP', the ms range and default) are load-bearing rather than decorative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter tool with a nested object and no output schema, the description covers transport, auth, timing, and points to zihin://schemas/mcp_resource_config for headers and defaults_from_context. The only gap is that it never indicates what a successful registration returns (e.g., a server ID) for subsequent get_mcp_server or test_mcp_server calls.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the schema baseline is 3; the description earns above that by explaining how auth_method interacts with the nested config object (which auth modes require vault_secret_id, which allow an optional api_key_header) and by clarifying the timeout versus call_timeout_ms distinction. It does not explain the informational-versus-access-granting role of integration_id beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence states a specific verb and resource ('Register an external MCP server for an agent'), which separates it cleanly from update_mcp_server, delete_mcp_server, and the non-MCP create_* siblings. An agent can identify the operation without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete selection guidance for the transport parameter ('http (Streamable HTTP) or stdio (local development)') and enumerates the four auth methods with their required config. It does not, however, state when to prefer this over create_integration or when registration should be skipped in favor of update_mcp_server.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools