What is the key difference between Cuba Memorys and JustOnce?

Cuba Memorys belongs to the Knowledge & Memory category with local stdio execution, while JustOnce belongs to the Knowledge & Memory category with cloud HTTP/SSE execution.

How do I install Cuba Memorys or JustOnce 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 Cuba Memorys and JustOnce free or paid?

Cuba Memorys operates under a Free / Open Source model (No auth required). JustOnce operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Cuba Memorys lists 0 tools with 2 views and 26 GitHub stars. JustOnce lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Cuba Memorys and JustOnce 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

Cuba Memorys vs JustOnce

In-depth architectural comparison of the Cuba Memorys and JustOnce 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

Cuba Memorys

Knowledge & Memory · Local stdio

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

JustOnce

Knowledge & Memory · Remote HTTP/SSE

Quality: 30/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Cuba Memorys if you need specialized Knowledge & Memory tools running via a local process. Choose JustOnce if your workspace requires Knowledge & Memory integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Cuba Memorys 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).

Explore Cuba Memorys Details

Choose JustOnce 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).

Explore JustOnce Details

Feature & Specification Comparison

Specification	Cuba Memorys Knowledge & Memory	J JustOnce Knowledge & Memory
Summary	Persistent memory MCP server. 25 tools, BM25+MMR+OOD retrieval, CFR-21 audit, knowledge graph.	Persistent memory for AI assistants — one shared, OAuth-secured vault for every MCP client.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

Cuba Memorys Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

JustOnce Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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).

Cuba Memorys Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "cuba-memorys": {
      "command": "uvx",
      "args": [
        "cuba-memorys"
      ]
    }
  }
}

JustOnce Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "justonce": {
      "url": "https://justonce.ai"
    }
  }
}

Frequently Asked Questions

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

More alternatives to Cuba Memorys More alternatives to JustOnce Knowledge & Memory category hub