Skip to content
Back to search

utcp-mcp

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

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/universal-tool-calling-protocol--utcp-mcp/badge.svg)](/listings/universal-tool-calling-protocol--utcp-mcp)

HTML

<a href="/listings/universal-tool-calling-protocol--utcp-mcp"><img src="/api/listings/universal-tool-calling-protocol--utcp-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Add this configuration to your MCP client (Claude Desktop, etc.):

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

**That's it!** No installation required. The bridge will automatically: - Download and run the latest version via npx - Load your UTCP configuration from the specified path - Register all your UTCP manuals as MCP tools - Provide a unified interface to manage your tool ecosystem

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 144 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # UTCP-MCP Bridge
  2. **The last MCP server you'll ever need.**
  3. A universal, all-in-one MCP server that brings the full power of the Universal Tool Calling Protocol (UTCP) to the MCP ecosystem.
  4. ## 🚀 Quick Start
  5. Add this configuration to your MCP client (Claude Desktop, etc.):
  6. ```json
  7. {
  8. "mcpServers": {
  9. "utcp": {
  10. "command": "npx",
  11. "args": ["@utcp/mcp-bridge"],
  12. "env": {
  13. "UTCP_CONFIG_FILE": "/path/to/your/.utcp_config.json"
  14. }
  15. }
  16. }
  17. }
  18. ```
  19. **That's it!** No installation required. The bridge will automatically:
  20. - Download and run the latest version via npx
  21. - Load your UTCP configuration from the specified path
  22. - Register all your UTCP manuals as MCP tools
  23. - Provide a unified interface to manage your tool ecosystem
  24. ## 🔧 Configuration
  25. Create a `.utcp_config.json` file to configure your tools and services:
  26. ```json
  27. {
  28. "load_variables_from": [
  29. {
  30. "variable_loader_type": "dotenv",
  31. "env_file_path": ".env"
  32. }
  33. ],
  34. "manual_call_templates": [
  35. {
  36. "name": "openlibrary",
  37. "call_template_type": "http",
  38. "http_method": "GET",
  39. "url": "https://openlibrary.org/static/openapi.json",
  40. "content_type": "application/json"
  41. }
  42. ],
  43. "post_processing": [
  44. {
  45. "tool_post_processor_type": "filter_dict",
  46. "only_include_keys": ["name", "description"],
  47. "only_include_tools": ["openlibrary.*"]
  48. }
  49. ],
  50. "tool_repository": {
  51. "tool_repository_type": "in_memory"
  52. },
  53. "tool_search_strategy": {
  54. "tool_search_strategy_type": "tag_and_description_word_match"
  55. }
  56. }
  57. ```
  58. ### Claude Code (CLI)
  59. For [Claude Code](https://claude.com/claude-code) (the CLI / IDE extension), register the bridge as a user-scoped MCP server:
  60. ```bash
  61. 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"}}'
  62. ```
  63. Then restart Claude Code. Verify with `claude mcp list`. Remove with `claude mcp remove utcp --scope user`.
  64. ## 🧪 Local development against the bridge
  65. If you're hacking on `@utcp/sdk` or any other [typescript-utcp](https://github.com/universal-tool-calling-protocol/typescript-utcp) package and want to exercise it through Claude Code, use the dev scripts:
  66. ```bash
  67. cd utcp-mcp
  68. npm install
  69. npm run dev:register # builds typescript-utcp packages, overlays each into the bridge's node_modules, builds the bridge, and registers it as 'utcp-dev' in Claude Code
  70. # restart Claude Code
  71. # After every edit:
  72. npm run dev:register # rebuilds, re-registers; restart Claude Code
  73. # When done:
  74. npm run dev:unregister # removes the MCP entry and restores registry node_modules
  75. ```
  76. Both scripts are idempotent and never mutate `package.json`. The overlay strategy avoids `npm link`, which under modern npm aliases `unlink` to `uninstall --save` and would silently strip the dependency.
  77. The script expects the typescript-utcp checkout to live next to this repo (`../typescript-utcp`). Override with flags if not:
  78. - `--lib-dir <path>` — point at a different typescript-utcp checkout, or pass `none` to skip the overlay step entirely (useful when only editing the bridge)
  79. - `--name <mcp-name>` (default `utcp-dev`) — useful if you want the dev bridge alongside a published one
  80. - `--config <path>` (default `./.utcp_config.json`) — point at a different UTCP config
  81. ## 🛠️ Available MCP Tools
  82. The bridge exposes these MCP tools for managing your UTCP ecosystem:
  83. - **`register_manual`** - Register new UTCP manuals/APIs
  84. - **`deregister_manual`** - Remove registered manuals
  85. - **`call_tool`** - Execute any registered UTCP tool
  86. - **`search_tools`** - Find tools by description
  87. - **`list_tools`** - List all registered tool names
  88. - **`get_required_keys_for_tool`** - Get required environment variables
  89. - **`tool_info`** - Get complete tool information and schema
  90. ## 📁 What is UTCP?
  91. The Universal Tool Calling Protocol (UTCP) allows you to:
  92. - **Connect to any API** via HTTP, OpenAPI specs, or custom formats
  93. - **Use command-line tools** with automatic argument parsing
  94. - **Process text and files** with built-in utilities
  95. - **Chain and combine** multiple tools seamlessly
  96. With this MCP bridge, all your UTCP tools become available in Claude Desktop and other MCP clients.
  97. ## 🌟 Features
  98. - ✅ **Zero installation** - Works via npx
  99. - ✅ **Universal compatibility** - Works with any MCP client
  100. - ✅ **Dynamic configuration** - Update tools without restarting
  101. - ✅ **Environment isolation** - Each project can have its own config
  102. - ✅ **Comprehensive tool management** - Register, search, call, and inspect tools
  103. - ✅ **Web interface available** - See [web_ui_utcp_mcp_bridge/](web_ui_utcp_mcp_bridge/)
  104. ## 🐍 Python Version
  105. For Python users, see the standalone Python implementation in [`python_mcp_bridge/`](python_mcp_bridge/)
  106. ## 🌐 Web Interface
  107. For advanced management with a web UI, check out [`web_ui_utcp_mcp_bridge/`](web_ui_utcp_mcp_bridge/)
  108. ---
  109. <img width="2263" height="976" alt="UTCP MCP Bridge Interface" src="https://github.com/user-attachments/assets/a6759512-1c0d-4265-9518-64916fbe1428" />

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.