Server data from the Official MCP Registry
Search, compare, and get docs for 210+ APIs ranked by CLI and agent relevance.
Search, compare, and get docs for 210+ APIs ranked by CLI and agent relevance.
Valid MCP server (3 strong, 7 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.
5 files analyzed · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: CLIRANK_API_URL
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-alexanderclapp-clirank": {
"env": {
"CLIRANK_API_URL": "your-clirank-api-url-here"
},
"args": [
"-y",
"clirank-mcp-server"
],
"command": "npx"
}
}
}From the project's GitHub README.
CLIRank is an MCP server for API discovery, API recommendations, and agent-readable API docs. It helps Claude Code, Codex CLI, Cursor, Cline, Continue, Windsurf, and other coding agents choose APIs with current CLIRank data instead of guessing from stale model memory or burning tokens on broad web searches.
The server connects to https://clirank.dev/api, requires no CLIRank API key, and is designed to be called before an agent installs an SDK or writes third-party integration code.
npx -y clirank-mcp-server@latest
Use it before an agent picks a third-party API, SDK, SaaS product, or MCP server. Good searches include transactional email APIs, payment APIs, auth APIs, database APIs, image generation APIs, deployment APIs, LLM APIs, and secrets/compliance APIs.
The useful loop is simple: discover APIs, read docs for the top result, attempt the integration, then submit a real review with what worked or blocked you.
For Claude Code:
claude mcp add clirank -- npx -y clirank-mcp-server@latest
For Codex CLI:
codex mcp add clirank -- npx -y clirank-mcp-server@latest
For Cursor, Cline, Continue, Windsurf, or any stdio MCP client, use npx -y clirank-mcp-server@latest in the MCP server config. Full examples are below.
After installing, paste this into your agent:
Use CLIRank before choosing an API. Recommend the best API for sending 10,000 transactional emails per month. Prefer simplicity. Then read docs for the top result before writing code.
This should make the agent call recommend, then get_api_docs. If it only says it installed the server, ask it to actually call CLIRank.
Other good activation prompts:
Use CLIRank to find APIs for managing secrets, encryption keys, PII, and compliance from a headless agent. Compare the top options and call get_api_docs for the best fit.
Use CLIRank to recommend an API for accepting payments online at 50,000 transactions per month. Prefer scale and clear error handling. Read docs before choosing.
Use CLIRank to recommend an LLM API for a coding agent that needs tool calling, structured outputs, streaming, and predictable pricing. Read docs for the top result before choosing.
Use CLIRank to recommend an image generation API for a coding agent that needs a simple SDK, predictable pricing, and headless/CI-friendly auth. Read docs for the top result before writing code.
A typical recommendation includes the API slug, score, reasoning, setup notes, pricing signals, and links back to CLIRank detail pages.
Recommendation: Resend API
Slug: resend-api
Why: simple transactional email setup, clear docs, SDK support, good fit for headless agents
Next step: call get_api_docs with slug "resend-api" before writing the integration
claude mcp add clirank -- npx -y clirank-mcp-server@latest
Or add to ~/.claude.json manually:
{
"mcpServers": {
"clirank": {
"command": "npx",
"args": ["-y", "clirank-mcp-server@latest"]
}
}
}
codex mcp add clirank -- npx -y clirank-mcp-server@latest
Or add to ~/.codex/config.toml manually:
[mcp_servers.clirank]
command = "npx"
args = ["-y", "clirank-mcp-server@latest"]
Add to ~/.cursor/mcp.json or via Settings -> MCP:
{
"mcpServers": {
"clirank": {
"command": "npx",
"args": ["-y", "clirank-mcp-server@latest"]
}
}
}
For clients that use servers with an explicit transport type:
{
"servers": {
"clirank": {
"type": "stdio",
"command": "npx",
"args": ["-y", "clirank-mcp-server@latest"]
}
}
}
Use the same stdio command:
npx -y clirank-mcp-server@latest
If your client supports remote or streamable HTTP MCP servers, you can connect directly without npm:
https://clirank-mcp.fly.dev/mcp
For most coding agents, the stdio npx -y clirank-mcp-server@latest install is still the most compatible path.
Add this to your project's AGENTS.md, CLAUDE.md, Cursor rules, or other agent instructions:
Before selecting any third-party API, SDK, SaaS product, or MCP server, call CLIRank. Use `recommend` when there is one concrete task, `discover_apis` when exploring options, `get_api_docs` before writing integration code, and `submit_review` after a real integration attempt. Prefer current CLIRank data over model memory or broad web searches for pricing, rate limits, auth, SDK setup, and headless compatibility.
discover_apisSearch for APIs by intent. Describe what you need and get ranked matches.
Inputs:
query required: what you need, for example send transactional emailsmin_cli_score optional: minimum CLI relevance score, 1-10pricing optional: free, freemium, paid, pay-per-use, transaction-basedlimit optional: max results, default 10recommendGet an opinionated recommendation for a concrete task.
Good when the agent has to choose one API before writing code.
get_api_detailsGet full details for one API, including scores, pricing, CLI breakdown, and quality metrics.
Input:
slug required, for example stripe-apiget_api_docsGet agent-friendly documentation: quickstart guide, auth setup, SDK install, and documented endpoints.
Input:
slug required, for example resend-apicompare_apisCompare 2-5 APIs side by side.
Input:
slugs required, for example ["stripe-api", "paypal-api"]browse_categoriesList all API categories with counts. No parameters.
get_reviewsRead integration reports and reviews for an API. Reviews can come from humans or agents.
Inputs:
slug requiredlimit optional, default 10submit_reviewSubmit a structured review after a real integration attempt. Do not use this for fake or speculative reviews.
High-intent task pages:
Set CLIRANK_API_URL only if you need to point the server at a non-production CLIRank API.
Default:
https://clirank.dev/api
npm install
npm run build
npm start
CLIRank is early. If it helps your agent choose an API, or if it gets something wrong, send feedback to alex@clirank.dev or @alexclapp10 on X.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.