local-mcp-with-docker
Related Servers
Alternatives to local-mcp-with-docker
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA minimal, zero-dependency MCP server that enables defining and running tools over stdio transport, without extra features like HTTP or resources.36 npm1MIT
- AlicenseAqualityFmaintenanceA minimal MCP server that exposes a single bash tool to execute commands inside a devcontainer, returning real output and exit codes.1MIT
- FlicenseAqualityDmaintenanceA simple MCP server that exposes a terminal tool, allowing AI agents to execute shell commands.1-
- FlicenseNot gradedqualityDmaintenanceA basic MCP server implementation for testing purposes. Communicates via stdio and is designed to work with MCP-compliant clients.-
- AlicenseAqualityDmaintenanceA minimal MCP server that provides a single 'hello' tool returning 'Hello, world!'.26 npmMIT
- FlicenseNot gradedqualityBmaintenanceMinimal MCP server for testing GitHub PR checks pipeline, with deterministic tools echo, add, and server_info.-
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.