Log inSubmit server
Neurolink logo

Neurolink

by juspay

Routes MCP requests across AI providers, models, local runtimes, text generation, streaming, and typed decisions.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Neurolink

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "juspay-neurolink": {
      "command": "npx",
      "args": [
        "-y",
        "@juspay/neurolink"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

juspay/neurolink MCP server connects MCP clients to NeuroLink’s provider abstraction for text generation, streaming responses, and typed boolean, choice, or score decisions. It can route requests across providers such as OpenAI, Anthropic, Google, AWS Bedrock, Azure, Mistral, Ollama, LM Studio, and llama.cpp, with aggregator access through LiteLLM and OpenRouter. MCP connectivity covers stdio, HTTP, SSE, and WebSocket transports. Reach for it when an agent needs provider switching, local-runtime support, or structured decision inference through one interface.

Use cases

  • Route agent requests across hosted and local model providers
  • Stream generated responses through an MCP client
  • Evaluate approval or routing rules with typed decisions
  • Combine provider inference with MCP-compliant tools
  • Reduce provider lock-in in TypeScript applications

Key features

  • Generate and stream text
  • Typed boolean, choice, and score decisions
  • Support for hosted, aggregator, and local providers
  • MCP stdio, HTTP, SSE, and WebSocket transports
  • Model metadata and context-window checks
  • Optional routing, compaction, and failover

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

20/20 checks healthy over the last 76d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · @juspay/neurolink (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars157Stargazers on the source repository.
npm downloads22kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Neurolink works

What juspay/neurolink does

juspay/neurolink exposes NeuroLink’s TypeScript-first inference layer through MCP. It gives an MCP-connected application a common interface for sending requests to multiple hosted providers, aggregator services, and local model runtimes instead of coupling the application to one vendor’s API.

The inference surface has three distinct modes. generate returns text, stream delivers incremental output, and decide produces a typed judgment such as a boolean, choice, or score. Decision requests can include application state and named questions, making them suitable for routing, gating, or approval logic where a calibrated answer is more useful than generated prose.

How it works

NeuroLink places providers behind a shared request layer. A provider can be selected per request, allowing an application to move between services such as OpenAI, Anthropic, Google, AWS Bedrock, Azure, Mistral, Ollama, LM Studio, and llama.cpp. LiteLLM and OpenRouter provide access to larger model catalogs through aggregator endpoints.

A model registry supplies metadata for supported models and aliases, including context-window information used during request handling. Provider capabilities declare which inference kinds they support rather than treating every provider as interchangeable.

The MCP connection layer supports stdio, HTTP, SSE, and WebSocket transports. NeuroLink also supports MCP-compliant tool servers, so an application can combine its provider calls with external MCP tools. Its built-in optimization behavior includes model routing, context compaction, and tool selection; these operations are designed to fail open when their optional configuration is unavailable.

Setup and configuration

The project is distributed as the @juspay/neurolink npm package and provides both a TypeScript SDK and a CLI. The documented entry points are the NeuroLink quick-start guide and the package’s npm page. Provider credentials are configured according to the services selected for a deployment; local runtimes can be used without relying on a hosted provider.

The MCP layer can be used with clients that support standard MCP transports. Choose the transport supported by the client and deployment environment, then configure the selected provider credentials and model settings for the requests the client will issue.

Tools and capabilities

  • Generate text through a selected provider.
  • Stream incremental model output.
  • Request typed boolean, choice, or score decisions.
  • Route requests across hosted, aggregator, and local providers.
  • Use model metadata, aliases, and context-window checks.
  • Connect to MCP tools over stdio, HTTP, SSE, or WebSocket.
  • Apply optional routing, context compaction, and tool-selection behavior.
  • Use Redis memory and multi-provider failover in supported deployments.

Limitations and notes

Provider capabilities differ: not every provider necessarily supports all three inference modes. Hosted providers require their respective credentials, while local runtimes require a running Ollama, LM Studio, or llama.cpp setup. Decision inference uses dedicated decision providers or models rather than treating ordinary text generation as an equivalent decision API.

NeuroLink is MIT licensed. Its primary development interfaces are TypeScript and the professional CLI, while MCP provides the connection surface for compatible agent clients.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Neurolink

juspay/neurolink is an MCP server that connects MCP clients to NeuroLink’s multi-provider AI layer and its hosted or local model runtimes. Its main tools support text generation, streamed output, and typed decisions that return boolean, choice, or score judgments for routing, gating, and approval workflows.

Install the `@juspay/neurolink` npm package and follow the project’s quick-start guidance. NeuroLink provides both a TypeScript SDK and a CLI, and the MCP connection can use stdio, HTTP, SSE, or WebSocket transports.

It supports providers including OpenAI, Anthropic, Google, AWS Bedrock, Azure, Mistral, Ollama, LM Studio, and llama.cpp. LiteLLM and OpenRouter extend access to larger model catalogs through aggregator providers.

Yes, Cursor can connect when configured as an MCP client using one of the supported MCP transports. The server supports stdio, HTTP, SSE, and WebSocket connections.

Related MCP servers

All in Aggregators All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNeurolink AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/juspay-neurolink?style=directory)](https://allmcps.com/mcp/juspay-neurolink)
HTML Embed
<a href="https://allmcps.com/mcp/juspay-neurolink"><img src="https://allmcps.com/api/badge/juspay-neurolink?style=directory" alt="Neurolink on AllMCPs" /></a>