search-webdeveloper-tools

Nexus (OpenRouter Search)

adawalli

by adawalli

Experience AI-powered search with Nexus using OpenRouter—intelligent results and source citations, similar to Bing by Mi

Provides web search capabilities through OpenRouter's Perplexity Sonar models, delivering intelligent search results with source citations for current information retrieval.

github stars

19

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

Zero-install via bunx/npxMultiple AI model optionsProduction-ready with caching

best for

  • / Researchers needing current information with sources
  • / Developers building AI applications with search
  • / Anyone using Claude Desktop who needs web search

capabilities

  • / Search the web with AI-powered queries
  • / Get source citations with search results
  • / Access real-time information through Perplexity Sonar
  • / Query training data knowledge via Grok models
  • / Cache and deduplicate search requests

what it does

Provides AI-powered web search through OpenRouter's Perplexity models, delivering search results with source citations directly in MCP-compatible clients like Claude Desktop.

about

Nexus (OpenRouter Search) is a community-built MCP server published by adawalli that provides AI assistants with tools and capabilities via the Model Context Protocol. Experience AI-powered search with Nexus using OpenRouter—intelligent results and source citations, similar to Bing by Mi It is categorized under search web, developer tools.

how to install

You can install Nexus (OpenRouter Search) in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

license

MIT

Nexus (OpenRouter Search) is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

readme

