Nexus MCP server - Intelligent AI model search and discovery with OpenRouter integration
Nexus MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Nexus MCP server - Intelligent AI model search and discovery with OpenRouter integration.
Nexus is a Model Context Protocol (MCP) server that provides AI-powered search functionality through the OpenRouter API. It integrates with MCP-compatible clients including Claude Desktop and Cursor, providing search capabilities via multiple model families including Perplexity Sonar (real-time web search) and Grok 4 (training-data knowledge).
Once Nexus is connected, these are the calls the assistant has available:
Pricing — See current rates at OpenRouter ModelsMonitoring — Usage tracking available in OpenRouter dashboardLimits — Configure spending limits in OpenRouter account settingsOptimization — Server implements response caching and request deduplication to minimize redundant API callsDeployment — The Deployment tool exposed by this serverArchitecture — The Architecture tool exposed by this serverPrerequisites — The Prerequisites tool exposed by this serverCursor — The Cursor tool exposed by this serversearch — The main search tool that provides AI-powered search capabilitiesYou will need 2 environment variables: OPENROUTER_API_KEY, OPENROUTER_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
npx on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Nexus's toolset — Pricing, Monitoring, Limits and 6 more — is a fair guide to whether it matches your workflow. It is maintained by adawalli; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Pricing | See current rates at [OpenRouter Models](https://openrouter.ai/models) |
| Monitoring | Usage tracking available in OpenRouter dashboard |
| Limits | Configure spending limits in OpenRouter account settings |
| Optimization | Server implements response caching and request deduplication to minimize redundant API calls |
| Deployment | The Deployment tool exposed by this server. |
| Architecture | The Architecture tool exposed by this server. |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Cursor | The Cursor tool exposed by this server. |
| search | The main search tool that provides AI-powered search capabilities. |
{
"mcpServers": {
"nexus": {
"command": "npx",
"args": ["-y", "npx"],
"env": {
"OPENROUTER_API_KEY": "your-value",
"OPENROUTER_BASE_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| OPENROUTER_API_KEY | Credential the server authenticates with. | Yes |
| OPENROUTER_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.