Memors vs Mindpm
A side-by-side look at the Memors and Mindpm MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
MemorsDatabasesLocal, explainable knowledge base for AI agents: hybrid search with provenance over SQLite.36FairAuth: no auth requiredVerdict: choose Memors for databases work; choose Mindpm for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
MChoose Memors when
- You need dedicated capabilities in the Databases domain.
- Its auth model fits you: No auth required.
- You have the keys it needs:
MEMORS_HOME, MEMORS_KB.
Choose Mindpm when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MINDPM_DB_PATH. - You want tools like
create_project, list_projects, get_project_status.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M Memors | |
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 36/100 · Fair | 56/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | MEMORS_HOMEMEMORS_KB | MINDPM_DB_PATH |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 9 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 22 |
| Full listing | View Memors | View Mindpm |
Tools & capabilities
Memors tools
No tool names declared yet. Check the project README from the listing page.
Mindpm tools 22
create_projectCreate a new projectlist_projectsList all projectsget_project_statusFull project overviewset_project_repo_pathSet/update the project's local git repo path (enables the session brief's git delta)create_taskAdd a taskupdate_taskUpdate status, priority, etc.list_tasksList with filtersget_taskFull task detail with sub-tasks and notesget_next_tasksSmart: highest priority, unblockedlog_decisionRecord a decision with reasoninglist_decisionsBrowse decision historyadd_noteAdd a note (architecture, bug, idea, etc.)- +10 more on 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.
Memors
No confirmed install command for Memors yet — follow the setup steps linked from its listing page rather than a guessed package name.
Mindpm
{
"mcpServers": {
"mindpm": {
"command": "npx",
"args": [
"-y",
"mindpm"
],
"env": {
"MINDPM_DB_PATH": "YOUR_MINDPM_DB_PATH_HERE"
}
}
}
}
Frequently asked questions
Memors is categorized under Databases and uses an install path we have not confirmed yet. Mindpm belongs to Databases and uses a local stdio subprocess. Pick Memors for databases work and Mindpm for databases.
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. Memors has no confirmed install command yet — follow its own setup instructions.
Memors is listed as free. Auth: no auth required. Mindpm has no declared pricing — check the project's own site. 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 memors and mindpm as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Memors has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Mindpm has 56/100 (Good) with 2 views, 0 installs and 9 GitHub stars.