Bazel MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bazel_build_targetC | Build specified Bazel targets |
| bazel_query_targetA | Query the Bazel dependency graph for targets matching a pattern |
| bazel_test_targetC | Run Bazel tests for specified targets |
| bazel_list_targetsB | List all available Bazel targets under a given path |
| bazel_fetch_dependenciesB | Fetch Bazel external dependencies |
| bazel_set_workspace_pathB | Set the current Bazel workspace path for subsequent commands |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no ambiguity: building, fetching dependencies, listing targets, querying the dependency graph, setting workspace path, and testing. The descriptions clearly differentiate their functions, making misselection unlikely.
All tools follow a consistent 'bazel_verb_noun' pattern (e.g., bazel_build_target, bazel_fetch_dependencies), using snake_case throughout. This predictable naming makes the tool set easy to navigate and understand.
With 6 tools, this server is well-scoped for Bazel operations, covering core workflows like building, testing, querying, and workspace management. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool set provides strong coverage for essential Bazel tasks, including build, test, query, and dependency management. A minor gap exists in operations like cleaning or caching, but agents can work around this with the available tools for most common workflows.