Sovseal Memory MCP Server

Zero-knowledge, local-first AI memory for work you can't send to the cloud. One private memory across Claude, ChatGPT, Cursor, and every MCP client - plaintext physically never leaves your machine.

People connecting browser automation tools to Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.

VERIFIED ACTIVE

LAST COMMIT 2026-08-05 · ★ 7 · #101 OF 196 MAINTAINED BROWSER AUTOMATION · VERIFIED 2026-08-25

Apache-2.0 · TypeScript servers · how we verify → /methodology

01 · Install Sovseal Memory

before you install - you'll need

Set SOVSEAL_TRANSPORT, SOVSEAL_ENDPOINT before connecting.

Claude Code

claude mcp add sovseal-core -- npx -y @sovseal/mcp-server

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "sovseal-core": {
      "command": "npx",
      "args": [
        "-y",
        "@sovseal/mcp-server"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license Apache-2.0 - declared in the repository

npm package @sovseal/mcp-server - published under the repo owner's npm scope (@sovseal)

registry registry publisher io.github.bobybarack is not the repo owner (sovseal) - the registry entry was published by someone else

03 · Who maintains Sovseal Memory

sovseal-memory is maintained by sovseal. It's the only MCP server we track from this author; the repo dates to May 2026.

04 · Facts

repository: github.com/sovseal/core
category: browser automation - ranked #101 of 196 actively-maintained browser automation servers as of 2026-08-25.
registry: io.github.bobybarack/sovseal-memory (active, first published 2026-08-04)
packages: npm:@sovseal/mcp-server

05 · Sovseal Memory FAQ

What is Sovseal Memory?

Zero-knowledge, local-first AI memory for work you can't send to the cloud. One private memory across Claude, ChatGPT, Cursor, and every MCP client - plaintext physically never leaves your machine.

Is Sovseal Memory still maintained?

Yes - as of 2026-08-25, its last commit was 2026-08-05. We re-verify nightly.

How do I install Sovseal Memory?

Run `npx -y @sovseal/mcp-server`. The README documents 2 environment variables (SOVSEAL_TRANSPORT, SOVSEAL_ENDPOINT) to set first. Set SOVSEAL_TRANSPORT, SOVSEAL_ENDPOINT before connecting. You can also paste the ready-made client config above.

Does Sovseal Memory run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

06 · Alternatives to Sovseal Memory

Alternatives to Sovseal Memory

Maintained browser automation servers if Sovseal Memory isn't the fit.

Pairs well with

Servers that cover what Sovseal Memory doesn't - only shown when the pairing reason fits the companion.

More browser automation MCP servers · Mobile Device MCP · DevTool MCP · Gdocs Comments MCP · Metro MCP · StudioMeyer Video

More TypeScript MCP servers · Spanlens MCP Server · Transcription · Omnisearch · SQLite Tools · Turso Cloud · see all