Cosmos

Every AI you use is building its own private graph of you. Claude has one. ChatGPT has one. Cursor has one. None of them talk to each other, and none of them are yours.

Cosmos inverts that. Your knowledge graph lives in one place, and any MCP-capable client (Claude Code, Claude Desktop, Cursor, Codex, Zed, Continue) reads and writes to the same one. When an agent notices something durable about you, it lands in the graph. When you switch tools, the graph follows. The user, not the platform, owns the integration layer.

The thing you carry is a.polarityfile. Yours.

curl -fsSL https://mcp.polarity-lab.com/install.sh | sh

On macOS this installs the MCP server, registerscosmos-mcp://, wires Claude Desktop, Claude Code, Cursor, Codex, Zed, and Continue, then installsCosmos Sync.appso iMessage, browser history, calendar, Claude Desktop transcripts, and shell history can sync in the background. On linux and windows it installs the MCP server path only.

If you want to inspect before changing anything:

curl -fsSL https://mcp.polarity-lab.com/install.sh -o install.sh bash install.sh --dry-run bash install.sh

There are two ways to get apmk_…key onto your Mac.

For that deep link to work, register the URL scheme once:

npx -y @polarity-lab/cosmos-mcp install-handler

This drops a tiny.appinto~/Library/Application Support/cosmos-mcp/and registerscosmos-mcp://with Launch Services. macOS-only.

Manual.If you already have apmk_…key, or you do not want to install the handler:

npx -y @polarity-lab/cosmos-mcp provision pmk_xxx

The CLI validates the key against cosmos, then stores it in the macOS system keychain under servicecosmos-mcp-key. Subsequentimessage sync,browser sync,calendar synccalls read from the keychain. No env var needed.

npx -y @polarity-lab/cosmos-mcp imessage probe

Verifies Full Disk Access is granted and reports how many chats are visible. If you see an EACCES message, open System Settings, Privacy & Security, Full Disk Access, and add Terminal (or whichever app runs the CLI).

CI.SetCOSMOS_TOKEN=pmk_…in env. It takes precedence over the keychain, so existing pipelines keep working untouched.

The installer handles this for common clients. If you want to wire a client by hand, point it at the package.

{ "mcpServers": { "cosmos": { "command": "npx", "args": ["-y", "@polarity-lab/cosmos-mcp"] } } }

That config drops into~/Library/Application Support/Claude/claude_desktop_config.jsonfor Claude Desktop, your.cursor/mcp.jsonfor Cursor, the equivalent for whichever client.

The MCP server is one way to write to the graph. Cosmos accepts source pages from anywhere you keep notes, and the MCP read tools see all of it through the same view.

Unchanged pages are skipped server-side, so re-syncing a quiet vault or stable Notion workspace costs almost nothing. The iMessage sync is incremental too, watermarked on the last successful run, so re-running it is a no-op until new messages arrive.

cosmos-mcpships animessagesubcommand that reads your local Messages database and lands every conversation in your graph.

# default: incremental sync, 90-day window on first run npx -y @polarity-lab/cosmos-mcp imessage sync # re-sync the original 90-day window regardless of watermark npx -y @polarity-lab/cosmos-mcp imessage sync --backfill # pull everything since a specific date npx -y @polarity-lab/cosmos-mcp imessage sync --since 2024-01-01 # check what the last run did npx -y @polarity-lab/cosmos-mcp imessage status

A three-rule slop filter (no-reply senders, short-code numbers, low-volume contacts) keeps the graph clean. Your AddressBook resolves phone numbers and emails into real contact names. The reading is local to your Mac; only the extracted, normalized turns go into your cosmos graph, which is your account.

cosmos-mcpships aclaude-desktopsubcommand that watches Claude Code session transcripts and lands each turn in your graph. The desktop chat surface itself stores conversations server-side, so the live, watchable on-disk source is~/.claude/projects/<encoded-cwd>/<session-id>.jsonl.

# default: incremental, watermarked per session npx -y @polarity-lab/cosmos-mcp claude-desktop sync # limit to recent activity npx -y @polarity-lab/cosmos-mcp claude-desktop sync --since 2026-05-01 # scan and report without shipping npx -y @polarity-lab/cosmos-mcp claude-desktop sync --dry-run # see what the last run did npx -y @polarity-lab/cosmos-mcp claude-desktop status

Tool-use blocks, hook plumbing, and sub-agent (sidechain) turns are stripped client-side; only the visible text the user and the assistant exchanged is shipped. Each session id becomes its own thread node, keyed by(user_id, "claude-desktop", session_id).

cosmos-mcp daemon installdrops a LaunchAgent that ticks every four hours and runs the browser, iMessage, calendar, claude-desktop, and shell-history syncs back-to-back. The agent fires a signed, notarizedCosmos Sync.appbundle that ships inside the npm package and gets copied into~/Applications/Cosmos Sync.appat install time.

npx -y @polarity-lab/cosmos-mcp daemon install

After install, grant the bundle Full Disk Access once:
- open System Settings → Privacy & Security → Full Disk Access
- click +, then drag~/Applications/Cosmos Sync.appinto the list
- make sure the checkbox next to it is on
- runcosmos-mcp daemon kickto fire a tick now

Browser sync works without that step. iMessage and Calendar need it because they read TCC-protected SQLite databases on the user side.cosmos-mcp daemon statusreports the signing team id, the plist + runner paths, and whether launchd has the agent loaded.cosmos-mcp daemon uninstallremoves the plist, runner, and~/Applications/Cosmos Sync.app.

Your AI tools each know fragments of you. They are not allowed to share. Cosmos is the layer that lets them. You hold the key. The graph is portable. When you leave, you take the understanding with you.

Persistent AI memory across tools — remember your preferences, code standards, and decisions across Claude Code, Cursor, Codex, and any MCP tool. Local-first, zero-cloud.

One memory URL. Every AI tool. Your rules, lessons, and context — recalled automatically, every conversation.

Portable knowledge layer about you, connected to AI tools via MCP. Learns from how you work. Travels across Claude, ChatGPT, Cursor, and more.

Gives your AI persistent context across every chat and session, so it always knows where your projects stand and what's next.

Hebbian memory for AI agents — learns file access patterns, builds neural pathways, predicts next tools/files, saves tokens

Local-first cross-agent memory MCP. 6-layer structured brain (goal/context/emotion/impl/caveat/learning) with token-saving file diff cache (86% measured savings on re-reads)

Give your AI the ability to remember key facts and everything you've ever discussed

Mnemex is a Python MCP server that provides AI assistants with human-like memory dynamics through temporal decay and natural spaced repetition, storing memories locally in human-readable JSONL and Markdown formats.

Centralized note store across AI clients: Claude, ChatGPT, Cursor, Codex, Windsurf. Save in one client, access in another instantly. Across devices — phone, desktop, everywhere. Cross-session context: 'catch me up' surfaces plans and findings from any prior session. AES-256-GCM encryption at rest, per-user key isolation. Soft delete with 30-day recovery window. Pin notes to exempt from cleanup and prioritize. Tag notes for categorization and filtering ('tag: auth'). Your mctx account is your identity — instant access from any AI tool.

An AI capability enhancement system providing professional roles, memory management, and knowledge systems for applications like Claude and Cursor.