RUAGENTIC Directory vs Kansei MCP Server | AllMCPs
Side-by-Side Model Context Protocol Comparison
RUAGENTIC Directory vs Kansei MCP Server
In-depth architectural comparison of the RUAGENTIC Directory and Kansei MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
RUAGENTIC Directory
Aggregators · Remote HTTP/SSE
Quality: 47/100 (Fair) | Auth: No auth required
Kansei MCP Server
Aggregators · Local stdio
Quality: 65/100 (Great) | Auth: No auth required
Verdict Summary: Choose RUAGENTIC Directory if you need specialized Aggregators tools running via a hosted cloud SSE transport. Choose Kansei MCP Server if your workspace requires Aggregators integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose RUAGENTIC Directory when:
You need dedicated capabilities in the Aggregators domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Search MCP servers, MCP clients and AI agents from an AI assistant. Two read-only tools, search_directory and get_listing, search public listings and return connection details. Free Streamable HTTP endpoint with no API key or local installation.
Local-first MCP navigator with verified data on 11,000+ SaaS services, 200 workflow recipes, and 89-97% token savings vs web search.
No explicit tool names declared in metadata yet. Check project README on main listing page.
Kansei MCP Server Tools (3)
search_services
Before 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.
lookup
Get 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.
report
Contribute data back to the KanseiLink community. Report success/failure after using a service (5 seconds, helps everyone), submit feedback, record API change events, or share your qualitative experience. PII is auto-masked. This is step 4 of the standard flow: search_services → lookup → (execute) → report.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
RUAGENTIC Directory is categorized under Aggregators and uses a remote streaming HTTP/SSE transport. In contrast, Kansei MCP Server belongs to Aggregators using local stdio subprocess. Select RUAGENTIC Directory when you need capabilities focused on aggregators and Kansei MCP Server when you require tools for aggregators.