AI vs Cosmic
A side-by-side look at the AI and Cosmic MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AI for developer tools work as a local process; choose Cosmic for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose AI when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Cosmic when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
COSMIC_BUCKET_SLUG, COSMIC_READ_KEY, COSMIC_WRITE_KEY. - You want tools like
cosmic_objects_list, cosmic_objects_get, cosmic_objects_create.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 57/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | COSMIC_BUCKET_SLUGCOSMIC_READ_KEYCOSMIC_WRITE_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 1 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 18 |
| Full listing | View AI | View Cosmic |
Tools & capabilities
AI tools
No tool names declared yet. Check the project README from the listing page.
Cosmic tools 18
cosmic_objects_listList objects with optional type filter, status, and paginationcosmic_objects_getGet a single object by ID or slugcosmic_objects_createCreate a new object (requires write key)cosmic_objects_updateUpdate an existing object (requires write key)cosmic_objects_deleteDelete an object (requires write key)cosmic_media_listList media files with optional folder filtercosmic_media_getGet media details by IDcosmic_media_uploadUpload media from URL or base64 (requires write key)cosmic_media_deleteDelete a media file (requires write key)cosmic_types_listList all object types in the bucketcosmic_types_getGet object type schema by slugcosmic_types_createCreate a new object type (requires write key)- +6 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
AI
{
"mcpServers": {
"contentrain-ai": {
"command": "npx",
"args": [
"-y",
"contentrain"
]
}
}
}
Cosmic
{
"mcpServers": {
"cosmic": {
"command": "npx",
"args": [
"-y",
"@cosmicjs/mcp"
],
"env": {
"COSMIC_BUCKET_SLUG": "YOUR_COSMIC_BUCKET_SLUG_HERE",
"COSMIC_READ_KEY": "YOUR_COSMIC_READ_KEY_HERE",
"COSMIC_WRITE_KEY": "YOUR_COSMIC_WRITE_KEY_HERE"
}
}
}
}
Frequently asked questions
AI is categorized under Developer Tools and uses a local stdio subprocess. Cosmic belongs to Developer Tools and uses a local stdio subprocess. Pick AI for developer tools work and Cosmic for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
AI is listed as free. Auth: no auth required. Cosmic has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add contentrain-ai and cosmic as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AI has a quality signal of 57/100 (Good) with 4 views, 0 installs and 6 GitHub stars. Cosmic has 56/100 (Good) with 1 views, 0 installs and 1 GitHub stars.