# 🔍 Nexus MCP Server **AI integration without the complexity** [![npm version](https://img.shields.io/npm/v/nexus-mcp.svg)](https://www.npmjs.com/package/nexus-mcp) ![NPM Downloads](https://img.shields.io/npm/dt/nexus-mcp?style=flat-square&logo=npm&label=downloads) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) [![TypeScript](https://img.shields.io/badge/TypeScript-Ready-blue.svg)](https://www.typescriptlang.org/) [![MCP Compatible](https://img.shields.io/badge/MCP-Compatible-green.svg)](https://modelcontextprotocol.io/) [![CodeRabbit Pull Request Reviews](https://img.shields.io/coderabbit/prs/github/adawalli/nexus)](https://coderabbit.ai) [![Trust Score](https://archestra.ai/mcp-catalog/api/badge/quality/adawalli/nexus)](https://archestra.ai/mcp-catalog/adawalli__nexus) _Intelligent AI model search and discovery with zero-install simplicity_ [Quick Start](#-quick-start) • [Features](#-features) • [Documentation](#-documentation) • [Contributing](#-contributing)
--- ## What is Nexus? 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). ### Key Characteristics - **Zero-install deployment**: Executable via `bunx` (or `npx`) with no build requirements - **OpenRouter integration**: Multiple AI models including Perplexity Sonar (web search) and Grok 4 (training data) - **MCP protocol compliance**: Implements standard MCP tool and resource interfaces - **Production architecture**: Includes request caching, deduplication, retry logic, and error handling - **Type-safe implementation**: Full TypeScript coverage with strict type checking ## Features ### Deployment - Bunx/NPX-based execution with zero local installation - Cross-platform compatibility (macOS, Linux, Windows) - Bun 1.0+ or Node.js 18+ runtime requirement - Automated version updates via npm registry ### Search Capabilities - **Multiple model tiers** with different capabilities: - `sonar` - Fast Q&A, real-time web search (30s timeout, standard tier) - `sonar-pro` - Multi-step queries, real-time web search (60s timeout, premium tier) - `sonar-reasoning-pro` - Chain-of-thought reasoning, real-time web search (120s timeout, premium tier) - `sonar-deep-research` - Exhaustive research reports, real-time web search (300s timeout, premium tier) - `grok-4` - Training-data knowledge, no real-time search (60s timeout, premium tier) - Real-time web search with current information (Perplexity models) - Training-data knowledge responses (Grok 4) - Structured citation extraction from responses - Configurable model parameters (temperature, max tokens, timeout override) ### Architecture - Comprehensive error handling with typed error classes - Request caching with configurable TTL - Request deduplication for concurrent identical queries - Automatic retry logic with exponential backoff - Winston-based structured logging - TypeScript strict mode implementation with full type coverage ## Quick Start ### Prerequisites - [Bun](https://bun.sh) 1.0+ (recommended) or Node.js 18+ - OpenRouter API key ([register at openrouter.ai](https://openrouter.ai)) ### Quick Install Execute the server without local installation: ```bash # Set your OpenRouter API key export OPENROUTER_API_KEY=your-api-key-here # Run the server via bunx (recommended) bunx nexus-mcp # Or via npx npx nexus-mcp ``` The server starts and listens for MCP client connections via STDIO transport. ### Testing the Installation ```bash # Test the CLI help bunx nexus-mcp --help # Test the version bunx nexus-mcp --version # Run with your API key OPENROUTER_API_KEY=your-key bunx nexus-mcp ``` ## Alternative: Local Development Installation For local development or customization: 1. Clone the repository: ```bash git clone https://github.com/adawalli/nexus.git cd nexus ``` 2. Install dependencies: ```bash bun install ``` 3. Build the server: ```bash bun run build ``` 4. Configure your OpenRouter API key: ```bash # Copy the example environment file cp .env.example .env # Edit .env and add your actual API key # OPENROUTER_API_KEY=your-api-key-here ``` 5. Test the server: ```bash bun run start ``` ## Integration with MCP Clients ### Bunx-Based Integration (Recommended) Configure MCP clients to execute the server via bunx: ### Claude Code Configuration in `~/.claude/mcp_settings.json`: ```json { "mcpServers": { "nexus": { "command": "bunx", "args": ["nexus-mcp"], "env": { "OPENROUTER_API_KEY": "your-api-key-here" } } } } ``` Restart Claude Code after configuration changes. ### Cursor Add server configuration in Cursor's MCP settings: - **Name**: `nexus` - **Command**: `bunx` - **Args**: `["nexus-mcp"]` - **Environment Variables**: `OPENROUTER_API_KEY=your-api-key-here` Restart Cursor after configuration changes. ### Generic MCP Client Configuration Standard MCP client connection parameters: - **Transport**: stdio - **Command**: `bunx` - **Args**: `["nexus-mcp"]` - **Environment**: `OPENROUTER_API_KEY=your-api-key-here` ### Alternative: npx or Local Installation If you don't have Bun installed, use `npx` in place of `bunx` in any of the configurations above. For a local installation (after following the local development setup): ```json { "mcpServers": { "nexus": { "command": "bun", "args": ["run", "/path/to/nexus-mcp/dist/cli.js"], "env": { "OPENROUTER_API_KEY": "your-api-key-here" } } } } ``` ## Usage Once integrated, you can use the search tool in your MCP client: ### Basic Search ``` Use the search tool to find information about "latest developments in AI" ``` ### Advanced Search with Parameters ``` Search for "climate change solutions" using: - Model: sonar-pro - Max tokens: 2000 - Temperature: 0.3 ``` ### Using Different Models ``` # Fast Q&A with real-time web search (default) Search for "latest news" with model: sonar # Deep research with comprehensive analysis Search for "AI safety research" with model: sonar-deep-research # Knowledge from training data (no web search) Search for "explain quantum computing" with model: grok-4 ``` ## Available Tools ### `search` The main search tool that provides AI-powered search capabilities. **Parameters:** - `query` (required): Search query (1-2000 characters) - `model` (optional): Model to use (default: `sonar`) - `sonar` - Fast Q&A with real-time web search (30s timeout) - `sonar-pro` - Multi-step queries with real-time web search (60s timeout, premium) - `sonar-reasoning-pro` - Chain-of-thought reasoning with real-time web search (120s timeout, premium) - `sonar-deep-research` - Exhaustive research reports with real-time web search (300s timeout, premium) - `grok-4` - Training-data knowledge, no real-time search (60s timeout, premium) - `maxTokens` (optional): Maximum response tokens (1-4000, default: 1000) - `temperature` (optional): Response randomness (0-2, default: 0.3) - `timeout` (optional): Override default timeout in milliseconds (5000-600000) **Example Response (Perplexity model):** ``` Based on current information, here are the latest developments in AI... [Detailed AI-generated response with current information] --- **Search Metadata:** - Model: perplexity/sonar - Response time: 1250ms - Tokens used: 850 - Timeout: 30000ms - Search type: realtime - Sources: 5 found ``` **Example Response (Grok 4 model):** ``` Quantum computing is a type of computation that harnesses quantum mechanics... [Response based on training data knowledge] --- **Search Metadata:** - Model: x-ai/grok-4 - Response time: 3500ms - Tokens used: 650 - Timeout: 60000ms - Search type: training-data - Cost tier: premium ``` ## Configuration ### Environment Variables - `OPENROUTER_API_KEY` (required): Your OpenRouter API key - `NODE_ENV` (optional): Environment setting (development, production, test) - `LOG_LEVEL` (optional): Logging level (debug, info, warn, error) ### Advanced Configuration The server supports additional configuration through environment variables: - `OPENROUTER_TIMEOUT_MS`: Request timeout in milliseconds (default: 30000) - `OPENROUTER_MAX_RETRIES`: Maximum retry attempts (default: 3) - `OPENROUTER_BASE_URL`: Custom OpenRouter API base URL ## Resources The server provides a configuration status resource at `config://status` that shows: - Server health status - Configuration information (with masked API key) - Search tool availability - Server uptime and version ## Troubleshooting ### Bunx/NPX-Specific Issues **"bunx: command not found"** - Install Bun: `curl -fsSL https://bun.sh/install | bash` - Or fall back to npx if you have Node.js 18+ installed **"npx: command not found"** - Ensure Node.js 18+ is installed: `node --version` - Update npm: `npm install -g npm@latest` **"Cannot find package 'nexus-mcp'"** - The package may not be published yet. Use local installation instead - Verify network connectivity for npm registry access **Slow startup on first run** - This is normal on first run as the package is downloaded - Subsequent runs will be faster due to caching - For faster startup, use local installation instead **"Permission denied" errors with npx** - Try: `npx --yes nexus-mcp --stdio` - Or set npm permissions: `npm config set user 0 && npm config set unsafe-perm true` ### Common Issues **"Search functionality is not available"** - Ensure `OPENROUTER_API_KEY` environment variable is set - Verify your API key is valid at [OpenRouter](https://openrouter.ai) - Check the server logs for initialization errors **"Authentication failed: Invalid API key"** ---

