Code Index vs Memory Find
A side-by-side look at the Code Index and Memory Find 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 Code Index for databases work as a local process; choose Memory Find for databases. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Code Index when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CODE_INDEX_HOME. - You want tools like
search_function, search_class, get_function.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M Memory Find | |
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 63/100 · Good | 36/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | CODE_INDEX_HOME | MEMORS_HOMEMEMORS_KB |
| Verified owner | Community listing | Community listing |
| GitHub stars | 138 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 31 | Not listed |
| Full listing | View Code Index | View Memory Find |
Tools & capabilities
Code Index tools 31
search_functionFull-text search across functions (name, docstring, body)search_classFull-text search across classesget_functionGet function by exact name (case-insensitive fallback; **(v0.44.0)** on 0 matches returns `did_you_mean` with similar names)get_classGet class by exact name (case-insensitive fallback; **(v0.44.0)** on 0 matches returns `did_you_mean` with similar names)get_object_structureStructure of a 1C object. **v0.63.0:** object templates are now in the registry — a row `Catalog.X.Template.Y` with the owner, the template kind and a `content_indexed` flag (large templates stay out of the index, yet the template itself is visible and findable by name)get_callersWho calls this function? **(v0.35.0)** each row carries the caller's source `path` (distinguishes same-named callers from different files). **v0.62.0:** for 1C configurations, form event handler bindings (`kind: form_binding`) are added to the code callers — such a procedure is run by the platform…get_calleesWhat does this function call? **(v0.35.0)** each row carries the source `pathfind_path(v0.23.0)** Shortest path in the call graph between two functions `from`→`to` (iterative cycle-safe BFS over unique `calls` nodes, `max_depth=5`, any language). Returns path edges `[{caller, callee, line}]`. **v0.57.0:** an empty answer carries walk cut-off flags `walk_depth_exhausted` / `walk_node…get_call_tree(v0.23.0)** Call tree from a `root` function up to `max_depth` (default 3). `direction`: `callees`/`down` (downstream) or `callers`/`up`. Flat edge list `[{caller, callee, line, depth, path}]` (**(v0.35.0)** `path` = source file of each edge) + nested `{name, children}` tree; `max_nodes` capfind_symbolSearch everywhere (functions, classes, variables, imports)get_importsImports by module or fileget_file_summaryComplete file map without reading source- +19 more on the listing page
Memory Find 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.
Code Index
{
"mcpServers": {
"code-index": {
"command": "npx",
"args": [
"-y",
"@regsorm/code-index-mcp"
],
"env": {
"CODE_INDEX_HOME": "YOUR_CODE_INDEX_HOME_HERE"
}
}
}
}
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.
Frequently asked questions
Code Index is categorized under Databases and uses a local stdio subprocess. Memory Find belongs to Databases and uses an install path we have not confirmed yet. Pick Code Index for databases work and Memory Find 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.
Code Index has no declared pricing — check the project's own site. Memory Find 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 code-index and memory-find as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Code Index has a quality signal of 63/100 (Good) with 2 views, 0 installs and 138 GitHub stars. Memory Find has 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.