Universal Tool Calling Protocol (utcp Client) MCP Server

@universal-tool-calling-protocol

代码仓库

基本信息

分类

其他

传输方式

stdio

作者

universal-tool-calling-protocol

提交者

Radulescu Razvan

关于 Universal Tool Calling Protocol (utcp Client) MCP Server

暂无概览

#utcp#mcp #protocol

Universal Tool Calling Protocol (utcp Client) MCP Server 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "simple-utcp-client-mcp": {
      "command": "uv",
      "args": [
        "run",
        "--script",
        "path\\to\\simple-utcp-client-mcp.py"
      ]
    }
  }
}

Universal Tool Calling Protocol (utcp Client) MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表，不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Universal Tool Calling Protocol (utcp Client)?

Universal Tool Calling Protocol (utcp Client) is an MCP server that acts as a bridge between the Universal Tool Calling Protocol (UTCP) ecosystem and any MCP client. It exposes all tools registered via UTCP as MCP-compatible tools and provides a direct UTCP client interface for registering, deregistering, searching, and calling tools. It is designed for developers who need a single integration point to manage and extend their tool ecosystem.

How to use Universal Tool Calling Protocol (utcp Client)?

Install the server using Docker (docker-compose up --build), a bash script (./run.sh), or a PowerShell script (./run.ps1). Alternatively, for a standalone UTCP client, download simple-utcp-client-mcp.py and configure your MCP client with the uv command and script path. The server exposes HTTP endpoints on ports 8776 (UTCP Client MCP), 8777 (UTCP Proxy MCP), and 8778 (web UI). Connect your MCP client by adding entries for utcp-client-mcp-local and/or utcp-proxy-mcp-local with the appropriate URLs.

Key features of Universal Tool Calling Protocol (utcp Client)

Registers and deregisters UTCP providers directly.
Searches and calls tools registered via UTCP.
Proxies all UTCP tools as MCP-compatible tools.
Provides a web UI to manage providers and tools.
Supports Docker and local script deployment.
Configurable via .utcp_config.json or environment variables.

Use cases of Universal Tool Calling Protocol (utcp Client)

Expose a collection of UTCP-registered tools to any MCP client (e.g., Cursor, VS Code).
Manage provider registration and tool enabling/disabling through a browser interface.
Use the UTCP client directly within an MCP workflow without separate setup.
Centralize tool management across multiple providers in a single MCP server.

常见问题

What is the difference between the UTCP client and UTCP proxy modes?

The UTCP client mode lets you register, deregister, search, and call UTCP providers directly. The UTCP proxy mode exposes all tools already registered via UTCP as MCP tools without needing direct management.

What are the runtime dependencies?

Python 3, `uv` (package manager), and Docker (optional). The server automatically installs Python packages: `utcp`, `fastmcp`, `fastapi`, and `python-dotenv`.

Where does the server store provider and tool definitions?

Provider and tool definitions are loaded from the `data/` directory (e.g., `data/providers.json`). You can also specify a `providers_file_path` in `.utcp_config.json`.

What transport does the server use?

The server communicates via HTTP on ports `8776` (UTCP client MCP), `8777` (UTCP proxy MCP), and `8778` (web UI). No authentication or TLS is mentioned in the README.

What are the known limitations?

The README does not document any specific limitations. The web UI is described as having more features "coming soon."

其他分类下的更多 MCP 服务器

Hindsight

vectorize-io

Hindsight: Agent Memory That Learns

50.4K

The Living Bread

A free remote MCP server for The Living Bread. Bible passages read word for word from a stored public domain text with an evidence label, keyword search and cross references, real churches, gatherings and prayer groups w