FAQ

What is the Nexus (OpenRouter Search) MCP server?
Nexus (OpenRouter Search) is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for Nexus (OpenRouter Search)?
This profile displays 55 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.7 out of 5—verify behavior in your own environment before production use.

Use Cases

Web Research & Information Gathering

Fetch and extract information from websites automatically

Example

Research competitor pricing, scrape product reviews, monitor news mentions

Automate 5-10 hours/week of manual web research

Content Monitoring & Alerts

Track website changes, new content, price updates

Example

Monitor competitor blog for new posts, track stock availability, watch for pricing changes

Stay informed without manual checking, never miss important updates

Data Extraction & Aggregation

Extract structured data from multiple websites

Example

Compile product listings from 10 e-commerce sites, aggregate job postings, collect real estate data

Build datasets 100x faster than manual copying

API-less Integration

Interact with services that don't offer APIs

Example

Check form submissions, validate website functionality, test user flows

Automate interactions with any website, even without API

Implementation Guide

Prerequisites

  • Claude Desktop or Cursor with MCP support
  • Understanding of web scraping ethics and robots.txt
  • Rate limiting awareness to avoid overwhelming target sites
  • Knowledge of legal restrictions on data collection

Time Estimate

20-40 minutes including configuration and testing

Installation Steps

  1. 1.Install web automation MCP server via npm or pip
  2. 2.Configure allowed domains and rate limits in MCP config
  3. 3.Test with simple fetch: 'Get content from example.com'
  4. 4.Progress to extraction: 'Extract all product prices from this page'
  5. 5.Set up monitoring: 'Check this URL daily for changes'
  6. 6.Parse structured data: 'Create CSV from this table'
  7. 7.Respect robots.txt and rate limits always

Troubleshooting

  • 403 Forbidden: Website blocks bots—respect their wishes, use official API instead
  • Rate limit errors: Slow down requests, add delays between fetches
  • Stale data: Target site changed HTML structure—update selectors
  • Timeout errors: Site is slow or blocking—increase timeout, try different user agent
  • JavaScript-rendered content: Use headless browser MCP servers for dynamic sites

Best Practices

✓ Do

  • +Check robots.txt and respect crawl rules
  • +Rate limit requests: 1-2 requests/second maximum
  • +Use official APIs when available instead of scraping
  • +Identify your bot with descriptive user agent
  • +Cache results to minimize repeated requests
  • +Handle errors gracefully with retries and fallbacks
  • +Validate extracted data for accuracy

✗ Don't

  • Don't scrape sites that explicitly forbid it (robots.txt, ToS)
  • Don't overwhelm servers with rapid requests—use rate limiting
  • Don't scrape personal data without consent and legal basis
  • Don't ignore copyright on extracted content
  • Don't assume HTML structure is stable—handle changes
  • Don't use scraped data for commercial purposes without permission

💡 Pro Tips

  • Use CSS selectors or XPath for robust data extraction
  • Set up monitoring alerts for extraction failures (structure changed)
  • Implement exponential backoff for retries on failures
  • Store raw HTML for reprocessing if extraction logic changes
  • Combine with data analysis tools for insights from extracted data
  • Consider using official APIs or RSS feeds as more stable alternatives

Technical Details

Architecture

MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.

Protocols

  • HTTP/HTTPS
  • WebSocket (for real-time sites)
  • Puppeteer/Playwright (for JavaScript sites)

Compatibility

  • Static HTML sites
  • JavaScript-rendered SPAs (with headless browser)
  • REST APIs
  • GraphQL endpoints

When to Use This

✓ Use When

Use for research automation, content monitoring, data aggregation from multiple sources, and when official APIs don't exist. Best for read-only information gathering.

✗ Avoid When

Avoid for sites with APIs (use API instead), sites that explicitly forbid scraping, when data is copyrighted, or for login-required content without proper authorization.

Integration

  • Scheduled monitoring with change detection
  • Multi-source data aggregation pipelines
  • Fallback to web scraping when API rate limits hit
  • Headless browser for JavaScript-heavy sites

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.

List & Promote Your MCP Server

Share your MCP server with the developer community

GET_STARTED →
MCP server reviews

Ratings

4.755 reviews
  • Soo Johnson· Dec 20, 2024

    Strong directory entry: Nexus (OpenRouter Search) surfaces stars and publisher context so we could sanity-check maintenance before adopting.

  • Mateo Shah· Dec 20, 2024

    According to our notes, Nexus (OpenRouter Search) benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.

  • Amelia Ramirez· Dec 16, 2024

    We evaluated Nexus (OpenRouter Search) against two servers with overlapping tools; this profile had the clearer scope statement.

  • Hana Li· Dec 12, 2024

    Useful MCP listing: Nexus (OpenRouter Search) is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Amelia Robinson· Nov 15, 2024

    I recommend Nexus (OpenRouter Search) for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

  • Mateo Sharma· Nov 11, 2024

    We wired Nexus (OpenRouter Search) into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

  • Soo Brown· Nov 11, 2024

    Nexus (OpenRouter Search) has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Sofia Harris· Nov 7, 2024

    Nexus (OpenRouter Search) is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.

  • Amelia Chawla· Nov 3, 2024

    Nexus (OpenRouter Search) is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Mateo Reddy· Oct 26, 2024

    Nexus (OpenRouter Search) is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

showing 1-10 of 55

1 / 6