Introduction
Nexus is the missing brain in your AI workflow.
Every time you start a new AI session, you lose context. You re-explain your project structure, remind the AI about your conventions, and watch your token budget evaporate on information you've provided a dozen times before.
Nexus fixes this. It gives your AI assistant persistent memory, instant access to up-to-date documentation, and a curated registry of MCP servers—all through a single MCP connection.
Why Nexus?
Documentation Search
Semantic search across 500+ indexed libraries. Get accurate, up-to-date code examples without hallucinations.
Persistent Memory
Your AI remembers your projects across sessions. Store decisions, conventions, and learnings.
MCP Server Registry
Discover and configure MCP servers for databases, APIs, and cloud services.
Token Efficiency
Semantic search returns only relevant chunks. Save 90%+ on context tokens.
Quick Install
Choose your deployment mode:
Remote Mode
Connect directly to the hosted Nexus service. Zero setup required.
claude mcp add nexus -- npx -y @anthropic-ai/mcp-remote https://api.nexus.yogan.dev/sseAdded MCP server nexus
Or add to your MCP configuration file:
{
"mcpServers": {
"nexus": {
"url": "https://api.nexus.yogan.dev/sse"
}
}
}Local Mode
Run Nexus locally for offline access or development.
npm install -g @nexus/clinexus serveStarting Nexus MCP server on stdio...Server ready
Then add to your MCP configuration:
{
"mcpServers": {
"nexus": {
"command": "nexus",
"args": ["serve"]
}
}
}Architecture
Nexus is a Model Context Protocol (MCP) server that provides your AI assistant with three core capabilities:
┌──────────────────────────────────────────┐
│ Your AI Client │
│ (Claude Code, Cursor, VS Code) │
└─────────────────────┬────────────────────┘
│
│ MCP Protocol
│
┌─────────────────────▼────────────────────┐
│ Nexus Server │
│ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ Docs │ │ Memory │ │ Registry │ │
│ │ Tools │ │ Tools │ │ Tools │ │
│ └────┬─────┘ └────┬─────┘ └────┬─────┘ │
│ │ │ │ │
└───────┼────────────┼────────────┼────────┘
│ │ │
┌───────────────────▼────┐ │ ┌───────▼───────────────┐
│ Documentation │ │ │ Server Registry │
│ Database │ │ │ Database │
│ │ │ │ │
│ - 500+ libraries │ │ │ - Official MCP servers│
│ - Semantic embeddings │ │ │ - Community servers │
│ - Code examples │ │ │ - Install configs │
└────────────────────────┘ │ └───────────────────────┘
│
┌────────────────▼────────────────┐
│ Memory Store │
│ │
│ - Project context │
│ - Session summaries │
│ - Architectural decisions │
│ - Lessons learned │
└─────────────────────────────────┘Token Savings
Context is expensive. Nexus uses semantic search to return only the relevant chunks instead of entire documentation pages.
Before vs After
| Without Nexus | With Nexus |
|---|---|
| Re-explain project structure every session | Load context in one tool call |
| Paste documentation into chat | AI queries docs directly |
| Search for MCP server setup guides | Get instant installation configs |
| Lose context between conversations | Persistent memory across sessions |
Available Tools
Documentation Tools
| Tool | Description |
|---|---|
resolve-library | Find library IDs for documentation queries |
query-docs | Search indexed documentation with semantic search |
get-library-info | Get detailed library metadata and stats |
list-libraries | Browse all indexed documentation |
Memory Tools
| Tool | Description |
|---|---|
save-memory | Store project context, decisions, and learnings |
recall-memories | Retrieve relevant memories using natural language |
get-project-context | Load all context for a specific project |
list-memories | Browse and manage stored memories |
update-memory | Update an existing memory |
delete-memory | Delete a memory permanently |
Server Registry Tools
| Tool | Description |
|---|---|
discover-servers | Find MCP servers by capability or category |
get-server-info | Get detailed server documentation |
get-server-config | Generate ready-to-use MCP configurations |