mcp-dev

This MCP server (mcp-dev) provides a centralized interface to manage software development project context, perform file system operations, initialize templates, and interact with Git repositories. It also enables code execution within Docker environments, allowing you to run builds and tests in isolated containers. The server exposes capabilities for project analysis, development suggestions, and error diagnosis through prompts, as well as a suite of tools for project initialization, building, testing, and Docker-related commands. You can query or script common tasks (structure inspection, template creation, and repository operations) and receive structured responses that reflect the current project context and artifact status.

To use the server, start it via the Python module entry point and communicate with its MCP capabilities. The tools available include:

• Project initialization: scaffold new projects or templates based on templates or boilerplates.
• Build operations: compile or assemble project artifacts inside containerized environments.
• Test execution: run unit/integration tests and collect results.
• Docker commands: manage and execute code within Docker containers for reproducible environments.
• Prompts: analyze project structure, receive development suggestions, and diagnose errors with context-aware guidance.

Access to these features is typically mediated through the MCP protocol (MCP requests/responses) and any client UI or CLI you use to interact with the server. Ensure Docker is running and that your environment has network access to dependencies required by your workflow.

Prerequisites:

• Python 3.12 or higher
• Docker
• Git

Install the MCP server from PyPI:

pip install mcp-dev-server

(Development installation)

git clone https://github.com/your-org/mcp-dev-server.git
cd mcp-dev-server
pip install -e .

If you prefer running the server directly as a module, ensure it is installed in your Python environment and start using:

python -m mcp_dev_server

Notes & tips:

• The server is intended to run in environments with Docker available and Git installed.
• If you run into port or binding issues, check your environment's network settings and any CLI configuration you use to connect to the MCP server.
• You can configure the MCP server in your Claude Desktop configuration by referencing the server name (e.g., dev) and the CLI command used to start it. The example in the README shows the expected JSON structure for Claude Desktop integration.
• Environment variables may be required for Docker access or authentication in certain workflows; add them to your startup environment or the mcp config as needed.
• If you upgrade the server, verify compatibility with your MCP clients and update any CLI tooling accordingly.