Memory Find vs Obsidian Semantic Search
A side-by-side look at the Memory Find and Obsidian Semantic Search MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
Memory FindDatabasesLocal, explainable knowledge base for AI agents: hybrid search with provenance over SQLite.36FairAuth: no auth requiredVerdict: choose Memory Find for databases work; choose Obsidian Semantic Search 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 Memory Find 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 Obsidian Semantic Search when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OBSIDIAN_VAULT_ROOT. - You want tools like
index_status, index_vault, search_notes.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M Memory Find | |
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 36/100 · Fair | 52/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 | OBSIDIAN_VAULT_ROOT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 4 |
| Full listing | View Memory Find | View Obsidian Semantic Search |
Tools & capabilities
Memory Find tools
No tool names declared yet. Check the project README from the listing page.
Obsidian Semantic Search tools 4
index_statusReturns index metadata and safety settings.index_vaultBuilds or updates the external SQLite index.search_notesSearches notes with hybrid semantic and keyword ranking.read_noteReads a note or line range by vault-relative path.
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.
Memory Find
No confirmed install command for Memory Find yet — follow the setup steps linked from its listing page rather than a guessed package name.
Obsidian Semantic Search
{
"mcpServers": {
"obsidian-semantic-search": {
"command": "npx",
"args": [
"-y",
"--package",
"@dalecb/obsidian-semantic-mcp",
"obsidian-semantic-mcp-setup"
],
"env": {
"OBSIDIAN_VAULT_ROOT": "YOUR_OBSIDIAN_VAULT_ROOT_HERE"
}
}
}
}
Frequently asked questions
Memory Find is categorized under Databases and uses an install path we have not confirmed yet. Obsidian Semantic Search belongs to Databases and uses a local stdio subprocess. Pick Memory Find for databases work and Obsidian Semantic Search 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. Memory Find has no confirmed install command yet — follow its own setup instructions.
Memory Find is listed as free. Auth: no auth required. Obsidian Semantic Search 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 memory-find and obsidian-semantic-search as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Memory Find has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Obsidian Semantic Search has 52/100 (Good) with 3 views, 0 installs and 1 GitHub stars.