Neurolink vs Treg.to
A side-by-side look at the Neurolink and Treg.to 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 Treg.to for aggregators. 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 63/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 157 | 5,874 |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Neurolink | View Treg.to |
Tools & capabilities
Neurolink tools
No tool names declared yet. Check the project README from the listing page.
Treg.to tools
No tool names declared yet. Check the project README from the listing page.
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"
]
}
}
}
Treg.to
No confirmed install command for Treg.to yet — follow the setup steps linked from its listing page rather than a guessed package name.