home / mcp / mcp build service mcp server
Provides AI-assisted access to git repos for builds, tests, and code inspection via MCP tools and HTTP streaming endpoints.
Configuration
View docs{
"mcpServers": {
"jbroll-mcp-build": {
"url": "http://your-server:3344/sse?key=SESSION_KEY"
}
}
}The MCP Build Service lets an AI assistant access your git repositories to run builds, tests, and inspections in a dedicated environment. It provides practical commands for listing repos, querying git history, reading files, and executing Makefile targets, so you can verify changes and validate builds safely from an AI-enabled workflow.
You connect an MCP client to the Build Service to perform common software development tasks inside a build environment. Start by placing all your git repositories in a single directory, then run the service in that directory. The AI can list repos, inspect branches, read files, and trigger builds and tests through Makefiles. Use the HTTP transport for remote access or the local stdio mode for a direct, in-process workflow.
Prerequisites: Python and pip must be available on your system. You will also need a directory that contains your git repositories.
# Install this MCP server in editable mode
git clone <this-repo-url>
cd mcp-build
pip install -e .
# Prepare your build area with git repositories
/path/to/build-area/Choose between local (stdio) mode for a direct in-process setup or remote (HTTP) mode for networked access. In local mode, run the service from the directory that contains your git repositories.
Local mode example—start the service in the directory with your repos and connect your MCP client to it. This runs the server in stdio mode and keeps the build environment isolated from your main IDE. Use an MCP client to issue commands like listing repos, reading files, or running Makefile targets.
Remote mode example—start the service with HTTP transport to allow remote clients to connect. The service will generate a session key on startup, which you pass to the MCP client for authenticated access.
Git operations are limited to a predefined whitelist (status, log, checkout, pull, branch, diff, fetch, show). Dangerous actions such as push or hard resets are blocked. Command validation guards against path traversal and common injection patterns.
Make targets run exactly as defined in the repository’s Makefile, with no sandboxing applied by default. Treat this environment as suitable for builds but not as a fully hardened sandbox.
If no repositories are found, ensure you started the service in the parent directory of your git repos and that every directory contains a .git folder.
If a repository cannot be found, verify the available names with the list operation and ensure you reference the correct repository directory.
In addition to the MCP protocol, the service exposes HTTP endpoints for quick and streaming operations. Authentication via a session key is required for all endpoints.
List available repositories in the configured build area.
Execute allowed git commands such as status, log, checkout, pull, branch, diff, fetch, show.
Run make targets as defined in each repository's Makefile to build, test, or clean.
List files and directories within a repository or path.
Show installed tools and their versions available in the build environment.
Read contents of a file with optional line range for large files.