💻

Bazel Build MCP

Updated June 2026

The Bazel Build MCP, built by community, provides scalable build system integration via Bazel — query build targets and dependency graphs, run incremental builds and tests with caching, retrieve build event protocol data, analyze build performance and bottlenecks, manage remote execution and caching configuration, query workspace rules and macro definitions, and integrate with CI/CD systems for hermetic, reproducible builds. It is community-built and best for Coding & Dev.

by community

About

Scalable build system integration via Bazel — query build targets and dependency graphs, run incremental builds and tests with caching, retrieve build event protocol data, analyze build performance and bottlenecks, manage remote execution and caching configuration, query workspace rules and macro definitions, and integrate with CI/CD systems for hermetic, reproducible builds.

Unverifiable
not scored

No repository for this entry resolves against the live GitHub API, so there is nothing to verify. It is deliberately left unscored rather than given a number we cannot stand behind.

What could not be measured

These contributed nothing to the score — not a penalty, not a zero. They are why the confidence reads the way it does.

  • Source verificationunknown

    No repository for this entry resolves against the live GitHub API. Without a confirmed source there is nothing to inspect, so this entry is excluded from trust scoring entirely rather than scored on catalog metadata alone.

What we could verify

No public repository, published package, or project website has been confirmed for Bazel Build MCP. The description above reflects what the server is reported to do; we have not been able to verify an implementation behind it, so there is no install command to give you and no star count worth quoting.

If you maintain it, or you know the repository, the fastest way to fix this listing is to point us at the source.

Frequently Asked Questions

What is Bazel Build MCP?
Bazel Build MCP is an MCP server built by community. Scalable build system integration via Bazel — query build targets and dependency graphs, run incremental builds and tests with caching, retrieve build event protocol data, analyze build performance and bottlenecks, manage remote execution and caching configuration, query workspace rules and macro definitions, and integrate with CI/CD systems for hermetic, reproducible builds.
Who built Bazel Build MCP?
Bazel Build MCP was built by community.
Is Bazel Build MCP free?
Yes, Bazel Build MCP has a free option. This MCP server is free and open-source. Check the GitHub repository for details.
How do I install Bazel Build MCP?
Bazel Build MCP has no verified public repository, so there is no confirmed install command for it.
What does Bazel Build MCP integrate with?
Bazel Build MCP integrates with Claude Desktop, Cursor, VS Code.
No verified public repository

Repo Health

Local install

Local/stdio install — runs on your machine, so there is no remote endpoint to verify live. Trust signal below is from the source repo.

Install
pip

Repo recency not yet available for this server.

Quick Info

Install Type
pip
Author
community
Categories
2
Integrations
3

Related Servers

💻

Everything

Reference/test server with prompts, resources, and tools. Perfect for testing MCP implementations.

Local
💻

Git

Tools to read, search, and manipulate Git repositories. Full Git operations support.

Local
🤖

Sequential Thinking MCP Server

a single structured-reasoning tool that lets a model plan, revise and branch its own chain of thought instead of answering in one shot. Published by Anthropic as part of the official modelcontextprotocol/servers monorepo (89,000+ stars, actively maintained), it exposes exactly one tool — sequential_thinking — and that tool is the whole product. Each call carries a `thought` string plus bookkeeping fields: `thoughtNumber`, `totalThoughts`, and `nextThoughtNeeded`, which the model flips to false when it is done. The interesting fields are the optional ones. `isRevision` and `revisesThought` let the model go back and correct an earlier step rather than plowing ahead on a bad assumption; `branchFromThought` and `branchId` let it fork into an alternative line of reasoning and carry both forward; `needsMoreThoughts` lets it extend past its own original estimate when a problem turns out to be deeper than it looked. In practice you never call the tool by hand. You connect the server to an MCP host and ask a question that deserves more than one pass — plan a PostgreSQL 14 to 16 migration and revise if downtime exceeds five minutes, work out why a deploy only fails in production, compare three architectures and branch when an assumption breaks. You can tell it is working when the host inspector shows repeated sequential_thinking calls with a rising `thoughtNumber` rather than a single response. Install with `npx -y @modelcontextprotocol/server-sequential-thinking` — note the hyphenated package name, which differs from both the `sequentialthinking` directory in the repo and the Docker image `mcp/sequentialthinking`, a mismatch that breaks a lot of copied configs. A Docker image is published alongside the npm package, and the README carries one-click VS Code install buttons for both transports. Set `DISABLE_THOUGHT_LOGGING=true` if you do not want every thought written to the server log.

Local
💻

21st.dev Magic

Create crafted UI components inspired by the best 21st.dev design engineers.

Local
💻

GitHub MCP Server

authenticated access to the whole GitHub platform — repositories, files, branches, issues, pull requests, Actions runs, security alerts, discussions and notifications — from Claude, Cursor, VS Code, Copilot CLI and any other MCP host. There is no npm package for this server, and that trips up most people who try to install it: `@github/mcp-server` is not published to the npm registry, so any `npx` line you find for it will fail. GitHub ships it three other ways. The easiest is the hosted remote server at https://api.githubcopilot.com/mcp/, which needs no install at all — point an HTTP-transport MCP client at that URL and log in with OAuth (VS Code 1.101+, Claude Desktop, Claude Code, Cursor and Windsurf all support this). The second is the official Docker image ghcr.io/github/github-mcp-server, which is what the copy-paste command on this page runs; on github.com it now performs a browser-based OAuth login on first use and keeps the token in memory only, which is why the published Docker configs map a fixed loopback callback port (-p 127.0.0.1:8085:8085 with GITHUB_OAUTH_CALLBACK_PORT=8085) so the container can receive the callback. Prefer a token? Set GITHUB_PERSONAL_ACCESS_TOKEN instead — it takes precedence over OAuth, and the minimum useful scopes are repo, read:org and read:packages. The third is the native Go binary from the repository's releases, which needs no fixed port for the OAuth flow. GitHub Enterprise Server has no hosted option: use the local server with --gh-host or GITHUB_HOST set to your instance (include the https:// scheme — it defaults to http://, which GHES rejects). Toolsets can be narrowed with GITHUB_TOOLSETS, and an insiders channel is available at /mcp/insiders or via the X-MCP-Insiders header.

Auth required📘

Sponsored

Better Stack

Free Plan

Get alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.

Start monitoring free →