Skip to main content
Glama
ParitoshMaurya

mcp-repo-search

by ParitoshMaurya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-repo-search

No user-submitted related servers found.

    Related Servers

    • Cross Repo Ops MCP

      DHCross
      F
      license
      B
      quality
      C
      maintenance
      Enables secure, policy-controlled operations on local git repositories through MCP, including bounded reads, context-checked patches, allowlisted tasks, and guarded git operations.
      10
      -

    • Gitingest-MCP

      puravparab
      A
      license
      B
      quality
      D
      maintenance
      An MCP server for gitingest. It allows MCP clients like Claude Desktop, Cursor, Cline etc to quickly extract information about Github repositories including repository summaries, project directory structure, file contents, etc
      3
      136
      MIT

    • Wendy - Codebase Q&A Agent

      Julia-b-work
      A
      license
      B
      quality
      A
      maintenance
      Codebase Q&A agent with git-history awareness. Explore a repo with list_files, read_file, and search, plus git log, blame, and diff and a repo map to answer "why did this change?" questions. Runs locally as an MCP server for Claude Code and other MCP clients.
      11
      MIT

    • repo-context

      zyf0717
      A
      license
      D
      quality
      D
      maintenance
      Read-only repository context explorer for coding agents. Provides repository exploration tools via CLI or MCP adapter.
      1
      GPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: cloning, checking status, reading a file, listing a directory, and searching. ensure_repo and get_repo_status are related but one performs an action while the other reports state, so no ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (ensure_repo, get_repo_status, read_file, list_directory, search_repo), using snake_case throughout. This makes the set predictable and easy to navigate.

    Tool Count5/5

    Five tools is well-scoped for a repo search server: one setup action, one status query, and three core read/search operations. Each tool earns its place, and the count is within the ideal 3-15 range.

    Completeness5/5

    The tool surface provides complete lifecycle coverage for the stated purpose of searching within a cloned repo. It supports cloning (with reuse), checking cached state, reading individual files, listing directories, and searching by text/regex—no obvious gaps for this read-only domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources