clirank — Claude Code MCP server: pick APIs, read docs
Searches, compares and serves docs for 420+ APIs so your agent stops guessing which SDK to use. Points at https://clirank.dev/api, no key needed.
claude mcp add --env CLIRANK_API_URL=<CLIRANK_API_URL> --transport stdio clirank -- npx -y clirank-mcp-serverWhat clirank does
CLIRank is an MCP server that lets a coding agent look up APIs and pull their documentation. It talks to https://clirank.dev/api and needs no CLIRank API key. Call it before the agent installs an SDK or writes integration code — otherwise the choice rests on stale model memory or eats tokens in broad web searches.
Eight tools ship with it. discover_apis searches by intent and filters on price model and minimum CLI score; recommend returns one pick for a concrete job along with pricing and setup signals; get_api_docs hands back a quickstart, auth setup and SDK install steps. compare_apis lines up two to five APIs, browse_categories lists categories with counts, get_reviews reads past integration reports and submit_review files a new one after a real attempt rather than a guess.
The server runs as a stdio process through npx -y clirank-mcp-server@latest, so Node.js with npx has to be on your PATH. A hosted endpoint at https://clirank-mcp.fly.dev/mcp exists for clients that speak remote HTTP, though the README still calls stdio the most compatible route. To make the agent reach for CLIRank on its own, drop the activation rule into AGENTS.md, CLAUDE.md or your Cursor rules.
What it helps with
- pick an API for a task instead of trusting model memory
- read quickstart and auth setup before writing integration code
- compare two or three APIs on pricing and setup
- check reviews from earlier integration attempts
- file a structured review after wiring up an SDK
Example prompts for the agent
- Use CLIRank to recommend an API for sending 10,000 transactional emails a month, simplicity first. Then read docs for the top result.
- Use CLIRank to recommend an LLM API with tool calling, structured outputs and streaming, then read docs before choosing.
How to install clirank
Platform CLI
claude mcp add --env CLIRANK_API_URL=<CLIRANK_API_URL> --transport stdio clirank -- npx -y clirank-mcp-serverReplace <…> with your own values
Platform CLI
codex mcp add clirank --env CLIRANK_API_URL=<CLIRANK_API_URL> -- npx -y clirank-mcp-serverReplace <…> with your own values
Config file
{
"mcpServers": {
"clirank": {
"command": "npx",
"args": [
"-y",
"clirank-mcp-server"
],
"env": {
"CLIRANK_API_URL": "<CLIRANK_API_URL>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"clirank": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"clirank-mcp-server"
],
"env": {
"CLIRANK_API_URL": "<CLIRANK_API_URL>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e CLIRANK_API_URL=<CLIRANK_API_URL> clirank npx -y clirank-mcp-serverReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about clirank
How do I install clirank in Claude Code?
Run claude mcp add clirank -- npx -y clirank-mcp-server. That registers the server as a stdio process and no CLIRank key is involved.
What does clirank do?
It searches APIs by task, recommends one for a concrete job, returns agent-friendly docs and compares candidates. It also surfaces past integration reviews and accepts a new one.
Does clirank need an API key?
No CLIRank key is required. You only need Node.js with npx, since the server starts with npx -y clirank-mcp-server@latest.
