WorkingMemory vs Scrivener MCP
A side-by-side look at the WorkingMemory and Scrivener MCP 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 WorkingMemory for knowledge & memory work over a hosted endpoint; 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?
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.
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 | W WorkingMemory | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 39/100 · Fair | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 68 |
| Directory activity | 1 views 0 installs 0 upvotes | 20 views 12 installs 6 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View WorkingMemory | View Scrivener MCP |
Tools & capabilities
WorkingMemory 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.
WorkingMemory
{
"mcpServers": {
"workingmemory": {
"command": "npx",
"args": [
"-y",
"workingmemory"
]
}
}
}
Scrivener MCP
{
"mcpServers": {
"writerslogic-scrivener-mcp": {
"command": "npx",
"args": [
"scrivener-mcp"
]
}
}
}
Frequently asked questions
WorkingMemory is categorized under Knowledge & Memory and uses a remote HTTP/SSE transport. Scrivener MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick WorkingMemory 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.
WorkingMemory has no declared pricing — check the project's own site. Auth: no auth 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 workingmemory and writerslogic-scrivener-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, WorkingMemory has a quality signal of 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Scrivener MCP has 65/100 (Great) with 20 views, 12 installs and 68 GitHub stars.