pickfit

BrowseMCP servers

CodePrism

Builds a persistent code knowledge graph and exposes precise context to AI agents via MCP.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Python 3.12+
  1. install codeprism-ai with uv tool

    uv tool install codeprism-ai

Check that it works

codeprism --help 2>&1

The output should contain “CodePrism”.

Add it to your agent

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

Run codeprism serve . from your project folder, or add that command as an MCP server in your AI client.

What it does

  • Build a lasting knowledge graph of your code
    How to use it
    1. Start the server in your project folder with codeprism serve ..
    2. From your MCP client, call the index_project tool with the path set to your project folder.
    Tested
  • Find callers, callees and impact of code
    How to use it
    1. Start the server in your project folder with codeprism serve ..
    2. Call the get_callees tool with the file and the function name, for example <file> and <function>.
    Tested
  • Scan code changes for security issues
    How to use it
    1. Start the server in your project folder with codeprism serve ..
    2. Call the scan_diff tool with the original text, the proposed text and the file name.
    Tested
  • Give AI agents code context over MCP
    How to use it
    1. Start the server in your project folder with codeprism serve ..
    2. Call the get_context tool with a file and a symbol name to get its context.
    Tested

How far pickfit got

Linux x86_64

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

Good for

  • get structured context for a function with callers and callees
  • scan proposed file changes for secrets before writing
  • analyze impact and blast radius before refactoring
  • track agent session reads and writes to avoid re-fetching

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 30 Oct 2026
  • Version 0.1.11

An MCP client handshake over stdio listed 21 tools, and a call to index_project 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.