A side-by-side look at the MaxGraph and Cuba Memorys MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MaxGraph for knowledge & memory work over a hosted endpoint; choose Cuba Memorys for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
M
Choose MaxGraph when
You need dedicated capabilities in the Knowledge & Memory domain.
No tool names declared yet. Check the project README from the listing page.
Cuba Memorys tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MaxGraph is categorized under Knowledge & Memory and uses a remote HTTP/SSE transport. Cuba Memorys belongs to Knowledge & Memory and uses a local stdio subprocess. Pick MaxGraph for knowledge & memory work and Cuba Memorys for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MaxGraph has no declared pricing — check the project's own site. Cuba Memorys is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add maxgraph and cuba-memorys as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MaxGraph has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. Cuba Memorys has 48/100 (Fair) with 3 views, 0 installs and 29 GitHub stars.