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 分