One vs Kansei MCP Server
A side-by-side look at the One 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 One 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 One when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ONE_SECRET, ONE_IDENTITY, ONE_IDENTITY_TYPE, ONE_PERMISSIONS, ONE_CONNECTION_KEYS, ONE_ACTION_IDS, ONE_KNOWLEDGE_AGENT. - You want tools like
list_one_integrations, find_one_actions, execute_one_action.
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 | 57/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | ONE_SECRETONE_IDENTITYONE_IDENTITY_TYPEONE_PERMISSIONSONE_CONNECTION_KEYSONE_ACTION_IDSONE_KNOWLEDGE_AGENT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 11 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 3 | 3 |
| Full listing | View One | View Kansei MCP Server |
Tools & capabilities
One tools 3
list_one_integrationsList available platforms and active connections, each with the `access` it confers (full, methods, or specific actions)find_one_actionsFind the action for every operation a task needs, across platforms, with its documentation, in one call; `load` fetches more of a document or an alternative'sexecute_one_actionExecute an API action on a connected platform
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.
One
{
"mcpServers": {
"one": {
"command": "npx",
"args": [
"-y",
"@withone/mcp"
],
"env": {
"ONE_SECRET": "YOUR_ONE_SECRET_HERE",
"ONE_IDENTITY": "YOUR_ONE_IDENTITY_HERE",
"ONE_IDENTITY_TYPE": "YOUR_ONE_IDENTITY_TYPE_HERE",
"ONE_PERMISSIONS": "YOUR_ONE_PERMISSIONS_HERE",
"ONE_CONNECTION_KEYS": "YOUR_ONE_CONNECTION_KEYS_HERE",
"ONE_ACTION_IDS": "YOUR_ONE_ACTION_IDS_HERE",
"ONE_KNOWLEDGE_AGENT": "YOUR_ONE_KNOWLEDGE_AGENT_HERE"
}
}
}
}
Kansei MCP Server
{
"mcpServers": {
"kansei-link-kansei-mcp-server": {
"command": "npx",
"args": [
"-y",
"@kansei-link/mcp-server"
]
}
}
}
Frequently asked questions
One is categorized under Aggregators and uses a local stdio subprocess. Kansei MCP Server belongs to Aggregators and uses a local stdio subprocess. Pick One 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.
One has no declared pricing — check the project's own site. 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 one 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, One has a quality signal of 57/100 (Good) with 0 views, 0 installs and 11 GitHub stars. Kansei MCP Server has 60/100 (Good) with 5 views, 0 installs and 1 GitHub stars.