MCP Repo Search Server MCP Server

MCP server for multi-repository AST-based symbol search and API route discovery

Local serverstdioTypeScript

What is the MCP Repo Search Server MCP server?

MCP Repo Search Server MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for multi-repository AST-based symbol search and API route discovery.

What you get

Unlike grep-style text search, Repo Lens uses ast-grep (written in Rust) to parse code into Abstract Syntax Trees:

Setting it up

The server ships on npm as repo-lens-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once MCP Repo Search Server is connected, these are the calls the assistant has available:

  • paths — Ad-hoc directory paths to search (comma-separated, no registration needed)
  • repoFilter — Filter registered repositories by alias
  • repolens_find_functions — Find function/method definitions in JS/TS and PHP (supports wildcards like handle*)
  • repolens_find_classes — Find class definitions (also finds PHP traits)
  • repolens_find_types — Find interfaces and type aliases (PHP: interfaces only)
  • repolens_find_api_routes — Map API endpoints across Express, NestJS, Fastify, Laravel

Configuration and credentials

You will need one environment variable: MCP_LOG_LEVEL. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp repo search server mcp server does with a few real requests.

Choosing this one

Plenty of file and storage access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Repo Search Server's toolset — paths, repoFilter, repolens_find_functions and 3 more — is a fair guide to whether it matches your workflow. It is maintained by yohannhommet; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
pathsAd-hoc directory paths to search (comma-separated, no registration needed)
repoFilterFilter registered repositories by alias
repolens_find_functionsFind function/method definitions in JS/TS and PHP (supports wildcards like handle*)
repolens_find_classesFind class definitions (also finds PHP traits)
repolens_find_typesFind interfaces and type aliases (PHP: interfaces only)
repolens_find_api_routesMap API endpoints across Express, NestJS, Fastify, Laravel

How to install the MCP Repo Search Server MCP server

{
  "mcpServers": {
    "repo-lens": {
      "command": "npx",
      "args": ["-y", "repo-lens-mcp", "--config", "/home/user/repolens.yaml"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
MCP_LOG_LEVELConfiguration value read at startup.Optional

Example prompts to try

  • Use MCP Repo Search Server to paths.
  • Use MCP Repo Search Server to repoFilter.
  • Use MCP Repo Search Server to repolens find functions.

Frequently asked questions

It connects MCP Repo Search Server to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (paths, repoFilter, repolens_find_functions, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Repo Search Server directly.