pickfit

BrowseMCP servers

Context7

Fetches up-to-date, version-specific library documentation and code examples into AI coding agents via an MCP server or CLI.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: node>=22.13
  • Needs the network
  • Keys or accounts: Context7 API key (recommended for higher rate limits)
  1. npm install -g ctx7 @upstash/context7-mcp

    npm install -g ctx7 @upstash/context7-mcp

Check that it works

ls ~/.local/bin && ctx7 --version

The output should contain “0.11.1”.

Add it to your agent

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

Add the Context7 MCP server to your AI coding agent's MCP settings, and the agent can then use the resolve-library-id and query-docs tools.

What it does

  • Give your agent docs for a specific library version
    Not tested
  • Find a library's ID by searching its name
    Not tested
  • Install an agent skill with the ctx7 CLI
    Not tested

How far pickfit got

Linux x86_64

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

Good for

  • give a coding agent current docs for a specific library version
  • look up a library's Context7 ID from its name

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 connects and lists its tools

  • Replayed from scratch
  • Works offline
  • Checked on 15 Nov 2026

An MCP client handshake over stdio listed 2 tools.

Differences the test machine hit

  • README: npx ctx7 setup (authenticates via OAuth, generates an API key)
    In the test: Setup needs a browser OAuth login; for a local MCP server install the separate package @upstash/context7-mcp (npm install -g) and launch context7-mcp
  • README: Packages: ctx7 - CLI
    In the test: The ctx7 package does not include the MCP server binary; @upstash/context7-mcp must be installed separately to run the server locally

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.