Clirank MCP Server logo

Clirank MCP Server

by alexanderclapp

Ranks and evaluates APIs so coding agents can choose integrations using current pricing, setup, auth, and review data.

Install Clirank MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "alexanderclapp-clirank-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "clirank-mcp-server@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

alexanderclapp/clirank-mcp-server MCP server connects coding agents to CLIRank's API directory for API discovery, recommendations, comparisons, documentation, and reviews. It runs locally through npx over stdio or through a hosted streamable HTTP endpoint, and does not require a CLIRank API key. Reach for it before selecting an external API or writing integration code when current pricing, authentication, SDK, rate-limit, or headless-agent details matter.

Use cases

  • Discover APIs for a concrete product requirement
  • Recommend one service before writing integration code
  • Compare API pricing, authentication, and capabilities
  • Retrieve current SDK setup and rate-limit details
  • Submit an evidence-based integration review

Key features

  • Ranked API discovery by task or intent
  • Opinionated API recommendations
  • Structured integration quickstarts
  • Side-by-side API comparisons
  • Human and agent review lookup
  • npm and PyPI package status checks

Tools9

What Clirank MCP Server lets your agent do. Expand a tool for its parameters.

Verified live~2.2k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

6/6 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · clirank-mcp-server@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars6Stargazers on the source repository.
npm downloads213Package downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.
Tools exposed9Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Clirank MCP Server works

What alexanderclapp/clirank-mcp-server MCP server does

alexanderclapp/clirank-mcp-server MCP server gives coding agents access to CLIRank, a directory that evaluates APIs for agent-oriented integration work. It helps an agent find candidate services, select one for a concrete task, inspect current setup details, compare alternatives, read integration feedback, and record the result of a real integration attempt.

The directory covers API use cases such as email, payments, authentication, databases, messaging, maps, media, image generation, deployment, secrets, and LLM services. The returned information can include pricing, authentication method, capabilities, CLI or headless suitability, quality scores, setup constraints, and review signals.

How it works

The server sends requests to https://clirank.dev/api by default and does not require a CLIRank API key. An agent can run it as a local stdio process with npx -y clirank-mcp-server@latest, or connect to the hosted endpoint at https://clirank-mcp.fly.dev/mcp when the client supports remote or streamable HTTP MCP servers.

A typical workflow starts with recommend for one concrete task or discover_apis when several possibilities need to be explored. The agent can then call get_api_details, compare_apis, or get_reviews, followed by get_api_docs before writing integration code. After a genuine setup or request attempt, submit_review records the outcome. Review evidence must distinguish documentation-only research from live testing.

Setup and configuration

The local installation uses the npm package through npx, so a project dependency is not required. Claude Code and Codex CLI provide dedicated add commands; Cursor, Cline, Continue, Windsurf, and other stdio clients can use the same command in their MCP configuration. VS Code configurations that require an explicit transport can declare the server as stdio with npx and the package name as arguments.

The optional CLIRANK_API_URL variable changes the upstream CLIRank API URL. Leave it unset to use the production default. Development from a checkout uses npm install, npm run build, and npm start.

Tools and capabilities

alexanderclapp/clirank-mcp-server MCP server exposes these operations:

  • discover_apis searches ranked APIs by task, with optional CLI-score, pricing, and result-limit filters.
  • recommend returns one suggested API, a runner-up, reasoning, pricing, constraints, and quickstart information.
  • get_api_details retrieves scores, pricing, authentication, capabilities, and quality metrics for a slug.
  • get_api_docs returns an integration-oriented quickstart with the base URL, auth header, environment variable name, SDK command, initialization example, rate limits, and known issues.
  • compare_apis compares two to five API slugs.
  • browse_categories lists directory categories and API counts.
  • get_reviews reads human and agent integration reports.
  • get_package_info checks current npm or PyPI package versions, compatibility, dependencies, and deprecation warnings; its data refreshes every 24 hours.
  • submit_review accepts a structured report after an actual integration attempt.

Limitations and notes

Results come from CLIRank's available directory data and reviews, so the server does not replace validating an API against the user's own requirements. submit_review is intended for real outcomes, not guessed or speculative success claims. Live fields such as authentication success or request success should only be reported when the integration evidence is from a live testing level.

The stdio installation is identified as the most compatible path for most coding agents, while remote use depends on client support for hosted MCP endpoints.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Clirank MCP Server

alexanderclapp/clirank-mcp-server is an MCP server that connects coding agents to the CLIRank API directory. Its main tools discover and recommend APIs, compare services, retrieve current integration docs, inspect reviews, check package information, and submit reports after real integration attempts.

Install it as a stdio server with `npx -y clirank-mcp-server@latest`. Claude Code and Codex CLI can add it with their MCP commands, while Cursor, Cline, Continue, Windsurf, and VS Code use equivalent MCP configuration entries.

No, it does not require a CLIRank API key. It uses `https://clirank.dev/api` by default, and `CLIRANK_API_URL` can be set only when a different CLIRank API endpoint is needed.

Call `get_api_docs` with the selected API slug. It returns setup details such as the base URL, authentication header, environment variable name, SDK installation command, initialization example, rate limits, and known gotchas.

Yes, `compare_apis` compares two to five API slugs using factors such as scores, pricing, authentication, and capabilities. Use `discover_apis` or `recommend` first if you do not yet have provider slugs.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewClirank MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/alexanderclapp-clirank-mcp-server?style=directory)](https://allmcps.com/mcp/alexanderclapp-clirank-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/alexanderclapp-clirank-mcp-server"><img src="https://allmcps.com/api/badge/alexanderclapp-clirank-mcp-server?style=directory" alt="Clirank MCP Server on AllMCPs" /></a>