Hindsight vs Scrivener MCP
A side-by-side look at the Hindsight and Scrivener MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Hindsight for knowledge & memory work as a local process; choose Scrivener 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?
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.
Choose Scrivener MCP 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 57/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Free | Free |
| Required env vars | HINDSIGHT_API_LLM_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 51,891 | 67 |
| Directory activity | 13 views 0 installs 0 upvotes | 20 views 12 installs 6 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Hindsight | View Scrivener MCP |
Tools & capabilities
Hindsight tools
No tool names declared yet. Check the project README from the listing page.
Scrivener 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.
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"
}
}
}
}
Scrivener MCP
{
"mcpServers": {
"writerslogic-scrivener-mcp": {
"command": "npx",
"args": [
"scrivener-mcp"
]
}
}
}
Frequently asked questions
Hindsight is categorized under Knowledge & Memory and uses a local stdio subprocess. Scrivener MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Hindsight for knowledge & memory work and Scrivener 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.
Hindsight is listed as free. Auth: api key required. Scrivener MCP 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 vectorize-io-hindsight and writerslogic-scrivener-mcp 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 13 views, 0 installs and 51,891 GitHub stars. Scrivener MCP has 61/100 (Good) with 20 views, 12 installs and 67 GitHub stars.