Hindsight vs WorkingMemory
A side-by-side look at the Hindsight and WorkingMemory MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
W
WorkingMemoryKnowledge & Memory · Remote HTTP/SSEPersistent personal memory for AI assistants — save, search, and recall across every MCP client.39FairAuth: no auth requiredVerdict: choose Hindsight for knowledge & memory work as a local process; choose WorkingMemory for knowledge & memory over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Hindsight 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:
HINDSIGHT_API_LLM_API_KEY, HINDSIGHT_API_LLM_PROVIDER, HINDSIGHT_DB_PASSWORD.
WChoose WorkingMemory when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | W WorkingMemory | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 57/100 · Good | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | No auth required |
| Pricing | Free | Not declared |
| Required env vars | HINDSIGHT_API_LLM_API_KEYHINDSIGHT_API_LLM_PROVIDERHINDSIGHT_DB_PASSWORD | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 53,323 | — |
| Directory activity | 14 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Hindsight | View WorkingMemory |
Tools & capabilities
Hindsight tools
No tool names declared yet. Check the project README from the listing page.
WorkingMemory 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.
Hindsight
{
"mcpServers": {
"vectorize-io-hindsight": {
"command": "npx",
"args": [
"-y",
"@vectorize-io/hindsight-coding-agents"
],
"env": {
"HINDSIGHT_API_LLM_API_KEY": "YOUR_HINDSIGHT_API_LLM_API_KEY_HERE",
"HINDSIGHT_API_LLM_PROVIDER": "YOUR_HINDSIGHT_API_LLM_PROVIDER_HERE",
"HINDSIGHT_DB_PASSWORD": "YOUR_HINDSIGHT_DB_PASSWORD_HERE"
}
}
}
}
WorkingMemory
{
"mcpServers": {
"workingmemory": {
"command": "npx",
"args": [
"-y",
"workingmemory"
]
}
}
}
Frequently asked questions
Hindsight is categorized under Knowledge & Memory and uses a local stdio subprocess. WorkingMemory belongs to Knowledge & Memory and uses a remote HTTP/SSE transport. Pick Hindsight for knowledge & memory work and WorkingMemory 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.
Hindsight is listed as free. Auth: api key required. WorkingMemory has no declared pricing — check the project's own site. 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 vectorize-io-hindsight and workingmemory as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Hindsight has a quality signal of 57/100 (Good) with 14 views, 0 installs and 53,323 GitHub stars. WorkingMemory has 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.