Skip to main content
Glama
egn88

Build Runner MCP Server

by egn88
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Build Runner MCP Server

A Model Context Protocol (MCP) server that provides structured build, compile, and test operations with parsed output to reduce token usage and improve readability.

Features

  • Java version switching via SDKMAN (sdk use java <version>)

  • Compilation with structured error output

  • Build/Package with success/failure summary

  • Test execution with parsed test results (passed, failed, skipped)

  • Multi-build-system support: Maven, Gradle, npm/pnpm/yarn

Related MCP server: MCP Build Environment Service

Installation

# Clone the repository
git clone <repository-url>
cd build-runner-mcp

# Install dependencies
npm install

# Build the project
npm run build

Configuration

Add to your Claude Code settings (~/.claude.json):

{
  "mcpServers": {
    "build-runner": {
      "command": "node",
      "args": ["/path/to/build-runner-mcp/build/index.js"]
    }
  }
}

Available Tools

detect_project

Detect project type, build system, test framework, and configuration.

{
  "projectPath": "/path/to/project"
}

Returns: Project info including languages, build system, package manager, and test framework.

set_java_version

Switch Java version using SDKMAN before running commands.

Available versions: 17.0.16-amzn, 21.0.8-tem, 21.0.9-amzn, 25.0.1-tem

{
  "version": "17.0.16-amzn"
}

compile_project

Compile a Java project using Maven or Gradle.

{
  "projectPath": "/path/to/project",
  "javaVersion": "17.0.16-amzn",
  "clean": false,
  "module": "core"
}

Returns: Structured compile errors and warnings with file, line, column, and message.

build_project

Build/package a Java project.

{
  "projectPath": "/path/to/project",
  "javaVersion": "21.0.8-tem",
  "skipTests": true,
  "clean": true
}

Returns: Build artifacts with paths and sizes, duration, and any errors.

run_tests

Run tests for a Java project with structured results.

{
  "projectPath": "/path/to/project",
  "javaVersion": "17.0.16-amzn",
  "testPattern": "UserServiceTest",
  "module": "api",
  "failFast": true
}

Returns:

{
  "success": false,
  "summary": { "total": 50, "passed": 47, "failed": 2, "skipped": 1, "duration": "12.5s" },
  "failures": [
    {
      "testClass": "UserServiceTest",
      "testMethod": "testLogin",
      "message": "Expected 200 but got 401",
      "stackTrace": "...",
      "file": "UserServiceTest.java",
      "line": 42
    }
  ]
}

node_build

Build a Node.js/TypeScript project.

{
  "projectPath": "/path/to/project",
  "script": "build",
  "packageManager": "pnpm"
}

node_typecheck

Type check a TypeScript project using tsc --noEmit.

{
  "projectPath": "/path/to/project"
}

node_test

Run tests for a Node.js/TypeScript project (Jest, Vitest, or Mocha).

{
  "projectPath": "/path/to/project",
  "testPattern": "user.test.ts",
  "failFast": true,
  "coverage": true
}

Token Savings

Before (raw Maven test output): ~500 lines

[INFO] Scanning for projects...
[INFO] --- maven-surefire-plugin:3.0.0:test ---
... (hundreds of lines)
[ERROR] Tests run: 50, Failures: 2, Errors: 0, Skipped: 1

After (structured): ~20 lines

{
  "success": false,
  "summary": { "total": 50, "passed": 47, "failed": 2, "skipped": 1 },
  "failures": [
    { "testClass": "UserServiceTest", "testMethod": "testLogin", "message": "Expected 200 but got 401" }
  ]
}

SDKMAN Integration

The server automatically sources SDKMAN and switches Java versions when specified:

source "$HOME/.sdkman/bin/sdkman-init.sh" && sdk use java 17.0.16-amzn && mvn compile

Development

# Run in development mode
npm run dev

# Build
npm run build

# Clean build artifacts
npm run clean

License

MIT

This server cannot be installed

F
license - not found
-
quality - not tested
D
maintenance

How are these scores calculated?

Maintenance

–Maintainers
–Response time
–Release cycle
–Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/egn88/build-runner-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server