In-depth architectural comparison of the Sylex Search 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
Sylex Search
Aggregators · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Kansei MCP Server
Aggregators · Local stdio
Quality: 65/100 (Great) | Auth: No auth required
Verdict Summary: Choose Sylex Search if you need specialized Aggregators tools running via a local process. 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 Sylex Search when:
You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: AC_SUPABASE_URL, AC_SUPABASE_KEY, TRANSPORT, PORT.
Universal search engine for AI agents. Discover products, services, and businesses across every category. 10 MCP tools, zero LLM calls, millisecond responses. npx sylex-search
Local-first MCP navigator with verified data on 11,000+ SaaS services, 200 workflow recipes, and 89-97% token savings vs web search.
Category & Scope
Tools & Capabilities Breakdown
Sylex Search Tools (10)
search.discover
Search the index by natural language query. Returns ranked results with fit scores.
search.details
Get full product data by ID — pricing, features, integrations, reviews.
search.compare
Side-by-side comparison of 2-5 products.
search.categories
Browse all categories and subcategories with counts.
search.alternatives
Find similar products scored by relevance.
search.feedback
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).
Sylex Search is categorized under Aggregators and uses a local stdio subprocess. In contrast, Kansei MCP Server belongs to Aggregators using local stdio subprocess. Select Sylex Search when you need capabilities focused on aggregators and Kansei MCP Server when you require tools for aggregators.
Add MCP connection config so other agents can discover and connect.
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.