Neurolink vs Manifold
A side-by-side look at the Neurolink and Manifold 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 Manifold 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 Manifold when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
NetworkPolicy, headers.bypass, true.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 63/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| 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 | 4 |
| Directory activity | 5 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Neurolink | View Manifold |
Tools & capabilities
Neurolink tools
No tool names declared yet. Check the project README from the listing page.
Manifold tools 3
NetworkPolicyheaders.bypasstrue
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"
]
}
}
}
Manifold
{
"mcpServers": {
"manifold": {
"url": "https://mcp.notion.com/mcp"
}
}
}
Frequently asked questions
Neurolink is categorized under Aggregators and uses a local stdio subprocess. Manifold belongs to Aggregators and uses a remote HTTP/SSE transport. Pick Neurolink for aggregators work and Manifold 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. Manifold has no declared pricing — check the project's own site. 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 manifold 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. Manifold has 52/100 (Good) with 2 views, 0 installs and 4 GitHub stars.