Neurolink vs Toolmesh
A side-by-side look at the Neurolink and Toolmesh 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 Toolmesh for aggregators over a hosted endpoint. 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 Toolmesh when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: other.
- You have the keys it needs:
TOOLMESH_AUTH_PASSWORD, TOOLMESH_API_KEY, TOOLMESH_AUTH_USER, TOOLMESH_AUTH_PLAN, TOOLMESH_AUTH_ROLES, TOOLMESH_BCRYPT_MAX_CONCURRENT.
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 | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | other |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | None listed | TOOLMESH_AUTH_PASSWORDTOOLMESH_API_KEYTOOLMESH_AUTH_USERTOOLMESH_AUTH_PLANTOOLMESH_AUTH_ROLESTOOLMESH_BCRYPT_MAX_CONCURRENT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 157 | 6 |
| Directory activity | 5 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Neurolink | View Toolmesh |
Tools & capabilities
Neurolink tools
No tool names declared yet. Check the project README from the listing page.
Toolmesh 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"
]
}
}
}
Toolmesh
{
"mcpServers": {
"toolmesh": {
"url": "http://localhost:8123/mcp"
}
}
}
Frequently asked questions
Neurolink is categorized under Aggregators and uses a local stdio subprocess. Toolmesh belongs to Aggregators and uses a remote HTTP/SSE transport. Pick Neurolink for aggregators work and Toolmesh 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. Toolmesh is listed as free. Auth: other. 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 toolmesh 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. Toolmesh has 43/100 (Fair) with 2 views, 0 installs and 6 GitHub stars.