Localmem MCP
UnclaimedLocal-first, zero-API memory for AI agents. Persistent, private, and yours — runs entirely on your machine, no cloud calls, no API keys.
Set up this server
01 / Choose your client
02 / Before you connect
Authentication is not specified. Check the project instructions before connecting.
Project instructions03 / Add the configuration
claude mcp add --transport stdio 'localmem-mcp' -- 'uvx' 'localmem-mcp'04 / Check it in your client
Open your client’s MCP settings and confirm the server connects and lists its tools. A copied configuration does not confirm a working connection.
More in AI & ML
Browse the full directoryUnclaimed listing
Is this your MCP server?
This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.
Claim this serverSecurity profile
Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works
Documented tools (3)
From project documentation. A server handshake does not verify each tool’s description or behavior.
Tool change history
FAQ
Questions about Localmem MCP Server
- How do I connect Localmem MCP Server to Claude?
- Run `claude mcp add localmem-mcp -- uvx localmem-mcp` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.
- Is Localmem MCP Server free?
- The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
- What can Localmem MCP Server do?
- Localmem MCP Server documents 3 tools to the agent, including recall_memory, search_memory, store_memory. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.