nexusm-mcp-server
The nexusm-mcp-server exposes Nexusm's core AI memory and context capabilities to MCP clients, enabling persistent, searchable, and feedback-driven memory management across sessions.
Retrieve Context (
nexus.context_retrieve): Unified context lookup returning relevant memories, recent conversation turns, and knowledge entities in a single call — ideal for open-ended queries needing full session context. Supports time-anchored retrieval via anas_oftimestamp (up to 90 days in the past).Search Memories (
nexus.memory_search): Targeted semantic or hybrid (vector + trigram) search over stored memories, with optional filtering by memory type (episodic,semantic,procedural) and relevance score threshold. Hybrid mode provides better results for CJK/keyword queries.Create Memories (
nexus.memory_create): Persist new memories with typed categories (episodicfor events,semanticfor facts,proceduralfor how-tos), optional metadata tags, and temporal validity (valid_until).Submit Retrieval Feedback (
nexus.memory_feedback): Rate a previouscontext_retrievecall (1–5 stars), flag individual memories as useful or not (with optional reasons), and note any missing expected memories — feeding a quality-score reranking loop to improve future retrievals.
Exposes Prometheus metrics for monitoring the MCP server's performance and usage, including cardinality guards.
Click on "Install 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., "@nexusm-mcp-serversearch memory for recent conversations about Q3 planning"
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.
nexusm-mcp-server
Nexusm MCP Server — generic MCP server exposing Nexusm core capabilities (memory, conversation, knowledge, feedback, context) to MCP clients via @modelcontextprotocol/sdk stdio + Streamable HTTP transports.
Published to npm as @nexusm/mcp-server.
Tracked in Nexusm main repo:
packages/nexusm-mcp-server(US-037 v7.0).
Configuration
Set via environment (e.g. the env block of your client's .mcp.json):
Env var | Required | Purpose |
| yes | Base URL of the Nexus REST API. The server auto-appends |
| yes | Nexus API key (the product auth contract) |
| yes | Tenant id for the compound-id isolation |
| no | Single-user pin. When set to a non-empty value, the server uses it as |
| no | Opt-in Prometheus |
The Nexus API auth contract is
NEXUS_API_TOKEN. Any deployment-edge access control in front of the API (e.g. a reverse proxy / gateway / Cloudflare Access) is not this client's concern — handle it transparently at the network/transport layer (pointNEXUS_API_URLat a local proxy) so the client stays deployment-agnostic. When pointing at a local proxy, setNEXUS_API_URLto the proxy origin (e.g.http://localhost:8787); the server will append/v1automatically and log a one-line diagnostic to stderr confirming the normalization.
Related MCP server: @modusop/mcp-server
Status
Wave 2 done (2026-05-22): 4 tools fully wired to @nexusm/sdk (context_retrieve / memory_search / memory_create / memory_feedback) + full §M-3 HTTP→MCP error mapping (mapHttpStatusToMcpError + 2 new error codes Unauthorized/RateLimited) + Prometheus metrics with cardinality guard + cross-substory + E2E + schema_sync integration tests. Wave 3 (nexus-claude-plugin Anthropic marketplace) pending — see proposal.
Known Wave 2 limitations: (1) CI red until Gate-1 — @nexusm/sdk@1.3.0 npm publish pending (user action; SDK rename merged at 1fbdd69 in nexus-sdk-js main); (2) integration tests env-gated (require NEXUS_TEST_API_URL/TOKEN/TENANT_ID Forgejo secrets, currently dormant); (3) Python backend mcp.py metrics defined but emit-site wiring deferred to Wave 3 (FU-MCP-BACKEND-EMIT-WIRING); (4) HTTP transport per-request server.connect() is scaffold-only — Wave 3 entry condition (FU-MCP-HTTP-SESSION) before plugin TASK-019 E2E runs.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that wraps the nexus CLI, giving AI agents cross-session memory, semantic search, preference learning, and smart context injection.3,394MIT
- AlicenseNot gradedqualityCmaintenanceActs as a stdio-to-HTTP proxy for Modus Brain, enabling MCP-compatible AI clients to access an organization's knowledge base in ModusOp.37Cryptographic Autonomy 1.0 (Combined Work Exception)
- AlicenseNot gradedqualityBmaintenanceMCP server for the Synapse ecosystem that exposes the Synapse Memory API, Browser Proxy, and SSH Proxy as MCP tools, enabling multi-tenant, stateful interactions via stdio or HTTP/SSE.571MIT
- FlicenseNot gradedqualityBmaintenanceModel Context Protocol server for MCPGRAM that enables MCP clients to interact with connectors like GitHub, Slack, and Notion through stdio or Streamable HTTP transports.
Related MCP Connectors
Personal assistant MCP server with search, execute, packages, jobs, secrets, and integrations.
The official MCP Server from Mia-Platform to interact with Mia-Platform Console
AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/10CG/nexusm-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server