Developer · Remote MCP server
Cosmic
Manage Cosmic CMS content, media, object types, and AI generation from any MCP client.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.cosmicjs/mcp- Version
- 1.6.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-07-31
- Updated
- 2026-07-31
- Publisher
- com.cosmicjs
- Namespace
- Namespace verified by the MCP Registry via the domain cosmicjs.com · how
- Website
- www.cosmicjs.com
- Repository
- github.com/cosmicjs/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.cosmicjs.com/v1/buckets/{bucket_slug} | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @cosmicjs/mcp | 1.6.0 | stdio |
How to connect Cosmic
Cosmic is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.cosmicjs.com/v1/buckets/{bucket_slug}, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The URL contains placeholders to fill in before connecting: {bucket_slug}.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
It can also run locally from a Node.js package published to the npm registry: @cosmicjs/mcp version 1.6.0. 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 @cosmicjs/mcp@1.6.0. It reads these environment variables: COSMIC_BUCKET_SLUG (required), COSMIC_READ_KEY (required, secret) and COSMIC_WRITE_KEY (secret); set them 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": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@cosmicjs/mcp@1.6.0"
],
"env": {
"COSMIC_BUCKET_SLUG": "<value>",
"COSMIC_READ_KEY": "<secret>",
"COSMIC_WRITE_KEY": "<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 |
|---|---|
| CortexSyslog receiver and MCP server for homelab log intelligence. | Remote & Local · HTTP, stdioLive check: sign-in required |
| 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 |
| Cosmos MCPPersonal knowledge graph every MCP client reads from and writes to. Portable across agents. | Local · 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 |