Script Wrapper MCP Server

If you want an AI assistant working directly with Script Wrapper, the script wrapper mcp server is the bridge. A Model Context Protocol (MCP) server that provides coding agents with a generic interface to execute developer-defined bash scripts within a Dockerized environment.

What Script Wrapper does

A Model Context Protocol (MCP) server that provides coding agents with a generic interface to execute developer-defined bash scripts within a Dockerized environment.

Tools it exposes

Once connected, the assistant can call these 8 tools directly:

• run_script — Execute a configured script
• list_scripts — List all available scripts
• get_script_info — Get script details
• get_working_directory — Get current working directory
• set_working_directory — Set working directory
• reload_config — Reload configuration file
• Prerequisites — The Prerequisites tool exposed by this server
• Contributing — 1. Fork the repository 2. Create feature branch 3. Add tests for new functionality 4. Test with Docker: docker compose up --build 5. Submit pull request

Installing the script wrapper mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

The server reads one environment variable: PYTHONPATH. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Python 3.11+ - Docker (for containerized execution) - Bash-compatible shell

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Script Wrapper sits in that group, and the shape of its toolset — run_script, list_scripts, get_script_info among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• With 8 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Script Wrapper.
• Maintained by ceyhunkoc, written in Python.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the script wrapper mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.