News · Use case · November 6, 2026

Give Claude a private memory with the Ghostdrive MCP server

Connect Claude Code or Claude Desktop to your own Ghostdrive node: memory that stays encrypted on your machine, shared one file at a time.

DRIVE 369 DAO · 2 min read

Every chat with an AI starts from zero, or its memory lives on the vendor's servers. With Ghostdrive, your agent's memory lives on your own node, encrypted with your keys, and works with any agent that speaks the Model Context Protocol (MCP): Claude Code, Claude Desktop or your own.

Set it up

git clone https://github.com/NeyraLabs/ghostdrive && cd ghostdrive/packages
npm install && npm run build && npm link -w @ghostdrive/node
ghostdrive init && ghostdrive backup on
ghostdrive daemon &
claude mcp add ghostdrive -- ghostdrive mcp

For Claude Desktop, add the server to claude_desktop_config.json:

{ "mcpServers": { "ghostdrive": { "command": "ghostdrive", "args": ["mcp"] } } }

What your agent can do

Tool	What it does
`ghostdrive_remember`	Keep a note as an encrypted file and get back its capability
`ghostdrive_search`	Search your notes, Terminal threads and text files by meaning
`ghostdrive_add`, `ghostdrive_read`, `ghostdrive_list`	Store, read and list files
`ghostdrive_send`, `ghostdrive_inbox`	Send a sealed message, or one file, to another Ghost ID, and read replies

A day with it

You ask Claude to summarise a long contract. It keeps the summary with ghostdrive_remember. A week later, in a new session, you ask what the termination clause said: Claude finds it with ghostdrive_search, on your machine, without anything leaving it. When your lawyer needs that one summary, Claude sends exactly that file to their Ghost ID. They get one capability, for one file, and nothing else.

Why it is private

The MCP server talks only to your node's local API. Search runs on your CPU, and the index is sealed with your vault keys. A capability is permission: an agent that holds one can read that file and nothing more. Read more in the Docs.