Repo Lens MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_LOG_LEVEL | No | Log level: debug, info, warn, error | info |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| repolens_list_repositoriesA | List all configured repositories available for cross-repository search. Returns the list of repositories declared in repolens.yaml with their aliases, paths, and git branch info. Args:
|
| repolens_find_functionsA | Find function and method definitions across repositories using AST analysis. Searches for function declarations, arrow functions, and class methods in JS/TS and PHP. Uses ast-grep for accurate structural matching. Args:
Examples:
|
| repolens_find_classesA | Find class definitions across repositories using AST analysis. Searches for class declarations. Also finds PHP traits. Uses ast-grep for accurate structural matching. Args:
Examples:
|
| repolens_find_typesA | Find type aliases and interface definitions across repositories using AST analysis. Searches for both "type" and "interface" declarations. For PHP, finds interface declarations (PHP has no type aliases). Uses ast-grep for accurate structural matching. Args:
Examples:
|
| repolens_find_api_routesA | Find API route/endpoint definitions in backend code across repositories. Searches for HTTP route definitions in Express, Fastify, NestJS, and Laravel codebases. Supported Frameworks: Express, Fastify, NestJS, Laravel (PHP) Args:
Examples:
|
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 5 tools
Each tool targets a distinct code construct: repositories, functions, classes, types/interfaces, and API routes. The descriptions clearly separate concerns, so an agent is unlikely to confuse one tool for another.
All tool names follow the consistent `repolens_<verb>_<noun>` pattern using snake_case. The verb choices are uniform (`list` for one, `find` for the rest) and the object nouns clearly indicate the target.
Five tools is well-scoped for a focused cross-repository code search server. Each tool covers a meaningful piece of the search surface without redundant or unnecessary entries.
The set covers the primary search needs for functions, classes, types, and API routes across repositories. Notable gaps remain such as full-text search, enums, variables, or imports, but these are workable minor omissions rather than critical dead ends.