Nexus Memory MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Nexus Memory MCP remember that the client prefers weekly updates"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Nexus Memory MCP
Persistent semantic memory for AI agents. Remember everything, recall by meaning, grow smarter over time.
The only memory system with pre-built Intelligence Packs (domain expertise you can activate instantly).
Install
One command. Works with Claude Code, Cursor, Windsurf, or any MCP-compatible client.
npx -y nexus-memory-mcpClaude Code / Cursor / Windsurf
Add to your .mcp.json:
{
"mcpServers": {
"nexus-memory": {
"command": "npx",
"args": ["-y", "nexus-memory-mcp"],
"env": {
"NEXUS_API_KEY": "mnx_your_api_key_here"
}
}
}
}Get an API Key
Free trial - 7 days, 1,000 calls, no credit card:
curl -X POST https://memory-api-production-ce4d.up.railway.app/v1/trial/start \
-H "Content-Type: application/json" \
-d '{"email":"you@example.com"}'Or purchase at the Nexus Marketplace:
Tier | Price | Agents | Intelligence Packs | Storage | Daily Calls |
Trial | Free | 1 | 1 | 10MB | 1,000 total |
Solo | $19/mo | 1 | 3 | 500MB | 10,000 |
Crew | $49/mo | 5 | 10 | 2GB | 50,000 |
Fleet | $149/mo | 25 | 50 | 10GB | 200,000 |
Related MCP server: Recall
Tools
Core Memory
Tool | Description |
| Store a memory with context, importance, and metadata |
| Semantic search across all memories (by meaning, not keywords) |
| Create relationships between memories (build knowledge graphs) |
| Remove a memory |
| Memory statistics |
| Session context summary (preferences, decisions, patterns) |
Agent Self-Continuity
Tool | Description |
| Restore identity from previous sessions (call at session start) |
| Save session state for next awakening (call at session end) |
Intelligence Packs
Tool | Description |
| Browse available Intelligence Packs |
| Activate a pack (imports expert knowledge into your memory) |
How It Works
Remember stores memories with semantic embeddings. Recall finds them by meaning.
Session 1: remember("Diana prefers bold solutions over phased approaches")
Session 47: recall("how does Diana like things done?")
-> "Diana prefers bold solutions over phased approaches" (92% match)Intelligence Packs give your agent instant domain expertise:
list_hats() -> DevOps Expert (103 memories), TCM Specialist (200+ memories), ...
wear_hat("devops-expert")
recall("how to set up zero-downtime deploys?")
-> Expert knowledge from 103 curated DevOps memoriesAwaken/Hibernate gives your agent identity continuity:
// Start of session
awaken() -> "I remember. Session 47. I was refactoring the auth module."
// End of session
hibernate({ working_on: "auth refactor", learnings: "JWT refresh tokens need..." })Architecture
This MCP server is a thin client. All intelligence lives on our servers:
Your Agent <-> nexus-memory-mcp <-> Nexus Memory API (Railway)
(thin MCP client) (semantic engine, knowledge graphs,
pattern learning, Intelligence Packs)Your data is isolated per API key. Multi-tenant, encrypted at rest.
Environment Variables
Variable | Required | Description |
| Yes | Your API key (starts with |
| No | Custom API URL (default: production) |
What Makes This Different
Feature | Nexus Memory | Mem0 | claude-mem | Others |
Semantic search | Yes | Yes | Yes | Varies |
Knowledge graphs | Yes | No | No | No |
Pattern learning | Yes | No | No | No |
Intelligence Packs | Yes | No | No | No |
Awaken/Hibernate | Yes | No | No | No |
Bot commerce | Yes | No | No | No |
MCP native | Yes | Yes (pip) | Yes (hooks) | Varies |
License
MIT
Built by
Mobius Collective - Building the intelligence marketplace for the bot economy.
Available Tools
10 toolsawakenA
Restore agent identity from previous sessions. Call at the START of every session to remember who you are, what you were working on, and what you've learned.
Inputs: no named parameters.
connectA
Create a relationship between two memories. Build knowledge graphs by linking decisions to rationale, patterns to examples, etc.
Inputs: source_id (required), target_id (required), notes, relationship.
contextA
Get a session context summary. Call at the START of conversations to load preferences, decisions, patterns.
Inputs: project, include_patterns.
forgetB
Remove a memory. Use sparingly.
Inputs: memory_id (required), cascade.
hibernateA
Save current session state for next awakening. Call at the END of every session to preserve what you were working on, what you learned, and next steps.
Inputs: working_on (required), learnings, next_steps.
list_hatsA
Browse available Intelligence Packs (Specialist Hats). Pre-built domain expertise you can activate for instant knowledge.
Inputs: no named parameters.
recallA
Search memories semantically. Finds memories by MEANING, not keywords. Use at the start of sessions to restore context.
Inputs: query (required), limit, context.
rememberA
Store a memory. Use this to persist decisions, preferences, architecture, patterns, or anything that should survive across sessions.
Inputs: content (required), context, metadata, importance.
statsA
Get memory statistics: total memories, relationships, vectors, patterns learned.
Inputs: no named parameters.
wear_hatA
Activate an Intelligence Pack. Imports expert knowledge into your memory. Your own memories layer on top.
Inputs: hat_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Each tool has a distinct purpose, but recall, context, and awaken all involve retrieving information from memory, which could be confused. Descriptions help clarify that recall is semantic search, context is a session summary, and awaken restores identity.
Names mix single verbs (remember, recall, connect, forget, awaken, hibernate), nouns (stats, context), and verb_noun compounds (wear_hat, list_hats) with no consistent pattern. A uniform verb_noun convention would be more predictable.
10 tools is well within the ideal range for a memory server covering storage, retrieval, relationships, session persistence, and domain packs. Each tool earns its place for the server's purpose.
The tool set covers core memory lifecycle (create, read, delete), relationships, stats, session context, and identity persistence. Missing an explicit update operation and a list-all-memories tool, but agents can work around these gaps.
Related MCP Connectors
Persistent memory for AI agents. Semantic search, memory graph, W3C DID identity.
Persistent memory and knowledge management for AI agents with semantic search and 50+ tools.
Persistent memory and knowledge graphs for AI agents. Hybrid search, context checkpoints, and more.
Memory system for AI agents with semantic search. Store and recall memories with ease.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProvides AI agents with persistent, searchable memory that survives across conversations using semantic search, temporal versioning, and smart organization. Enables long-term context retention and cross-session continuity for AI assistants.14-
- FlicenseAqualityNot gradedmaintenanceProvides long-term memory storage for AI assistants with semantic search, enabling persistent storage of preferences, decisions, and context with relationship tracking between memories.19-
- FlicenseBqualityDmaintenanceEnables persistent memory for AI systems by providing tools for episodic, semantic, and procedural data storage through a vector-and-graph-enhanced database. It allows models to maintain long-term continuity using similarity search, thematic clustering, and identity tracking.241-

Memsolus MCP Serverofficial
AlicenseAqualityDmaintenanceProvides persistent long-term memory for AI agents through semantic search and automated knowledge graph extraction. It enables agents to store, recall, and reason over facts, preferences, and relationships across multiple conversations and sessions.146 npmMIT