UTCP Tools Bridge

Create a .utcp_config.json file that defines your tool sources. This file specifies manual call templates (HTTP endpoints, OpenAPI specs), environment variable sources, post-processing rules, and tool repository settings.

{
  "load_variables_from": [".env"],
  "manual_call_templates": [
    {
      "type": "http",
      "name": "my-api",
      "base_url": "https://api.example.com"
    }
  ],
  "tool_repository": { "type": "memory" }
}

Register the UTCP bridge in your MCP client config. Set the UTCP_CONFIG_FILE env var to the absolute path of your config file. The bridge is launched via npx.

{
  "mcpServers": {
    "utcp": {
      "command": "npx",
      "args": ["@utcp/mcp-bridge"],
      "env": {
        "UTCP_CONFIG_FILE": "/absolute/path/to/.utcp_config.json"
      }
    }
  }
}

If you are using Claude Code, you can add the server using the CLI directly with the claude mcp add-json command.

claude mcp add-json --scope user utcp '{"type":"stdio","command":"npx","args":["@utcp/mcp-bridge"],"env":{"UTCP_CONFIG_FILE":"/absolute/path/to/.utcp_config.json"}}'

Restart Claude Desktop or reload your MCP client configuration. The bridge will read your UTCP config and register all defined tools on startup.

The bridge provides a built-in web interface for registering and deregistering UTCP manuals, searching available tools, and inspecting tool schemas without editing the config file.