@utcp/code-mode-mcp
v1.2.1
Published
Model Context Protocol (MCP) server for UTCP Code Mode - Execute TypeScript code with direct tool access
Maintainers
Readme
UTCP Code Mode MCP Bridge
Execute TypeScript code with direct tool access through MCP.
An advanced MCP server that brings UTCP Code Mode to the MCP ecosystem, allowing you to execute TypeScript code with all registered tools available as native TypeScript functions.
🚀 Quick Start
Add this configuration to your MCP client (Claude Desktop, etc.):
{
"mcpServers": {
"utcp-codemode": {
"command": "npx",
"args": ["@utcp/code-mode-mcp"],
"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 tools available in TypeScript code
- Enable TypeScript code execution with hierarchical tool access (e.g.,
manual.tool())
🔧 Configuration
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"
}
}Protocol plugins
Each call_template_type (http, mcp, cli, text, file, ...) lives in
its own @utcp/<name> package and registers itself as a side effect of being
imported — the bridge already imports the bundled set in
index.ts. To add a new transport, install the package and add
a top-level import "@utcp/<name>" line; no manual register() call needed.
Security note: the @utcp/cli plugin lets a manual run arbitrary local
commands. It's bundled and active by default; only register manuals from
sources you trust.
Claude Code (CLI)
For Claude Code (the CLI / IDE extension), register the bridge as a user-scoped MCP server:
claude mcp add-json --scope user utcp-codemode '{"type":"stdio","command":"npx","args":["@utcp/code-mode-mcp"],"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-codemode --scope user.
🧪 Local development against the bridge
If you're hacking on @utcp/code-mode (the sibling typescript-library/ package) and want to exercise it through Claude Code, use the dev scripts:
cd code-mode-mcp
npm install
npm run dev:register # builds lib + bridge, overlays the lib build into the bridge's node_modules, registers as 'utcp-codemode-dev' in Claude Code
# restart Claude Code, then call mcp__utcp-codemode-dev__call_tool_chain to test
# 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 the registry @utcp/code-modeBoth 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.
Flags:
--name <mcp-name>(defaultutcp-codemode-dev) — useful if you want the dev bridge alongside a published one--config <path>(default./.utcp_config.json) — point at a different UTCP config
🛠️ Available MCP Tools
The bridge exposes these MCP tools for managing your UTCP Code Mode ecosystem:
register_manual- Register new UTCP manuals/APIsderegister_manual- Remove registered manualssearch_tools- Find tools by description with TypeScript interfaceslist_tools- List all registered tool namesget_required_keys_for_tool- Get required environment variablestool_info- Get complete tool information with TypeScript interfacecall_tool_chain- Execute TypeScript code with direct tool access
📁 What is UTCP?
The Universal Tool Calling Protocol (UTCP) allows you to:
- Connect to any API via HTTP, OpenAPI specs, or custom formats
- Use command-line tools with automatic argument parsing (requires explicit CLI plugin registration)
- Process text and files with built-in utilities
- Chain and combine multiple tools seamlessly
With this MCP bridge, all your UTCP tools become available in Claude Desktop and other MCP clients.
Security note: @utcp/cli allows manuals to run arbitrary local commands — only register manuals from sources you trust.
💻 Code Mode Example
The main feature of this bridge is the ability to execute TypeScript code with direct access to all registered tools:
// Example using call_tool_chain
const result = await call_tool_chain(`
// Get user data from an API
const user = await user_service.getUserProfile({ userId: "123" });
console.log('User data:', user);
// Process the data with another tool
const processed = await data_processor.analyzeUserBehavior({
userData: user,
timeframe: "30days"
});
// Generate a report
const report = await reporting.generateInsights({
analysis: processed,
format: "summary"
});
return {
userId: user.id,
totalActions: processed.actionCount,
topInsight: report.insights[0]
};
`);Key Benefits:
- Hierarchical Access: Use
manual.tool()syntax to avoid naming conflicts - Type Safety: Get TypeScript interfaces for all tools via
search_toolsortool_info - Code Execution: Chain multiple tool calls in a single code block
- Error Handling: Proper error handling with timeout support
🌟 Features
- ✅ Zero installation - Works via npx
- ✅ Universal compatibility - Works with any MCP client
- ✅ Dynamic configuration - Update tools without restarting
- ✅ Environment isolation - Each project can have its own config
- ✅ Comprehensive tool management - Register, search, call, and inspect tools
