Clirank

io.github.alexanderclapp由 GitHub 帳號 alexanderclapp 發布v0.2.1更新於 Oct 28, 2026

Search, compare, and get docs for 210+ APIs ranked by CLI and agent relevance.

概覽

AI 產生的概覽

CLIRank 讓程式開發助理在挑選第三方 API 或撰寫整合程式碼前,搜尋、比較並查閱數百個 API 的文件。

可以做什麼
  • 依任務或意圖搜尋 API,並瀏覽分類清單與價格篩選
  • 針對單一具體任務給出有立場的推薦,附上價格與接入訊號
  • 查看單一 API 的完整詳情:評分、價格、CLI 面向拆解與品質指標
  • 取得面向代理的說明文件:快速上手、驗證設定、SDK 安裝與端點清單
  • 將 2 至 5 個 API 並排比較
  • 讀取既有整合評論,並在實際嘗試後提交結構化評論
適用情境
當助理即將選擇第三方 API、SDK、SaaS 產品或 MCP 伺服器,而你希望取得目前的價格、驗證與接入資訊,而不是依賴模型記憶或大範圍網頁搜尋時使用。
執行需求
透過 npx 以 stdio 在本機執行(需要 Node.js);另提供託管的 HTTP 端點。不需要 CLIRank API 金鑰。選用變數 CLIRANK_API_URL 可指向非正式環境的 API 基礎位址。
安裝前請注意
伺服器會將搜尋查詢、slug 與提交的評論傳送到 CLIRank API。提交評論會公開發布內容,應僅在實際整合嘗試後進行;除非提供實際執行的證據等級,服務會拒絕或移除「實際成功」的聲明。推薦結果屬第三方排名,並非經驗證的建議。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Clirank,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

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.

bash
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.

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:

bash
claude mcp add clirank -- npx -y clirank-mcp-server@latest

For Codex CLI:

bash
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.

One-minute activation test

After installing, paste this into your agent:

text
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.

If you can call tools directly, use this as the first smoke test:

json
{  "tool": "recommend",  "arguments": {    "task": "send transactional email from Next.js with webhooks and SDK",    "volume": 10000,    "priority": "simplicity"  }}

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:

text
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.
text
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.
text
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.
text
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.

Example CLIRank output

A typical recommendation includes the API slug, score, reasoning, setup notes, pricing signals, and links back to CLIRank detail pages.

text
Recommendation: Resend APISlug: resend-apiWhy: simple transactional email setup, clear docs, SDK support, good fit for headless agentsNext step: call get_api_docs with slug "resend-api" before writing the integration

Install by agent

Claude Code

bash
claude mcp add clirank -- npx -y clirank-mcp-server@latest

Or add to ~/.claude.json manually:

json
{  "mcpServers": {    "clirank": {      "command": "npx",      "args": ["-y", "clirank-mcp-server@latest"]    }  }}

Codex CLI

bash
codex mcp add clirank -- npx -y clirank-mcp-server@latest

Or add to ~/.codex/config.toml manually:

toml
[mcp_servers.clirank]command = "npx"args = ["-y", "clirank-mcp-server@latest"]

Cursor

Add to ~/.cursor/mcp.json or via Settings -> MCP:

json
{  "mcpServers": {    "clirank": {      "command": "npx",      "args": ["-y", "clirank-mcp-server@latest"]    }  }}

VS Code / Copilot-style config

For clients that use servers with an explicit transport type:

json
{  "servers": {    "clirank": {      "type": "stdio",      "command": "npx",      "args": ["-y", "clirank-mcp-server@latest"]    }  }}

Cline / Continue / Windsurf

Use the same stdio command:

bash
npx -y clirank-mcp-server@latest

Hosted MCP endpoint

If your client supports remote or streamable HTTP MCP servers, you can connect directly without npm:

text
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.

Agent activation rule

Add this to your project's AGENTS.md, CLAUDE.md, Cursor rules, or other agent instructions:

text
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.

Tools

discover_apis

Search for APIs by intent. Describe what you need and get ranked matches.

Inputs:

  • query required: what you need, for example send transactional emails
  • min_cli_score optional: minimum CLI relevance score, 1-10
  • pricing optional: free, freemium, paid, pay-per-use, transaction-based
  • limit optional: 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:

  • slug required, for example stripe-api

get_api_docs

Get agent-friendly documentation: quickstart guide, auth setup, SDK install, and documented endpoints.

Input:

  • slug required, for example resend-api

compare_apis

Compare 2-5 APIs side by side.

Input:

  • slugs required, 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:

  • slug required
  • limit optional, 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, or production-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

High-intent task pages:

Configuration

Set CLIRANK_API_URL only if you need to point the server at a non-production CLIRank API.

Default:

text
https://clirank.dev/api

Development

bash
npm installnpm run buildnpm start

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.

來源:README.md,提交 997bb8c

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.2.1最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分