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