TCL

Provides a safe MCP server to execute TCL scripts, manage MCP tool ecosystems, and orchestrate external MCP servers.

rust

15

GitHub Stars

rust

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "cyberdione-mcp-tcl-udf-server": {
      "command": "tcl-mcp-server",
      "args": [
        "mcp",
        "add",
        "claude-flow",
        "Claude Flow",
        "--",
        "npx",
        "claude-flow@alpha",
        "mcp",
        "start"
      ]
    }
  }
}

You run a TCL MCP Server to safely execute TCL scripts, orchestrate MCP tool ecosystems, and coordinate multiple MCP endpoints from AI agents or other clients. It emphasizes safety by default with sandboxed Molt runtime while still offering full TCL capabilities when you explicitly opt in, making it ideal for complex scripting and tool management across MCP servers.

How to use

You interact with the MCP server through an MCP client by issuing management and execution commands that run TCL code, list and manage tools, and coordinate external MCP servers. Use the server to run small TCL scripts, create and organize tools, and maintain connections to other MCP endpoints for a unified scripting environment. Privileged mode lets you save and persist scripts and tools, while the default mode remains safe and sandboxed for day-to-day use.

How to install

Prerequisites: you need Rust tooling installed on your system to build or install the server.

Install the server from source or binaries.

Using cargo to install the server in release mode and run it in its default Molt runtime.

Advanced usage

Run with privileged access to save and store scripts and tools.

Runtime options

You can choose between two TCL runtime implementations. Molt Runtime is the default and is memory-safe with sandboxed execution. TCL Runtime gives full language features but requires careful input validation.

MCP server management

Add external MCP servers to your network, list all servers, and test connectivity. This enables you to coordinate multiple MCP endpoints from a single control point.

Tool organization

Tools are organized using a namespace system and follow MCP-compatible naming conventions. Examples include bin__tcl_execute for running TCL scripts, user__alice__utils__reverse_string for user-created tools, and mcp__context7__get_library_docs for external server tools.

Running the server

Start in default read-only mode to explore capabilities. Use privileged mode to enable saving and storing scripts and tools. The CLI supports commands to execute TCL, list tools, get tool information, and manage MCP servers.

MCP client integration

Configure MPC clients to connect to your server by providing the appropriate command and runtime. For example, you can point a client to the runtime you selected (Molt or TCL) and enable privileged or read-only operation as needed.

Built-in tools and management

Core tools are always available to execute TCL scripts and list tools, while privileged management tools enable creating new tools and wiring new MCP servers programmatically.

Runtime capability detection

Query the server for runtime capabilities to tailor code generation and execution behavior to the safe Molt or full TCL runtime.

Available tools

bin__tcl_execute

Execute TCL scripts via the MCP server and return results.

bin__list_tools

List available tools within a namespace and optional filter.

docs__molt_book

Access TCL documentation through the built-in Molt reference.

sbin__tcl_tool_add

Create custom tools in privileged mode by supplying tool metadata and TCL script.

sbin__mcp_add

Add MCP servers programmatically with a structured configuration.