Cognicore Env vs Memstate MCP
A side-by-side look at the Cognicore Env and Memstate MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
Cognicore EnvKnowledge & Memory · Local subprocess (stdio)Persistent memory, reflection & safety for AI agents. Zero dependencies — no vector DB, no embedding server. BM25 + multi-hop graph retrieval. MCP server with 10 tools.48FairAuth: no auth requiredVerdict: choose Cognicore Env for knowledge & memory work as a local process; choose Memstate MCP 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?
CChoose Cognicore Env when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Memstate MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
MEMSTATE_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Cognicore Env | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 48/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | BYOK (pay the provider) |
| Required env vars | None listed | MEMSTATE_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 77 | 8 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Cognicore Env | View Memstate MCP |
Tools & capabilities
Cognicore Env tools
No tool names declared yet. Check the project README from the listing page.
Memstate MCP 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.
Cognicore Env
{
"mcpServers": {
"cognicore-env": {
"command": "uvx",
"args": [
"cognicore-env"
]
}
}
}
Memstate MCP
{
"mcpServers": {
"memstate-ai-memstate-mcp": {
"command": "npx",
"args": [
"-y",
"@memstate/mcp"
],
"env": {
"MEMSTATE_API_KEY": "YOUR_MEMSTATE_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Cognicore Env is categorized under Knowledge & Memory and uses a local stdio subprocess. Memstate MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Cognicore Env for knowledge & memory work and Memstate MCP 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.
Cognicore Env is listed as free. Auth: no auth required. Memstate MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. 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 cognicore-env and memstate-ai-memstate-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cognicore Env has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 77 GitHub stars. Memstate MCP has 49/100 (Fair) with 2 views, 0 installs and 8 GitHub stars.