UTCP-MCP Bridge

All-in-one MCP server that can connect your AI agents to any native endpoint, powered by UTCP

python

189

GitHub Stars

python

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

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

You are about to run a universal MCP server that brings UTCP tools into your MCP client ecosystem, enabling centralized management and seamless tool orchestration without extra setup.

How to use

To use this MCP server with your MCP client, add a stdio-based MCP connection that runs via npx and points to the UTCP bridge package. You only need to configure the bridge once in your MCP client, and it will automatically load your UTCP configuration and expose all UTCP tools through the MCP interface.

How to install

Prerequisites: make sure you have Node.js and npm or npx installed on the machine where you run your MCP client.

Ensure you have a path for your UTCP configuration file, for example /path/to/your/.utcp_config.json.
In your MCP client configuration, add the UTCP bridge as a new MCP server entry using the following settings.

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

Additional configuration and notes

Create a .utcp_config.json file to configure your UTCP tools and services. You can define how variables are loaded, which tools are exposed, and how you want results to be processed. The bridge will load your UTCP configuration from the path you specify and register all UTCP manuals as MCP tools.

Example configuration elements you can include in .utcp_config.json are variable loaders, manual call templates, post-processing rules, and tool repositories. You can also define a search strategy and keep tools isolated per project.

Security and management notes

Environment isolation is supported, so each project can provide its own UTCP config. Be mindful of which UTCP manuals you register and expose through MCP to avoid leaking sensitive information.

Tool and endpoint overview

This bridge exposes a set of MCP actions to manage UTCP workflows, including registering and deregistering manuals, calling tools, searching and listing tools, and inspecting tool information and required environment variables.

Available tools

register_manual

Register new UTCP manuals/APIs so they become available as MCP tools.

deregister_manual

Remove registered UTCP manuals from the MCP bridge.

call_tool

Execute any registered UTCP tool via MCP, routing the call through UTCP.

search_tools

Find UTCP tools by description or metadata to discover capabilities.

list_tools

List all registered UTCP tool names currently available in the bridge.

get_required_keys_for_tool

Retrieve the environment variables required for a specific UTCP tool.

tool_info

Get complete information and schema for a registered UTCP tool.