原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Clirank

作者:alexanderclapp版本 0.2.1i★ –i在你的电脑上运行
注册名称io.github.alexanderclapp/clirank

安装

概览

作者提供的说明(英文原文)

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 搜索与 AI 记忆

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "clirank": {
      "command": "npx",
      "args": [
        "-y",
        "clirank-mcp-server"
      ],
      "env": {
        "CLIRANK_API_URL": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add clirank --env CLIRANK_API_URL=your-value -- npx -y clirank-mcp-server

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "clirank": {
      "command": "npx",
      "args": [
        "-y",
        "clirank-mcp-server"
      ],
      "env": {
        "CLIRANK_API_URL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "clirank": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "clirank-mcp-server"
      ],
      "env": {
        "CLIRANK_API_URL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • CLIRANK_API_URL env
    Override the CLIRank API base URL (defaults to https://clirank.dev/api)

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 alexanderclapp 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“搜索与 AI 记忆”中的其他服务器比较i

  • 星标数多于此分类中其他 7259 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 7259 个服务器的 7% 更新
  • 基础检查结果等于或优于此分类中其他 7259 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Clirank 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.2.1)于7个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:Context7, Codebase Memory, Exa

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Context7

作者:upstash

Up-to-date docs for AI agents

电脑或云端★ 64,224MIT今天更新
安装

Codebase Memory

作者:DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

在你的电脑上运行★ 48,148MIT20天前更新
安装

Exa

作者:exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

在云端运行★ 5,213MIT上个月更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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.

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:

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.

One-minute activation test

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.

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

{

"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:

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.

Example CLIRank output

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

Install by agent

Claude Code
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 CLI
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"]

Cursor

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

{

"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:

{

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

Cline / Continue / Windsurf

Use the same stdio command:

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:

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:

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

  • 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:

https://clirank.dev/api

Development

npm install

npm run build npm start

Feedback

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.

问 PopNx