What is the key difference between Memxus Remote MCP and Memory Nexus MCP?

Memxus Remote MCP belongs to the Knowledge & Memory category with cloud HTTP/SSE execution, while Memory Nexus MCP belongs to the Knowledge & Memory category with local stdio execution.

How do I install Memxus Remote MCP or Memory Nexus MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Memxus Remote MCP and Memory Nexus MCP free or paid?

Memxus Remote MCP operates under a Free / Open Source model (No auth required). Memory Nexus MCP operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Memxus Remote MCP lists 13 tools with 1 views and 3 GitHub stars. Memory Nexus MCP lists 10 tools with 1 views and 0 GitHub stars.

Can I use both Memxus Remote MCP and Memory Nexus MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Memxus Remote MCP vs Memory Nexus MCP

In-depth architectural comparison of the Memxus Remote MCP and Memory Nexus MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Memxus Remote MCP

Knowledge & Memory · Remote HTTP/SSE

Quality: 57/100 (Good) | Auth: No auth required

Memory Nexus MCP

Knowledge & Memory · Local stdio

Quality: 49/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Memxus Remote MCP if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose Memory Nexus MCP if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Memxus Remote MCP when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: remember, recall, get_context.

Explore Memxus Remote MCP Details

Choose Memory Nexus MCP when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: remember, recall, connect.

Explore Memory Nexus MCP Details

Feature & Specification Comparison

Specification	Memxus Remote MCP gpitrella Knowledge & Memory	Memory Nexus MCP Knowledge & Memory
Summary	Shared context engine for devs and teams. Syncs GitHub, Notion, and saved decisions into reusable project context, so Claude, ChatGPT, Cursor, VS Code and Gemini start each session with the architecture and decisions the team already made. OAuth 2.1 PKCE, AES-256 encrypted, RFC 9728 compliant. https://mcp.memxus.com/mcp	Persistent semantic memory for AI agents with knowledge graphs and Intelligence Packs.
Category & Scope

Tools & Capabilities Breakdown

Memxus Remote MCP Tools (13)

remember

Save context — manual input, decisions, or notes; optional `project:<slug>` collection

recall

Semantic search across memories; GitHub/Notion synced content via `project:<slug>` or tags

get_context

Formatted context block from GitHub, Notion, and saved decisions for agent prompts

list_memories

Browse memories by collection, tags, type, or visibility

get_memory

Retrieve full content and metadata by memory ID

list_collections

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Memxus Remote MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "gpitrella-memxus-remote-mcp": {
      "url": "https://mcp.memxus.com/mcp"
    }
  }
}

Memory Nexus MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "memory-nexus-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@memory-nexus/mcp"
      ]
    }
  }
}

Frequently Asked Questions

Memxus Remote MCP is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Memory Nexus MCP belongs to Knowledge & Memory using local stdio subprocess. Select Memxus Remote MCP when you need capabilities focused on knowledge & memory and Memory Nexus MCP when you require tools for knowledge & memory.

More alternatives to Memxus Remote MCP More alternatives to Memory Nexus MCP Knowledge & Memory category hub