Skip to main content
Glama
YohannHommet

Repo Lens MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_LOG_LEVELNoLog level: debug, info, warn, errorinfo

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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:

  • response_format (string, optional): Output format - "markdown" (default) or "json"

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:

  • name (string, optional): Function name pattern. Supports wildcards: "handle*", "*Controller", "user"

  • paths (string, optional): Ad-hoc directory paths to search (comma-separated). No registration needed.

  • repoFilter (string, optional): Filter registered repositories by alias (comma-separated)

  • language (string, optional): Filter by language: "typescript", "javascript", "php"

  • exportedOnly (boolean, optional): Only return exported functions (default: false)

  • maxResults (number, optional): Maximum results to return (default: 100)

  • response_format (string, optional): Output format - "markdown" (default) or "json"

Examples:

  • Search a directory directly: paths="/home/user/projects/api"

  • Find all handlers: name="handle*"

  • Find exported functions in backend: repoFilter="backend", exportedOnly=true

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:

  • name (string, optional): Class name pattern. Supports wildcards: "*Service", "Controller", "Base"

  • paths (string, optional): Ad-hoc directory paths to search (comma-separated). No registration needed.

  • repoFilter (string, optional): Filter registered repositories by alias (comma-separated)

  • language (string, optional): Filter by language: "typescript", "javascript", "php"

  • exportedOnly (boolean, optional): Only return exported classes (default: false)

  • maxResults (number, optional): Maximum results to return (default: 100)

  • response_format (string, optional): Output format - "markdown" (default) or "json"

Examples:

  • Search a directory directly: paths="/home/user/projects/api"

  • Find all services: name="*Service"

  • Find controllers in backend: repoFilter="backend", name="*Controller"

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:

  • name (string, optional): Type/interface name pattern. Supports wildcards: "*Props", "Config", "I"

  • paths (string, optional): Ad-hoc directory paths to search (comma-separated). No registration needed.

  • repoFilter (string, optional): Filter registered repositories by alias (comma-separated)

  • language (string, optional): Filter by language: "typescript", "javascript", "php"

  • exportedOnly (boolean, optional): Only return exported types (default: false)

  • maxResults (number, optional): Maximum results to return (default: 100)

  • response_format (string, optional): Output format - "markdown" (default) or "json"

Examples:

  • Search a directory directly: paths="/home/user/projects/api"

  • Find all props types: name="*Props"

  • Find interfaces with prefix: name="I*", exportedOnly=true

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:

  • method (string, optional): Filter by HTTP method: "GET", "POST", "PUT", "DELETE", "PATCH"

  • pathPattern (string, optional): Filter routes containing this path segment (e.g., "/users", "/api/v1")

  • paths (string, optional): Ad-hoc directory paths to search (comma-separated). No registration needed.

  • repoFilter (string, optional): Filter registered repositories by alias (comma-separated)

  • framework (string, optional): Filter by framework: "express", "fastify", "nestjs", "laravel"

  • maxResults (number, optional): Maximum results to return (default: 100)

  • response_format (string, optional): Output format - "markdown" (default) or "json"

Examples:

  • Search a directory directly: paths="/home/user/projects/api"

  • Find all user endpoints: pathPattern="/users"

  • Find POST routes in backend: repoFilter="backend-api", method="POST"

  • Find NestJS controllers: framework="nestjs"

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 5 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues