Nexus MCP Server
# ๐ Nexus MCP Server
> **The Hybrid Search & Retrieval Engine for AI Agents.**
Nexus is a local Model Context Protocol (MCP) server that combines the best features of **Exa** (semantic web search) and **Ref** (documentation-optimized reading). It provides your AI agent (Claude, Cursor, etc.) with the ability to search the web and extract surgical, token-efficient context from documentation without requiring external API keys.
## โจ Features
### 1. Hybrid Search (`nexus_search`)
Nexus understands that searching for news is different from searching for API docs.
* **General Mode:** Performs broad web searches (like Exa) to find articles, news, and general information.
* **Docs Mode:** Automatically filters results to prioritize technical domains (`readthedocs`, `github`, `stackoverflow`, official documentation).
### 2. Intelligent Reading (`nexus_read`)
Nexus doesn't just dump HTML into your context window. It parses content based on intent.
* **General Focus:** Cleans articles, removing ads, navigation bars, and fluff. Perfect for reading news or blog posts.
* **Code Focus:** Aggressively strips conversational text, retaining only **Headers**, **Code Blocks**, and **Tables**. This mimics `ref.tools`, ensuring your model gets pure syntax without the noise.
* **Auto-Detect:** Automatically switches to "Code Focus" when visiting technical sites like GitHub or API references.
### 3. Privacy & Cost
* **No API Keys Required:** Uses DuckDuckGo for search and standard HTTP requests for retrieval.
* **Runs Locally:** Your data stays on your machine until the cleaned context is sent to the LLM.
---
## ๐ ๏ธ Installation
### Prerequisites
* Python 3.10+
### Quick Install
**Option 1: Using pip (Simplest - Works Everywhere)**
```bash
# Install directly from GitHub
pip install git+https://github.com/rcdelacruz/nexus-mcp.git
```
**Option 2: Using uvx (Faster, Isolated)**
First install `uv` if you don't have it:
```bash
# On macOS/Linux
curl -LsSf https://astral.sh/uv/install.sh | sh
# On Windows
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"
```
Then use uvx (no separate installation needed):
```bash
uvx --from git+https://github.com/rcdelacruz/nexus-mcp.git nexus-mcp
```
### Development Install
**For local development or contributing:**
1. Clone the repository:
```bash
git clone https://github.com/rcdelacruz/nexus-mcp.git
cd nexus-mcp
```
2. Install in development mode:
```bash
# Create virtual environment
python3 -m venv .venv
source .venv/bin/activate # On Windows: .venv\Scripts\activate
# Install the package in editable mode
pip install -e .
```
3. For development with testing tools:
```bash
pip install -e ".[dev]"
```
---
## โ๏ธ Configuration
### Claude Code (CLI)
**Option 1: Using pip (Simplest)**
```bash
# First install the package
pip install git+https://github.com/rcdelacruz/nexus-mcp.git
# Add the server globally (available in all projects)
claude mcp add nexus --transport stdio --scope user -- nexus-mcp
# Verify installation
claude mcp list # Should show: โ Connected
```
**Option 2: Using uvx (Requires uv installation)**
Make sure you have `uv` installed first (see Installation section above), then:
```bash
# Add the server globally (available in all projects)
claude mcp add nexus --transport stdio --scope user -- \
uvx --from git+https://github.com/rcdelacruz/nexus-mcp.git nexus-mcp
# Verify installation
claude mcp list # Should show: โ Connected
```
**Option 3: Local Development Setup**
If you cloned the repository for development:
```bash
# Navigate to nexus-mcp directory
cd /path/to/nexus-mcp
# Install dependencies first
python3 -m venv .venv
source .venv/bin/activate
pip install -e .
# Add the server to Claude Code (project scope)
claude mcp add nexus --scope project -- \
$(pwd)/.venv/bin/python $(pwd)/nexus_server.py
# Verify installation
claude mcp list
```
**Configuration Scopes:**
- `--scope user` - Available across all projects (recommended for GitHub install)
- `--scope project` - Creates `.mcp.json` (shareable via git)
- `--scope local` - Personal config in `~/.claude.json`
**Check server status:**
```bash
claude mcp list # Should show: nexus - โ Connected
/mcp # In conversation: shows available tools
```
---
### Claude Desktop / Cursor
**Config Location:**
* **MacOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`
* **Windows:** `%APPDATA%\Claude\claude_desktop_config.json`
**Option 1: Using pip (Simplest)**
First install: `pip install git+https://github.com/rcdelacruz/nexus-mcp.git`
Then add to config:
```json
{
"mcpServers": {
"nexus": {
"command": "nexus-mcp"
}
}
}
```
**Option 2: Using uvx (Requires uv installed)**
Make sure `uv` is installed first (see Installation section), then add to config:
```json
{
"mcpServers": {
"nexus": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/rcdelacruz/nexus-mcp.git",
"nexus-mcp"
]
}
}
}
```
**For local development:**
If you cloned the repo and installed with `pip install -e .`:
```json
{
"mcpServers": {
"nexus": {
"command": "/ABSOLUTE/PATH/TO/.venv/bin/python",
"args": ["/ABSOLUTE/PATH/TO/nexus_server.py"]
}
}
}
```
*Replace `/ABSOLUTE/PATH/TO/` with the actual path to your clone.*
---
## ๐ Usage
Once connected, simply prompt Claude naturally. Nexus handles the tool selection.
### Verify It's Working
Check server connection:
```bash
claude mcp list
# Should show: nexus - โ Connected
# In a Claude Code conversation:
/mcp
# Should show nexus with 2 tools available
```
See [VERIFICATION.md](VERIFICATION.md) for detailed testing instructions.
### Scenario 1: Technical Research (Ref Emulation)
> **User:** "How do I use `asyncio.gather` in Python? Check the docs."
* **Nexus Action:**
1. Search: `nexus_search(query="python asyncio gather", mode="docs")`
2. Read: `nexus_read(url="docs.python.org/...", focus="code")`
* **Result:** The AI receives only the function signature and code examples, saving context window space.
### Scenario 2: General Research (Exa Emulation)
> **User:** "Search for the latest updates on the NVIDIA Blackwell chip."
* **Nexus Action:**
1. Search: `nexus_search(query="NVIDIA Blackwell updates", mode="general")`
2. Read: `nexus_read(url="techcrunch.com/...", focus="general")`
* **Result:** The AI reads a clean, ad-free summary of the news article.
---
## ๐ง Architecture
Nexus is built on the [Model Context Protocol](https://modelcontextprotocol.io/) using the FastMCP Python SDK.
| Component | Technology | Purpose |
| :--- | :--- | :--- |
| **MCP Framework** | `FastMCP` | Server implementation and tool registration |
| **Search Backend** | `DDGS` (DuckDuckGo) | Free web search without API keys |
| **HTTP Client** | `httpx` | Async HTTP requests with timeout handling |
| **HTML Parsing** | `BeautifulSoup4` | Intelligent content extraction |
| **Doc Detection** | Heuristic URL matching | Auto-detection of technical sites |
### Production Features
โ
**Comprehensive Error Handling** - All edge cases covered with graceful fallbacks
โ
**Input Validation** - URL format, parameter bounds, and mode validation
โ
**Proper Logging** - Structured logging instead of print statements
โ
**Configurable Limits** - Timeouts, content length, and result counts
โ
**85% Test Coverage** - 19 comprehensive unit tests
โ
**Type Hints** - Full type annotations for better IDE support
โ
**Dependency Management** - Modern pyproject.toml configuration
---
## ๐งช Testing
Run the test suite:
```bash
# Activate virtual environment
source .venv/bin/activate
# Run all tests with coverage
pytest
# Run specific test file
pytest tests/test_nexus_server.py -v
# Run manual integration test
python test_manual.py
```
---
## ๐ Project Structure
```
nexus-mcp/
โโโ nexus_server.py # Main MCP server implementation
โโโ tests/ # Comprehensive test suite
โ โโโ __init__.py
โ โโโ test_nexus_server.py
โโโ test_manual.py # Manual integration testing
โโโ pyproject.toml # Project configuration & dependencies
โโโ LICENSE # MIT License
โโโ README.md # This file
โโโ .gitignore # Git ignore rules
```
---
## ๐ค Contributing
Contributions are welcome! Please ensure:
- All tests pass (`pytest`)
- Code coverage remains above 80%
- Follow existing code style and patterns
- Add tests for new features
---
## ๐ License
MIT License - See [LICENSE](LICENSE) file for details. Free to use and modify.
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: 'nexus_read' fetches and parses content from a specific URL, while 'nexus_search' performs web searches based on a query. There is no overlap in functionality, and an agent can easily differentiate between them based on whether it needs to retrieve known content or discover new information.
Both tools follow a consistent 'nexus_verb' naming pattern, using snake_case throughout. The verbs 'read' and 'search' are distinct and accurately describe their respective actions, creating a predictable and readable naming convention across the tool set.
With only two tools, the server feels under-scoped for its apparent purpose of intelligent web content retrieval and search. This minimal set may limit agents' ability to perform more complex workflows, such as saving, organizing, or analyzing retrieved content, making it borderline too thin for practical use.
The tools cover basic retrieval (read) and discovery (search) functions, but there are notable gaps. For example, there is no tool for managing or storing fetched content, no way to interact with search results beyond viewing them, and no update or deletion capabilities, which could hinder agents in more advanced tasks.