Chromium CodeSearch MCP
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 |
|---|---|
| search_chromium_codeC | Search for code in the Chromium source repository using Google's official Code Search syntax |
| find_chromium_symbolC | Find symbol definition, references, and usage in Chromium source |
| get_chromium_fileC | Get contents of a specific file from Chromium source |
| get_gerrit_cl_statusC | Get status and test results for a Chromium Gerrit CL |
| get_gerrit_cl_commentsC | Get review comments for a Chromium Gerrit CL patchset |
| get_gerrit_cl_diffB | Get the diff/changes for a Chromium Gerrit CL patchset to understand what code was modified |
| get_gerrit_patchset_fileB | Get the content of a specific file from a Gerrit patchset for making code changes |
| get_gerrit_cl_trybot_statusA | Get detailed try-bot status for a Chromium Gerrit CL, including individual bot results and pass/fail counts |
| get_gerrit_cl_bot_errorsA | Get detailed error messages with stack traces from failed try-bots for a Chromium Gerrit CL. This includes the actual test failures, assertion errors, and full stack traces to diagnose why tests failed. |
| get_ci_build_errorsA | Get detailed error messages with stack traces from a specific CI build URL. This provides the actual test failures, assertion errors, and complete stack traces from a CI build. |
| get_pdfium_gerrit_cl_statusC | Get status and test results for a PDFium Gerrit CL |
| get_pdfium_gerrit_cl_commentsB | Get review comments for a PDFium Gerrit CL patchset |
| get_pdfium_gerrit_cl_diffB | Get the diff/changes for a PDFium Gerrit CL patchset to understand what code was modified |
| get_pdfium_gerrit_patchset_fileC | Get the content of a specific file from a PDFium Gerrit patchset for making code changes |
| get_pdfium_gerrit_cl_trybot_statusA | Get detailed try-bot status for a PDFium Gerrit CL, including individual bot results and pass/fail counts |
| list_pdfium_gerrit_clsA | List PDFium Gerrit CLs from PDFium dashboard (requires authentication cookie) |
| find_chromium_owners_fileC | Find OWNERS files for a given file path in Chromium source code by searching up the directory tree |
| search_chromium_commitsC | Search commit messages and metadata in the Chromium repository using Gitiles API |
| get_chromium_issueC | Get details for a specific Chromium issue/bug from issues.chromium.org |
| search_chromium_issuesB | Search for issues in the Chromium issue tracker with full-text search across titles, descriptions, and metadata |
| list_chromium_folderB | List files and folders in a specific directory of the Chromium source tree |
| list_gerrit_clsB | List Gerrit CLs from Chromium dashboard (requires authentication cookie) |
| suggest_reviewers_for_clA | Find optimal reviewers for a Chromium CL. Analyzes OWNERS files and recent commit activity to suggest the minimal set of reviewers who can cover all changed files. Ranks reviewers by both OWNERS coverage and recent commit activity. |
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 23 tools
Most tools have distinct purposes targeting different resources (e.g., Chromium vs. PDFium, file operations vs. issue tracking vs. CI builds). However, there is some overlap between Chromium and PDFium Gerrit tools (e.g., get_gerrit_cl_comments vs. get_pdfium_gerrit_cl_comments) that could cause confusion if the domain isn't clearly specified in queries. The descriptions help differentiate, but the parallel structures create minor ambiguity.
Tool names follow a highly consistent verb_noun pattern with clear prefixes (e.g., get_, list_, search_, find_). All tools use snake_case uniformly, and the naming conventions are predictable across the set, making it easy to understand each tool's function at a glance.
With 23 tools, the count feels heavy for a code search server, though it covers multiple domains (Chromium source, Gerrit, PDFium, CI). It's borderline because the scope is broad but not excessive; however, the duplication between Chromium and PDFium tools inflates the count without adding unique functionality, making it slightly over-scoped.
The tool set provides comprehensive coverage for Chromium development workflows, including code search, file access, issue tracking, Gerrit CL management (status, diffs, comments), CI error analysis, and reviewer suggestions. There are no obvious gaps; it supports full lifecycle operations from code exploration to patch review and debugging.