MCP.so
Sign In
U

Universal Tool Calling Protocol (utcp Client)

@universal-tool-calling-protocol

Repository

About Universal Tool Calling Protocol (utcp Client)

No overview available yet

#utcp#mcp#protocol

Config

Add this server to your MCP-compatible client using the configuration below.

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

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

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.

FAQ from Universal Tool Calling Protocol (utcp Client)

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."

Frequently asked questions

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."

Comments

Basic information

Category

Other

Transports

stdio

Author

universal-tool-calling-protocol

Submitted by

Radulescu Razvan

More Other MCP servers

IDA Pro MCP

mrexodia

AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.

9.9K

🚀 Model Context Protocol (MCP) Curriculum for Beginners

microsoft

This open-source curriculum introduces the fundamentals of Model Context Protocol (MCP) through real-world, cross-language examples in .NET, Java, TypeScript, JavaScript, Rust and Python. Designed for developers, it focuses on practical techniques for building modular, scalable,

16.7K

Unity MCP ✨

justinpbarnett

Unity MCP acts as a bridge between AI assistants and your Unity Editor. Give your LLM tools to manage assets, control scenes, edit scripts, and automate tasks within Unity.

12.2K

MCP Toolbox for Databases

googleapis

MCP Toolbox for Databases is an open source MCP server for databases.

15.9K

Inbox Zero AI MCP

elie222

The world's best AI personal assistant for email. Open source app to help you reach inbox zero fast.

11.6K