All-in-one MCP server that can connect your AI agents to any native endpoint, powered by UTCP
# Add to your Claude Code skills
git clone https://github.com/universal-tool-calling-protocol/utcp-mcpLast scanned: 5/30/2026
{
"issues": [
{
"type": "npm-audit",
"message": "@modelcontextprotocol/sdk: Anthropic's MCP TypeScript SDK has a ReDoS vulnerability",
"severity": "high"
}
],
"status": "WARNING",
"scannedAt": "2026-05-30T15:42:10.827Z",
"npmAuditRan": true,
"pipAuditRan": true
}utcp-mcp is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by universal-tool-calling-protocol. All-in-one MCP server that can connect your AI agents to any native endpoint, powered by UTCP. It has 201 GitHub stars.
utcp-mcp returned warnings in SkillsLLM's automated security scan. It has no critical vulnerabilities, but review the flagged issues in the Security Report section before adding it to your workflow.
Clone the repository with "git clone https://github.com/universal-tool-calling-protocol/utcp-mcp" and add it to your Claude Code skills directory (see the Installation section above).
utcp-mcp is primarily written in Python. It is open-source under universal-tool-calling-protocol on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh utcp-mcp against similar tools.
No comments yet. Be the first to share your thoughts!
Requires a passing catalog security scan. Resolve the flagged issues and resubmit to enable featuring.
The last MCP server you'll ever need.
A universal, all-in-one MCP server that brings the full power of the Universal Tool Calling Protocol (UTCP) to the MCP ecosystem.
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:
Create a .utcp_config.json file to configure your tools and services:
{
"load_variables_from": [
{
"variable_loader_type": "dotenv",
"env_file_path": ".env"
}
],
"manual_call_templates": [
{
"name": "openlibrary",
"call_template_type": "http",
"http_method": "GET",
"url": "https://openlibrary.org/static/openapi.json",
"content_type": "application/json"
}
],
"post_processing": [
{
"tool_post_processor_type": "filter_dict",
"only_include_keys": ["name", "description"],
"only_include_tools": ["openlibrary.*"]
}
],
"tool_repository": {
"tool_repository_type": "in_memory"
},
"tool_search_strategy": {
"tool_search_strategy_type": "tag_and_description_word_match"
}
}
For Claude Code (the CLI / IDE extension), register the bridge as a user-scoped MCP server:
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"}}'
Then restart Claude Code. Verify with claude mcp list. Remove with claude mcp remove utcp --scope user.
If you're hacking on @utcp/sdk or any other typescript-utcp package and want to exercise it through Claude Code, use the dev scripts:
cd utcp-mcp
npm install
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
# restart Claude Code
# After every edit:
npm run dev:register # rebuilds, re-registers; restart Claude Code
# When done:
npm run dev:unregister # removes the MCP entry and restores registry node_modules
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.
The script expects the typescript-utcp checkout to live next to this repo (../typescript-utcp). Override with flags if not:
--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)--name <mcp-name> (default utcp-dev) — useful if you want the dev bridge alongside a published one--config <path> (default ./.utcp_config.json) — point at a different UTCP configThe bridge exposes these MCP tools for managing your UTCP ecosystem:
register_manual - Register new UTCP manuals/APIsderegister_manual - Remove registered manualscall_tool - Execute any registered UTCP toolsearch_tools - Find tools by descriptionlist_tools - List all registered tool namesget_required_keys_for_tool - Get required environment variablestool_info - Get complete tool information and schemaThe Universal Tool Calling Protocol (UTCP) allows you to:
With this MCP bridge, all your UTCP tools become available in Claude Desktop and other MCP clients.
For Python users, see the standalone Python implementation in python_mcp_bridge/
For advanced management with a web UI, check out web_ui_utcp_mcp_bridge/