pickfit

BrowseMCP servers

indexio

Local code search engine that indexes repos once for AI agents via MCP.

Use it

Before you install: known vulnerabilities

pickfit found 6 known high or critical vulnerabilities (8 findings, one per affected package version) in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • crates:gix 0.66.0 gitoxide: CommandForbiddenInModulesConfiguration Bypass in gix_submodule::File::update() Enables Arbitrary Command Execution via .gitmodules (GHSA-f26g-jm89-4g65, high, fixed in 0.83.0)
  • crates:gix-fs 0.11.3 gix-fs: Symlink prefix-reuse allows worktree escape during checkout (GHSA-f89h-2fjh-2r9q, high, fixed in 0.21.1)
See 6 more

Linux x86_64

You need first

  • System packages: git
  1. install via uv tool install indexio-cli

    uv tool install indexio-cli

Check that it works

indexio --version 2>&1

The output should contain “indexio 0.1.10”.

First thing to try

mkdir -p /tmp/sample_repo && cd /tmp/sample_repo && git init -q && git config user.email "test@test.com" && git config user.name "test" && cat > main.py <<'PY'
# Sample repo for indexio testing
def hello(name):
    """Greet someone"""
    return f"Hello {name}"

def add(a, b):
    return a + b

# TODO: refactor this function
def old_function():
    pass

HELLO_CONSTANT = 42
PY
cat > utils.py <<'PY'
def helper():
    return hello("world")

def caller_of_add():
    return add(1,2)
PY
# need import for helper to reference hello - add import
printf 'from main import hello, add\n' | cat - utils.py > utils.py.tmp && mv utils.py.tmp utils.py
git add . && git commit -qm "initial" && ls -la
indexio add /tmp/sample_repo 2>&1 && indexio stats 2>&1
indexio search "TODO" --limit 3 2>&1

Add it to your agent

claude mcp add indexio -- indexio mcp
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "indexio": {
      "command": "indexio",
      "args": [
        "mcp"
      ]
    }
  }
}

Run indexio add <repo> to index a repository, then indexio mcp to serve it to your MCP client.

What it does

  • Search code by text, meaning, or both
    How to use it
    1. Index your repository with indexio add <repo> and check it with indexio stats.
    2. Start the MCP server with indexio mcp and connect your MCP client.
    3. Call the code_search tool with a query such as <your text> and an optional limit.
    Tested
  • Find where a symbol is defined and who calls it
    How to use it
    1. Index your repository with indexio add <repo>.
    2. Start the MCP server with indexio mcp and connect your MCP client.
    3. Call find_symbol with the symbol name to find its definition, or who_calls with the name to list its callers.
    Tested
  • See the impact of changing a symbol or diff
    Not shown working
  • Serve the code index over MCP and an HTTP API
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 2 of 4 features work
  4. Works offline

macOS and Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • find where a symbol is defined
  • answer semantic questions about code
  • find who calls a symbol and impact of change

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client called one of its tools

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version 0.1.10

An MCP client handshake over stdio listed 13 tools, and a call to code_search returned a result.

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.