Developer · Local MCP server
Cosmos MCP
Personal knowledge graph every MCP client reads from and writes to. Portable across agents.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.teampolarity/cosmos-mcp- Version
- 0.7.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-05-19
- Updated
- 2026-05-19
- Publisher
- teampolarity (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/teampolarity) · how
- Repository
- github.com/teampolarity/cosmos-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @polarity-lab/cosmos-mcp | 0.7.1 | stdio |
How to connect Cosmos MCP
Cosmos MCP runs locally from a Node.js package published to the npm registry: @polarity-lab/cosmos-mcp version 0.7.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @polarity-lab/cosmos-mcp@0.7.1. It reads the environment variable COSMOS_TOKEN (secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"cosmos-mcp": {
"command": "npx",
"args": [
"-y",
"@polarity-lab/cosmos-mcp@0.7.1"
],
"env": {
"COSMOS_TOKEN": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Cortex GatewaySelf-hosted federated MCP gateway: one OAuth 2.1 MCP server in front of N apps, user-level scopes. | Remote & Local · HTTPLive check: sign-in required |
| Cortex RMCPSelf-hosted homelab log intelligence over MCP, CLI, and REST with SQLite/FTS. | Local · stdio |
| Cortex RMCPRust MCP server for homelab logs, syslog, Docker logs, FTS search, and AI transcript correlation. | Local · stdio |
| CosmicManage Cosmic CMS content, media, object types, and AI generation from any MCP client. | Remote & Local · HTTP, stdio |
| Costory FinOps MCPFinOps MCP: query allocated, correlated cloud and AI cost across AWS, GCP, Azure and Snowflake. | Remote · HTTPLive check: sign-in required |
| CostPilotHosted MCP server for AWS cloud spend: service breakdowns, anomalies, savings and forecasts. | Remote · HTTPLive check: ✗ no handshake |
| COTAL actions (cotal.ai)Cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls. | Remote · HTTPLive check: ✓ handshake |
| Council AiMulti-LLM council: 25+ frontier models in parallel, consensus scoring, verdict-first code review. | Remote · HTTPLive check: ✓ handshake |