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