Cosmos MCP

Name: Cosmos MCP
Author: teampolarity

作者：teampolarity版本 0.7.1i★ –i在你的电脑上运行

注册名称io.github.teampolarity/cosmos-mcp

安装

概览

作者提供的说明（英文原文）

Personal knowledge graph every MCP client reads from and writes to. Portable across agents.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i非常新↓ 118/周 · ★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 搜索与 AI 记忆
你需要填写：COSMOS_TOKEN

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： COSMOS_TOKEN

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

claude mcp add cosmos --env COSMOS_TOKEN=your-value -- npx -y @polarity-lab/cosmos-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "cosmos": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@polarity-lab/cosmos-mcp"
      ],
      "env": {
        "COSMOS_TOKEN": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

COSMOS_TOKEN 机密 env
pmk_ key from https://cosmos.polarity-lab.com/connectors. Optional on macOS once the system keychain is provisioned via `npx -y @polarity-lab/cosmos-mcp provision pmk_...`.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 teampolarity 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“搜索与 AI 记忆”中的其他服务器比较i

星标数多于此分类中其他 5709 个服务器的 0%
发布到注册中心的时间比此分类中其他 5709 个服务器的 13% 更新
基础检查结果等于或优于此分类中其他 5709 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Cosmos MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：COSMOS_TOKEN

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.7.1）于6个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Context7, Codebase Memory, Exa

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Context7

Up-to-date docs for AI agents

作者：upstash广泛使用↓ 97.3万/周★ 6.4万前天更新

电脑或云端

安装

Codebase Memory

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

作者：DeusData广泛使用↓ 1.8万/周★ 4.8万22天前更新

在你的电脑上运行

安装

Exa

Connect AI agents to Exa for web search, content fetching, and multi-step research.

作者：exa-labs广泛使用★ 52132个月前更新

在云端运行✓ exa.ai

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

cosmos-mcp

One exocortex. Every agent.

MCP server for your Cosmos graph.

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 .polarity file. Yours.

One-line install

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

On macOS this installs the MCP server, registers cosmos-mcp://, wires Claude Desktop, Claude Code, Cursor, Codex, Zed, and Continue, then installs Cosmos Sync.app so 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

Provisioning

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

Automatic. Sign in at cosmos.polarity-lab.com/connectors, tap "open in cosmos-mcp." The OS opens a one-shot handler that writes the key into your system keychain. You never see the raw key.

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

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

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

Manual. If you already have a pmk_… 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 service cosmos-mcp-key. Subsequent imessage sync, browser sync, calendar sync calls read from the keychain. No env var needed.

Confirm iMessage access.

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. Set COSMOS_TOKEN=pmk_… in env. It takes precedence over the keychain, so existing pipelines keep working untouched.

Manual MCP config

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

npx -y @polarity-lab/cosmos-mcp init

This opens your browser. Sign in at cosmos.polarity-lab.com, approve a per-user key, and the token lands at ~/.config/cosmos-mcp/token (0600). Then point any MCP client at it:

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

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

What you get

Eleven tools, four read, seven write.

Read

Tool	Calls	What it returns
`polarity_whoami`	`GET /api/polarity/whoami`	Bound user + scopes. Cheap probe.
`polarity_export`	`POST /api/polarity/export`	Full personal graph as `polarity/v1` JSON.
`polarity_get_graph`	`GET /api/polarity`	Graph view, scoped by entity (`user`, `cosmos`, `polarity`).
`polarity_ask`	`POST /api/polarity/ask`	NL question synthesized over the graph.

Write

Tool	Calls	What it does
`polarity_observe`	`POST /api/polarity/observe`	Freeform observation. Cosmos extracts.
`polarity_record_event`	`POST /api/polarity/observe` (kind=event)	Something happened at a point in time.
`polarity_record_preference`	`POST /api/polarity/observe` (kind=preference)	A like, dislike, working-style rule.
`polarity_capture_turn`	`POST /api/polarity/capture-turn`	Hand a whole user/assistant exchange to cosmos. Pulls every durable observation in one call. Prefer over multiple `polarity_observe` calls.
`polarity_reconstruct_hours`	`POST /api/polarity/reconstruct-hours`	Persist life-hour receipts onto the skill-map sky (per user only). Use from Cursor/Cosmos IDE after substantive work.
`polarity_dump`	`POST /api/polarity/dump`	Location-anchored short message.
`polarity_checkin`	`POST /api/polarity/checkin`	Check-in at a waypoint. Triggers co-presence detection.
`polarity_declare`	`POST /api/polarity/declare`	Declare future presence at a waypoint.

Sources

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.

Source	How it connects	What lands
iMessage	Local CLI: `npx -y @polarity-lab/cosmos-mcp imessage sync`. Mac only. Grant Terminal Full Disk Access first.	Conversational turns from `chat.db`, with text content. People appear as person nodes in your graph, sized by conversation weight, named via your local AddressBook, dated by your real message timestamps.
Claude Desktop	Local CLI: `npx -y @polarity-lab/cosmos-mcp claude-desktop sync`. Reads Claude Code session transcripts at `~/.claude/projects/`.	Every Claude Code session becomes a thread node; user and assistant turns land in `conversation_turns` with full text. Tool-use plumbing is stripped client-side.
Shell history	Local CLI: `npx -y @polarity-lab/cosmos-mcp shell-history sync`. Reads `~/.zsh_history` (falls back to bash/fish) with a byte-offset watermark.	Each sync window lands as one `source_page` keyed by `shell-history:` , body = newline-joined commands. Trivial commands (`ls`, `cd ..`, single chars) and consecutive duplicates are filtered client-side.
Notion	OAuth at cosmos.polarity-lab.com/connectors. Pick the pages and databases you want shared.	Each Notion page becomes a `source_page` node, keyed by Notion id, kept fresh by a daily sync.
Obsidian	Community plugin: polarity-lab/obsidian-cosmos. Paste your `pmk_` key, point at your vault.	Each note becomes a `source_page` node keyed by vault-relative path. Tags and wikilinks resolve into edges.
MCP clients	This package.	Observations, events, preferences, location dumps, check-ins, declarations.
Direct API	`POST /api/polarity/observe` with your key.	Anything you can express as an observation.

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.

iMessage sync

cosmos-mcp ships an imessage subcommand 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.

Claude Desktop sync

cosmos-mcp ships a claude-desktop subcommand 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/ / .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).

Background sync (macOS)

cosmos-mcp daemon install drops 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, notarized Cosmos Sync.app bundle that ships inside the npm package and gets copied into ~/Applications/Cosmos Sync.app at 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.app into the list
make sure the checkbox next to it is on
run cosmos-mcp daemon kick to 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 status reports the signing team id, the plist + runner paths, and whether launchd has the agent loaded. cosmos-mcp daemon uninstall removes the plist, runner, and ~/Applications/Cosmos Sync.app.

Configuration

Env var	Default	When you set it
`COSMOS_URL`	`https://cosmos.polarity-lab.com`	Override the cosmos API endpoint.
`COSMOS_TOKEN`	(from keychain)	`pmk_...` per-user key for CLI subcommands. Takes precedence over the macOS keychain entry. Set this in CI.
`COSMOS_MCP_KEY`	(from token file)	`pmk_...` per-user key. Honored for back-compat.
`COSMOS_USER_ID`	(from token file)	Polarity user id.
`COSMOS_SYSTEM_KEY`	(unset)	Single-tenant mode. Sends `X-System-Key` instead of `X-MCP-Key`. Requires `COSMOS_USER_ID`. For internal testing before per-user keys are deployed.

The pitch in three lines

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.

License

MIT.