Skip to main content
Glama
Build Unblocker MCP

Build Unblocker MCP

Build Unblocker MCP

A Model-Context-Protocol (MCP) server for Cursor IDE to terminate hung Windows build executables.

Features

  • Monitors specified build processes (cl.exe, link.exe, msbuild.exe, etc.)

  • Terminates processes that are idle (less than 1% CPU usage) for a configurable duration (default 90 seconds)

  • Provides a tool (unblock_build) for Cursor IDE to trigger the unblocking process

Related MCP server: stdout-mcp-server

Installation

  1. Ensure you have Python 3.11 or later installed.

  2. Install using pipx (recommended for CLI tools):

    pipx install .

    Or using pip:

    pip install .

Cursor Integration

Add the following to your Cursor IDE settings (settings.json):

{
  "mcpServers": {
    "build-unblocker": {
      "command": "unblock-build-mcp"
    }
  }
}

Local Smoke Test

You can run the tool manually to test it (use --dry-run to avoid killing processes):

pipx run unblock-build-mcp --idle-seconds 5 --dry-run

Continuous Integration

CI Status (Replace your-github-username with your actual GitHub username and build-unblocker-mcp with the repository name)

License

This project is licensed under the MIT License. See the LICENSE file for details.

Available Tools

1 tool
unblock_buildC

Kill build executables idle > idle_seconds.

Inputs: dry_run, idle_seconds, process_names.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose is clearly defined to kill idle build executables, making it distinct by default.

    Naming Consistency5/5

    Since there is only one tool, it inherently follows a consistent naming pattern with no deviations to evaluate. The tool name 'unblock_build' uses a verb_noun format, which is clear and predictable in isolation.

    Tool Count2/5

    A single tool is too few for a server named 'Build Unblocker MCP', which suggests a broader scope related to managing or troubleshooting builds. This minimal set likely leaves significant gaps in functionality, such as monitoring build status or handling other build-related issues.

    Completeness2/5

    The tool surface is severely incomplete for the implied domain of build management. While 'unblock_build' addresses killing idle executables, there are obvious gaps like checking build health, restarting builds, or logging build errors, which are essential for comprehensive build unblocking workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers