pickfit

BrowseMCP servers

AI Agents API Library

Curated machine-readable catalog of APIs and MCP servers for AI agents to call.

Tested on Linux

Use it

Linux x86_64

  1. Install MCP package globally via npm

    npm install -g ai-agents-api-library

Add it to your agent

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

Add ai-agents-api-library as an MCP server command in your MCP client, then call its tools such as list_categories or search_apis.

What it does

  • Browse a catalog of 300+ APIs and MCP servers
    How to use it
    1. From your MCP client, call the list_categories tool with no arguments.
    2. Read the returned list of categories to see what the catalog covers.
    Tested
  • Search APIs with MCP tools
    How to use it
    1. From your MCP client, call the search_apis tool with {"query":"<your text>"}.
    2. Review the matching APIs and MCP servers in the result.
    Tested
  • Get the catalog as JSON and llms.txt
    Not shown working

How far pickfit got

Linux x86_64

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

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 31 Oct 2026
  • Version 0.3.11

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