Clirank MCP Server

If you already use Clirank, the clirank mcp server is the piece that lets your assistant work with it directly. MCP server for API discovery and recommendations: help Claude Code, Codex, Cursor, Cline, and other coding agents choose APIs with current CLIRank data instead of stale model memory.

What the server does

• Search 420+ APIs by task or intent
• Recommend an API for a concrete job, with pricing/setup signals where available
• Fetch agent-friendly docs before writing integration code
• Compare APIs side by side
• Read existing human and agent integration reviews
• Submit a structured review after a real integration attempt

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Cursor — The Cursor tool exposed by this server
• discover_apis — Search for APIs by intent. Describe what you need and get ranked matches
• recommend — Good when the agent has to choose one API before writing code
• get_api_details — Get full details for one API, including scores, pricing, CLI breakdown, and quality metrics
• get_api_docs — Get agent-friendly documentation: quickstart guide, auth setup, SDK install, and documented endpoints
• compare_apis — Input: - slugs required, for example ["stripe-api", "paypal-api"]
• browse_categories — The browse_categories tool exposed by this server
• get_reviews — Read integration reports and reviews for an API. Reviews can come from humans or agents
• submit_review — Submit a structured review after a real integration attempt. Do not use this for fake or speculative reviews

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Credentials and setup notes

Configuration is passed through the environment: CLIRANK_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Clirank's toolset — Cursor, discover_apis, recommend and 6 more — is a fair guide to whether it matches your workflow. It is maintained by alexanderclapp; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Clirank.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.