A side-by-side look at the Memory Find and Memtether MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
No tool names declared yet. Check the project README from the listing page.
Memtether 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.
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.
Memtether
No confirmed install command for Memtether yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Memory Find is categorized under Databases and uses an install path we have not confirmed yet. Memtether belongs to Databases and uses an install path we have not confirmed yet. Pick Memory Find for databases work and Memtether for databases.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
Memory Find is listed as free. Auth: no auth required. Memtether 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 memory-find and memtether 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. Memtether has 33/100 (Emerging) with 0 views, 0 installs and 2 GitHub stars.