The MCP memory server
that runs on your machine.
telys mcp is a local stdio MCP memory server for Claude Code, Claude Desktop, Cursor, and Codex. Your client launches it as a subprocess — no port, no daemon, no cloud dependency. What the assistant stores persists across sessions, in a governed store on your own disk.
Three commands. Every client.
The SDK is Apache-2.0. telys login signs you in once, then provisions and verifies the signed, device-licensed runtime — after that, the server runs fully offline. telys mcp install writes the server entry into each client's config: it auto-detects installed clients, merges idempotently, and backs up any file it touches.
pipx install telys # Apache-2.0 SDK
telys login # one sign-in → signed device license
telys mcp install # register the server in your clients
# defaults: auto-detect installed clients, user scopetelys mcp install --client claude|cursor|codex|claude-desktop|all --scope user|project # defaults: auto-detect installed clients, user scope
Public Beta — `pipx install telys` from PyPI, then `telys login` (free for one developer) provisions the signed on-device runtime.
Zero environment. Self-locating runtime.
Every client gets the same canonical entry: launch telys with the single argument mcp. No PYTHONPATH, no kernel paths, no keys in config — the runtime self-locates from the verified telys login install.
The transport is MCP stdio: newline-delimited JSON-RPC 2.0 over stdin/stdout, with the client owning the process lifecycle. Where a client's own CLI owns its config file, the installer defers to it — claude mcp add for Claude Code, codex mcp add for Codex.
{
"mcpServers": {
"telys": {
"command": "telys",
"args": ["mcp"]
}
}
}Persistent, on-device, governed memory.
Memory outlives the session
Notes, decisions, and context stored through telys_add are still there in the next session, the next week, a different client. The store is shared state, not conversation state.
A directory on your disk
Memories live at ~/.telys/memory, or wherever $TELYS_MEMORY_PATH points. Add and search execute in-process against the local engine — offline after telys login, nothing leaves the machine at query time.
Scoped, filterable recall
Collections partition by a scope key. Search combines semantic and lexical matching and accepts an equality filter — the same engine that returns an explain plan on every SDK query.
| Tool | What it does |
|---|---|
| telys_search | Semantic + lexical search over a memory collection. Optional top_k and a single-key equality filter. |
| telys_add | Add text documents to a collection, created if absent. Optional ids and per-document metadata. |
| telys_create_collection | Create a collection; the partition key defaults to scope. |
| telys_list_collections | List the collections in the store. |
| telys_stats | Store statistics for a collection. |
Inspect it. Remove it.
telys mcp status reports where the server is registered across client configs. telys mcp uninstall deregisters it, taking the same --client and --scope options as install and backing up each config before writing. The same memory tools are also available from the terminal via telys mem.
telys mcp # run the stdio server (what your client launches) telys mcp status # where is the server registered? telys mcp uninstall # deregister (--client / --scope, as at install) telys mcp --path <dir> # point the server at a specific memory root
claude mcp add, or .mcp.json
User scope registers through the official claude mcp add. Project scope writes a clean, MCP-only .mcp.json at the repository root — safe to commit.
claude_desktop_config.json
Merges the entry into the app's config file in its platform config directory. Restart Claude Desktop to load the server.
~/.cursor/mcp.json
Writes the user-level mcp.json, or .cursor/mcp.json inside the project with --scope project.
codex mcp add, or config.toml
Registers through codex mcp add when the CLI is present; otherwise appends an [mcp_servers.telys] block to config.toml.
Add Telys to your MCP client.
Telys is in public beta (0.1.0b4). The SDK is Apache-2.0 on PyPI — pipx install telys, then telys login provisions the signed on-device runtime, free for one developer.