A side-by-side look at the MCP Memory Gateway and MisakaNet MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Memory Gateway for knowledge & memory work as a local process; choose MisakaNet 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?
Choose MCP Memory Gateway when
You need dedicated capabilities in the Knowledge & Memory domain.
No tool names declared yet. Check the project README from the listing page.
MisakaNet 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.
MCP Memory Gateway is categorized under Knowledge & Memory and uses a local stdio subprocess. MisakaNet belongs to Knowledge & Memory and uses a local stdio subprocess. Pick MCP Memory Gateway for knowledge & memory work and MisakaNet 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.
MCP Memory Gateway is listed as free. Auth: no auth required. MisakaNet 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 igorganapolsky-mcp-memory-gateway and ikalus1988-misakanet as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Memory Gateway has a quality signal of 60/100 (Good) with 5 views, 0 installs and 29 GitHub stars. MisakaNet has 64/100 (Good) with 4 views, 0 installs and 544 GitHub stars.