A side-by-side look at the Leteo and Memors 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.
Memors 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.
No confirmed install command for Memors yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Leteo is categorized under Databases and uses a local stdio subprocess. Memors belongs to Databases and uses an install path we have not confirmed yet. Pick Leteo for databases work and Memors 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.
Leteo is listed as free. Auth: no auth required. Memors 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 leteo and memors as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Leteo has a quality signal of 45/100 (Fair) with 3 views, 0 installs and 2 GitHub stars. Memors has 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.