Aggregators and gateways · MCP server
Neurolink: MCP server, setup and security
Neurolink is an open-source MCP server published on GitHub that lets an AI agent orchestrate multiple models and agents with human oversight and context summarization. Its repository has 157 stars and its last commit is from October 24, 2026 and it is licensed under MIT.
What Neurolink does
According to its repository: “Edge-first AI platform unifying many providers and models, with multi-agent orchestration, human-in-the-loop workflows, guardrails and context summarization.”
The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. Neurolink is listed under Aggregators and gateways, a category of 141 servers in the directory, where it ranks #53 by stars.
Topics declared by the repository: developer-tools, agents, local-first, neurolink, ai-sdk, anthropic.
Installing and connecting Neurolink
No package or remote server is declared in the official MCP registry: you install it from source, following the repository README.
It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: TypeScript. Listed systems: macOS, Windows, Linux.
Security: what to check
Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.
None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Neurolink. That does not replace reading the code.
Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.
Project activity and maintenance
Created on May 31, 2025, the juspay/neurolink repository has 157 stars and 133 forks, with 18 open issues. It has more stars than 74% of the servers in the directory. It received changes this month.
Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.
Verdict
Neurolink is a reasonable choice; check the points below before connecting it.
Strengths
- Active project: recent commit
- Permissive licence (MIT)
Limitations
- Install from source
Alternatives
- GitDiagram18.4K ★
- Mockserver monorepo5K ★
- Paperclip106.8K ★
- Basebalance.cloud — x402 RPC & MCP gateway7.5K ★
- AIHOT8.5K ★
- OpenWork MCP Gateway24.2K ★
Learn more
Frequently asked questions
How do I install Neurolink?
No package is declared in the MCP registry: clone the juspay/neurolink repository, follow its README, then declare the start command in your client's MCP configuration.
Is Neurolink free?
The code is published under the MIT licence and can be used free of charge.
Is Neurolink safe?
No risk signal found (system access, secrets, licence, abandonment). As with any MCP server, keep rights minimal and read the code before sensitive use.
Is it an official server?
Nothing says so: it is a project published by juspay on GitHub. Check who maintains it before giving it access.
What are the alternatives to Neurolink?
In the same category: GitDiagram, Mockserver monorepo, Paperclip, and Basebalance.cloud — x402 RPC & MCP gateway. GitDiagram and Mockserver monorepo score higher on our grid.
Related articles
- Build your own MCP server in 30 minutesOctober 24, 2026
- Automate your inbox with an AI agentOctober 18, 2026
- MCP, A2A, and tool calling: agent protocols explainedOctober 17, 2026
- Build an AI agent with n8n, without codingOctober 16, 2026
Neutrality. No affiliate links. No vendor pays to be reviewed, rated or ranked. Reviews are directed by François Chollet, neutral and factual, and every data point is dated and sourced. How we score