MCP Script Runner

Example Use Cases

• 1

  Run arbitrary local command-line tools as MCP-exposed commands by dropping executable scripts into a commands directory.

• 2

  Expose small automation scripts or utilities to other tools via the uv/mcp integration without building a full server.

• 3

  Run environment-variable-driven scripts locally (supports .env and COMMAND_DIRECTORY overrides) for development and testing.

Description

MCP Script Runner lets you expose local executable scripts as MCP server commands using the uv runtime. You configure it by adding an entry to your mcp.json, place executable scripts (with shebangs) in the commands directory, and optionally use a .env file or set COMMAND_DIRECTORY to change where commands are read from. It's intended for local use only and includes precautions about execution permissions and only running trusted scripts.