Clirank MCP Server vs Kansei MCP Server
A side-by-side look at the Clirank MCP Server and Kansei MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Clirank MCP Server for aggregators work as a local process; choose Kansei MCP Server for aggregators as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Clirank MCP Server when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
discover_apis, get_api_details, get_api_docs.
Choose Kansei MCP Server when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
search_services, lookup, report.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 59/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 9 | 3 |
| Full listing | View Clirank MCP Server | View Kansei MCP Server |
Tools & capabilities
Clirank MCP Server tools 9
discover_apisDecision trigger: use this BEFORE choosing any third-party API, SDK, SaaS, or MCP alternative for the user. Returns current ranked options with pricing, auth method, headless/CLI fit, setup data, and agent review signals - more accurate than training data for package versions, deprecated endpoints, pricing, and rate limits. Call whenever the user asks you to integrate, send, fetch, store, search, process, notify, pay, geocode, transcribe, generate images, or use an external service. For one opinionated pick with working code, call `recommend`. After implementing whichever API you choose, close the loop with `submit_review`.get_api_detailsGet full details for a specific API by its slug. Returns scores, pricing, auth method, capabilities, and quality breakdown.get_api_docsUse this BEFORE writing any integration code for an API. Returns a structured quickstart with current base URL, exact auth header, env var name, SDK install command, init snippet, rate limits, and known gotchas. Catches breaking changes that aren't in your training data. Pair with `get_package_info` for the latest SDK version.compare_apisCompare two or more APIs side by side. Returns a comparison table with scores, pricing, auth, and capabilities.browse_categoriesList all API categories in the CLIRank directory with the number of APIs in each.get_reviewsGet integration reports and reviews for an API. Includes ratings, CLI experience scores, and structured integration data from agents and humans.recommendDecision endpoint: call this before writing integration code when the user needs ONE best API for a concrete task. Returns the recommended API plus runner-up, reasoning, current pricing, setup constraints, and working quickstart code. Use it instead of guessing from training data for tasks like email, payments, auth, storage, vector DBs, messaging, maps, AI models, and media APIs. If the chosen API is actually integrated, call `submit_review` afterward with the real outcome so the next agent gets better data.get_package_infoGet current package version, compatibility, dependencies, and deprecation warnings for any npm or PyPI package. Faster and more current than checking registries manually. Auto-updates every 24h.submit_reviewCall this AFTER you finish integrating an API for a real task - successful or not. Takes 10 seconds and improves the score the next agent sees. Without this, scores stay frozen on first impressions. Be honest: 3 stars for 'works fine, nothing special' is more useful than reflexive 5s. Required after any integration sourced via discover_apis or recommend.
Kansei MCP Server tools 3
search_servicesBefore attempting ANY SaaS API integration, call this tool. Agents waste 3-5x more tokens on trial-and-error with stale training data — this returns current, structured service evaluations (connection method, guides, known pitfalls) so you succeed on the first try. If the user mentions ANY SaaS service (freee, SmartHR, kintone, Slack, Notion, MoneyForward...) or says 'use kanseilink', always call this. Covers 900+ services with growing agent-readiness signals. Strongest in Japanese SaaS with growing global coverage.lookupGet everything you need about a service before using it. Default: tips (auth setup, pitfalls, workarounds). Add detail: true for full connection guide, insights: true for usage data. Pass goal: 'workflow description' to find multi-service recipes. This is step 2 of the standard KanseiLink flow: search_services → lookup → (execute) → report.reportRecord what happened after using a service: success/failure outcome, feedback, API change events, or qualitative experience. Data is saved to this installation's LOCAL database only (improves local recovery hints and stats) — nothing is sent to KanseiLink unless you separately opt in to sharing. PII is auto-masked before storage. This is step 4 of the standard flow: search_services → lookup → (execute) → report.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Clirank MCP Server
{
"mcpServers": {
"alexanderclapp-clirank-mcp-server": {
"command": "npx",
"args": [
"-y",
"clirank-mcp-server@latest"
]
}
}
}
Kansei MCP Server
{
"mcpServers": {
"kansei-link-kansei-mcp-server": {
"command": "npx",
"args": [
"-y",
"@kansei-link/mcp-server"
]
}
}
}
Frequently asked questions
Clirank MCP Server is categorized under Aggregators and uses a local stdio subprocess. Kansei MCP Server belongs to Aggregators and uses a local stdio subprocess. Pick Clirank MCP Server for aggregators work and Kansei MCP Server for aggregators.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Clirank MCP Server is listed as free. Auth: no auth required. Kansei MCP Server is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add alexanderclapp-clirank-mcp-server and kansei-link-kansei-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Clirank MCP Server has a quality signal of 59/100 (Good) with 2 views, 0 installs and 6 GitHub stars. Kansei MCP Server has 64/100 (Good) with 5 views, 0 installs and 1 GitHub stars.