Neurolink vs One
A side-by-side look at the Neurolink and One MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Neurolink for aggregators work as a local process; choose One 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 Neurolink when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
Choose One when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
ONE_SECRET. - You want tools like
list_one_integrations, find_one_actions, execute_one_action.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 63/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | None listed | ONE_SECRET |
| Verified owner | Community listing | Community listing |
| GitHub stars | 157 | 11 |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Neurolink | View One |
Tools & capabilities
Neurolink tools
No tool names declared yet. Check the project README from the listing page.
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
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.
Neurolink
{
"mcpServers": {
"juspay-neurolink": {
"command": "npx",
"args": [
"-y",
"@juspay/neurolink"
]
}
}
}
One
{
"mcpServers": {
"one": {
"command": "npx",
"args": [
"-y",
"@withone/mcp"
],
"env": {
"ONE_SECRET": "YOUR_ONE_SECRET_HERE"
}
}
}
}
Frequently asked questions
Neurolink is categorized under Aggregators and uses a local stdio subprocess. One belongs to Aggregators and uses a local stdio subprocess. Pick Neurolink for aggregators work and One 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.
Neurolink is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. One has no declared pricing — check the project's own site. Auth: api key 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 juspay-neurolink and one as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Neurolink has a quality signal of 63/100 (Good) with 5 views, 0 installs and 157 GitHub stars. One has 60/100 (Good) with 0 views, 0 installs and 11 GitHub stars.