Cosmos MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 92 installs a week from npm. Last commit 26 Aug 2026.
Personal knowledge graph every MCP client reads from and writes to. Portable across agents.
What the code does
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
"\(home)/Library/LaunchAgents/com.polaritylab.cosmos-mcp.sync.plist"
postinstall: npm rebuild better-sqlite3 2>/dev/null || true
spawnSync(rebuildCmd, ["rebuild", "better-sqlite3"], {
let process = Process()
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add cosmos-mcp -- npx -y @polarity-lab/cosmos-mcp{
"mcpServers": {
"cosmos-mcp": {
"command": "npx",
"args": [
"-y",
"@polarity-lab/cosmos-mcp"
]
}
}
}[mcp_servers.cosmos-mcp]
command = "npx"
args = ["-y", "@polarity-lab/cosmos-mcp"]{
"mcpServers": {
"cosmos-mcp": {
"command": "npx",
"args": [
"-y",
"@polarity-lab/cosmos-mcp"
]
}
}
}{
"servers": {
"cosmos-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@polarity-lab/cosmos-mcp"
]
}
}
}Optional settings from the registry entry, left out of the block above:
COSMOS_TOKEN (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_...`).
Alternatives to Cosmos MCP
same job, measured the same wayLocal-first, zero-knowledge AI memory across Claude, Cursor, and every MCP client. 0 RTT reads.
A shared team wiki your coding agents read and write — across every repo and every MCP client.
Personal AI memory layer on your own computer. Read/write durable memory across MCP clients.
Cross-vendor AI memory over MCP. One semantic store, readable and writeable from every MCP client.
Persistent personal memory for AI assistants — save, search, and recall across every MCP client.
Persistent code knowledge graph + 9 composite MCP tools for AI coding agents.
A portable persona for MCP clients — the same agent in Claude Code, Codex, Cursor and VS Code
Persistent knowledge graph: entities, relations, and observations for agents.
Cosmos MCP — questions
Answers built from our own checks of this server.