Zephr Docs

Clients

Zephr is a server, not a plugin. Every client talks to the same stdio JSON-RPC process, and every capture is an explicit tool call the agent chose to make — there is no background indexer and no editor-state scraper.

Supported clients

ClientStatusNotes
Claude CodeshippedThe deepest integration. ClaudeCodeAdapter prefers the admitted scope snapshot, binding every tool call to the admitted worktree.
Cursorevolving@zephr-ai/adapter-cursor is a scope-bound mapper library, not an editor integration. The operator wires it into the process that brokers tool calls.
Any MCP clientshippedProtocol stable: any consumer respecting the stdio JSON-RPC MCP contract can connect using the same configuration shape.

Capture is always explicit

Zephr does not scrape editor state, chat history, or project indexes. Every capture is a tool call the agent explicitly made.

The Cursor distinction matters most: the adapter ships as a first-party mapper package rather than something the editor bundles, and Zephr still never reads private editor state.