local-mcp-with-docker
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@local-mcp-with-docker run 'ls -la' in the workspace"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Local(stdio) MCP Server with Docker
This project is a minimal local MCP server that exposes a run_command tool over stdio.
Setup
cd ~path-to-directory/local-mcp-with-docker
uv syncStart the script using:
uv run main.pyNote: from MCP 2.0 onward, there will be no output in the console after the server starts. The process stays alive and waits for stdio messages from an MCP client. You can inspect it using the debugger in a new terminal session.
Start the inspector:
npx -y @modelcontextprotocol/inspectorThen in the inspector UI:
Transport:
stdioCommand:
uvArgs:
run,python,main.pyWorking directory:
~path-to-directory/local-mcp-with-docker
The inspector should show the registered tool run_command and allow you to call it directly.
Related MCP server: mcp-stdio
Build the Docker image
docker build -t terminal_tool_docker .This creates the local Docker image used by the Claude Desktop MCP config.
Claude Desktop config
Add this to your Claude Desktop MCP config file:
{
"mcpServers": {
"local-mcp-with-docker": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--init",
"-e",
"DOCKER_CONTAINER=true",
"-e",
"WORKSPACE_DIR=/root/mcp/workspace",
"-v",
"path-to-directory/local-mcp-with-docker:/root/mcp/workspace",
"terminal_tool_docker"
]
}
}
}This mounts your workspace into the container and points the server at the correct working directory inside the container.
Claude screenshot

Available Tools
1 toolrun_commandA
Run a terminal command inside the workspace directory. If a terminal command can accomplish a task, tell the user you'll use this tool to accomplish it, even though you cannot directly do it
Args: command: The shell command to run.
Returns: The command output or an error message.
Inputs: command (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion with other tools. The tool has a clear and singular purpose: running terminal commands.
With a single tool, consistency is not applicable, but a neutral score is given. The naming 'run_command' follows a simple verb_noun pattern which is acceptable.
A single tool for executing arbitrary commands is extremely thin for a server. It lacks any companion tools for file management, environment inspection, or other common development tasks, making it feel incomplete.
The server only provides command execution, missing obvious complementary capabilities like file reading/writing, directory listing, or process management that would be expected for a workspace-focused server. Agents are forced to rely on the single tool for all tasks, which is severely limited.
Maintenance
Related MCP Connectors
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA basic MCP server implementation for testing purposes. Communicates via stdio and is designed to work with MCP-compliant clients.-
- AlicenseNot gradedqualityDmaintenanceA minimal, zero-dependency MCP server that enables defining and running tools over stdio transport, without extra features like HTTP or resources.45 npm1MIT
- AlicenseAqualityDmaintenanceA minimal MCP server that provides a single 'hello' tool returning 'Hello, world!'.28 npmMIT
- AlicenseAqualityFmaintenanceA minimal MCP server that exposes a single bash tool to execute commands inside a devcontainer, returning real output and exit codes.1MIT