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.
P
Pare Bazel
Community
Structured Bazel build system operations as typed JSON for AI agents.
GitHub source repository ↗
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.
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.
Tools
The tool list has not been reviewed yet.
Setup
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"
]
}
}
}
Fit and risk
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.
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.
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 DesktopFull support