A side-by-side look at the Agentkits Memory and Codemem MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agentkits Memory for knowledge & memory work as a local process; choose Codemem 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 Agentkits Memory when
You need dedicated capabilities in the Knowledge & Memory domain.
No tool names declared yet. Check the project README from the listing page.
Codemem 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.
Agentkits Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. Codemem belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Agentkits Memory for knowledge & memory work and Codemem 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.
Agentkits Memory is listed as free. Auth: no auth required. Codemem has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 aitytech-agentkits-memory and kunickiaj-codemem as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agentkits Memory has a quality signal of 52/100 (Good) with 4 views, 0 installs and 3 GitHub stars. Codemem has 59/100 (Good) with 0 views, 0 installs and 73 GitHub stars.