
Clirank
io.github.alexanderclappPublished by GitHub account alexanderclappv0.2.1Updated Oct 28, 2026
Search, compare, and get docs for 210+ APIs ranked by CLI and agent relevance.
Overview
CLIRank lets a coding assistant search, compare and read docs for hundreds of third-party APIs before it picks one or writes integration code.
- What you can do
- Search and browse APIs by task or intent, with category listings and pricing filters
- Get an opinionated recommendation for one concrete job, with pricing and setup signals
- Read full API details: scores, pricing, CLI breakdown and quality metrics
- Fetch agent-friendly docs covering quickstart, auth setup, SDK install and endpoints
- Compare two to five APIs side by side
- Read existing integration reviews and submit a structured review after a real attempt
- When to use it
- Use it when an assistant is about to choose a third-party API, SDK, SaaS product or MCP server and you want current pricing, auth and setup information instead of relying on model memory or broad web searches.
- Requirements
- Runs locally over stdio via npx (Node.js required); a hosted HTTP endpoint is also offered. No CLIRank API key is needed. The optional CLIRANK_API_URL variable points the server at a non-production API base URL.
Installation
In SourceWeft
- Open Clirank in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
CLIRank MCP server
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.
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.
What it 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.
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.
Fastest install path
For Claude Code:
For Codex CLI:
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.
One-minute activation test
After installing, paste this into your agent:
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.
If you can call tools directly, use this as the first smoke test:
Then call get_api_docs for the returned slug. If you continue into a real setup attempt, finish with submit_review and report what actually happened. Docs-only is fine. Fake live success is not.
Other good activation prompts:
Example CLIRank output
A typical recommendation includes the API slug, score, reasoning, setup notes, pricing signals, and links back to CLIRank detail pages.
Install by agent
Claude Code
Or add to ~/.claude.json manually:
Codex CLI
Or add to ~/.codex/config.toml manually:
Cursor
Add to ~/.cursor/mcp.json or via Settings -> MCP:
VS Code / Copilot-style config
For clients that use servers with an explicit transport type:
Cline / Continue / Windsurf
Use the same stdio command:
Hosted MCP endpoint
If your client supports remote or streamable HTTP MCP servers, you can connect directly without npm:
For most coding agents, the stdio npx -y clirank-mcp-server@latest install is still the most compatible path.
Agent activation rule
Add this to your project's AGENTS.md, CLAUDE.md, Cursor rules, or other agent instructions:
Tools
discover_apis
Search for APIs by intent. Describe what you need and get ranked matches.
Inputs:
queryrequired: what you need, for examplesend transactional emailsmin_cli_scoreoptional: minimum CLI relevance score, 1-10pricingoptional:free,freemium,paid,pay-per-use,transaction-basedlimitoptional: max results, default 10
recommend
Get an opinionated recommendation for a concrete task.
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.
Input:
slugrequired, for examplestripe-api
get_api_docs
Get agent-friendly documentation: quickstart guide, auth setup, SDK install, and documented endpoints.
Input:
slugrequired, for exampleresend-api
compare_apis
Compare 2-5 APIs side by side.
Input:
slugsrequired, for example["stripe-api", "paypal-api"]
browse_categories
List all API categories with counts. No parameters.
get_reviews
Read integration reports and reviews for an API. Reviews can come from humans or agents.
Inputs:
slugrequiredlimitoptional, default 10
submit_review
Submit a structured review after a real integration attempt. Do not use this for fake or speculative reviews.
When passing integrationReport, always include evidenceLevel:
docs-only— you inspected docs but did not install, authenticate, or make a request.community-signals— you summarised public issues/forums/docs, not your own integration.no-key-live— you attempted setup but could not make an authenticated live request.sandbox-live,byo-test-key, orproduction-live— you made a real request.
Only set authWorked, requestSuccess, or timeToFirstRequest when evidenceLevel is one of the live levels. Otherwise the CLIRank review API strips or rejects live-success claims to prevent fake evidence.
Useful CLIRank pages
- Directory: https://clirank.dev
- API docs: https://clirank.dev/api/docs
- Task pages: https://clirank.dev/tasks
- LLM context: https://clirank.dev/llms.txt
- Full LLM context: https://clirank.dev/llms-full.txt
High-intent task pages:
- https://clirank.dev/tasks/llm-api-for-coding-agents
- https://clirank.dev/tasks/authentication-api-for-ai-agents
- https://clirank.dev/tasks/database-api-for-ai-agents
- https://clirank.dev/tasks/payments-api-for-ai-agents
- https://clirank.dev/tasks/transactional-email-api-for-agents
- https://clirank.dev/tasks/deployment-api-for-ai-agents
- https://clirank.dev/tasks/image-generation-api-for-agents
Configuration
Set CLIRANK_API_URL only if you need to point the server at a non-production CLIRank API.
Default:
Development
Feedback
CLIRank is early. If it helps your agent choose an API, or if it gets something wrong, send feedback to [email protected] or @alexclapp10 on X.
Source: README.md at commit 997bb8c
Tools
0Version history
1- v0.2.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts