Searchfox 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 |
|---|---|
| search_codeA | Search for code in Mozilla repositories using Searchfox. IMPORTANT: Uses exact string matching only - no search operators, no OR logic, no phrase matching with quotes. Multiple words are treated as a single literal string. |
| get_fileC | Get the contents of a specific file from specified repository. |
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 2 tools
The two tools have completely distinct purposes: get_file retrieves specific file contents, while search_code performs code searches across repositories. There is no overlap or ambiguity between these operations, making tool selection straightforward for an agent.
Both tools follow a consistent verb_noun naming pattern (get_file, search_code) with clear, descriptive names that align with their functions. The naming convention is uniform and predictable throughout the set.
With only two tools, the server feels severely under-scoped for a code search and exploration domain. While the tools are clear, the lack of additional operations (e.g., list repositories, browse directories, or more advanced search options) limits functionality and makes the toolset feel incomplete for typical use cases.
The toolset is notably incomplete for a code search server. It provides basic file retrieval and simple string search but lacks essential operations like repository listing, directory navigation, or more sophisticated search capabilities (e.g., with operators). This creates significant gaps that could hinder agent workflows in exploring or analyzing codebases.