Pare Bazel

Community

Structured Bazel build system operations as typed JSON for AI agents.

How to install ↓ Compare GitHub source repository ↗

Category: Dev Tools #308 of 438
Stars: ★ 138 Popular
Transport: stdio (local process)
Runtime: Node.js 20+
Credentials: No credential needed
License: MIT
Last commit: 54 days ago

45FMRS · D

Pare Bazel is a focused MCP server for Bazel that provides structured output, significantly reducing token usage and improving reliability for AI agents. It is a third-party open-source project, not official, but MIT-licensed and publicly available. Suitable for developers using Bazel, but be aware of resource consumption and potential information disclosure risks.

Strongest · Setup experience 12/20 Weakest · Reliability 4/20

Reliability

4/20

Security and permissions

6/20

Maintenance

11/20

Documentation

12/20

Setup experience

12/20

Why each score

Reliability 4/20: Only the manifest and README were supplied; no source, tests, or tool list for the bazel server. The manifest is well-formed, but startup, init handshake, and tool-to-behavior matching cannot be verified. The git/npm examples in the README belong to sibling servers and were not counted. Badges are untrusted evidence, so reliability is 4.
Security and permissions 6/20: No red-line issues such as malware or credential theft are visible. However, the bazel server executes local build commands, and the README does not disclose data boundaries, side effects, or confirmation for dangerous operations, nor least-privilege guidance. Missing disclosure caps the score at 6.
Maintenance 11/20: The repository is not archived, has an MIT license, version 0.22.0, CI/codecov badges, and 17 open issues, indicating some activity. But no commit history, issue response times, or dependency update evidence was supplied; README claims are untrusted. Hence 11.
Documentation 12/20: The README offers quickstart, client config examples, env-var filtering, and troubleshooting, which is usable. However, bazel-specific tool parameters, output schemas, and examples are not in the supplied evidence—only a link to docs/tool-schemas—so limitations are undisclosed. Score 12.
Setup experience 12/20: Installation is clear: npx package @paretools/bazel, Node >=20, with client config examples and tool filtering. But no bazel-specific config example or execution evidence is present; static review caps setup at 15, so score 12.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessRuns commands or code

Best for

Teams using Bazel as their build system.
AI agents or coding assistants that need structured, reliable build output.
Users who want to reduce token consumption and increase output consistency.

Not for

Projects that do not use Bazel.
Scenarios requiring graphical or interactive Bazel operations (e.g., manual debugging).
Users who need raw, unconventional output for custom analysis.

Required permissions

Requires permission to execute Bazel commands, including read/write access to build caches, source directories, and generated artifacts. May involve network access to download dependencies.

Risks and side effects

Bazel commands can be resource-intensive (CPU, memory, disk), and prolonged or incorrect usage may lead to performance issues.
The server may expose sensitive build information (paths, dependency names) to AI assistants, posing disclosure risks.
As a third-party MCP server, its behavior depends on the maintenance and security of the upstream Pare project.

Setup

Before you start

Runtime：Node.js 20+

Other optional settings (1)

PARE_TOOLS optional Universal tool filter across all Pare servers, format server:tool,... (e.g. git:status,npm:install), restricting which tools register.

Install the MCP server via npm and configure a client (e.g., Claude Desktop) to launch with npx -y @paretools/bazel. Alternatively, use Pare's quick setup: npx @paretools/init --client <client> --preset devops.

claude_desktop_config.json

{
  "mcpServers": {
    "pare-bazel": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/bazel"
      ]
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json

{
  "servers": {
    "pare-bazel": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/bazel"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal

claude mcp add pare-bazel -- npx -y @paretools/bazel

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After starting the pare-bazel server via npx -y @paretools/bazel, its Bazel tools should appear in the client's tool list; you can also run npx @paretools/init doctor to validate the connection.

Troubleshooting

Ensure Node.js version >= 20.
If npx is not found, use an absolute path or `cmd /c npx` on Windows.
Check that Bazel is installed and in PATH.
If connection times out, increase `initTimeout` in client config or set `MCP_TIMEOUT`.
Use the `PARE_BAZEL_TOOLS` environment variable to limit available tools and reduce context usage.

Things to try

Once connected, you can ask your AI assistant things like:

Build the //app:main target with Bazel and return the result as JSON
List the Bazel test targets in this workspace and run them
Query the dependency graph of //... and give me a structured summary
Parse the error message from the last failed Bazel build into typed fields

Use cases

Query Bazel build status, run builds, or analyze build output in AI coding tools.

Automated build monitoring and error reporting.

Integrate Bazel operations into agent workflows without text parsing.

Supported clients

Claude Desktop

Listed from the project's documentation, not tested by this site.

Overview

Pare Bazel is an MCP server for the Bazel build system, part of the Pare collection. It converts Bazel CLI output into schema-validated, type-safe JSON for direct use by AI agents, eliminating fragile text parsing. The server is open-source (repo Dave-London/Pare) under MIT license, distributed via npm package @paretools/bazel, and communicates over stdio. It aims to reduce token usage (by approximately 46-95%) and provide consistent field names regardless of platform, version, or locale differences.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →

NPM Sentinel MCP Server 79 · B

AI-powered NPM package analysis MCP server

★ 18 · Tools 19 Compare with this →

MartinLoop MCP Server 79 · B

An independent control layer that gives AI coding agents budgets, brakes, and receipts

★ 410 Compare with this →

GitHub MCP Server 76 · B

GitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language

★ 33.5k · Tools 15 Compare with this →

Compare with other MCP servers

More servers from this repository

Source revision 57e1980e8375 Data synced 2026-10-12 Read the FMRS scoring method