cosmic_objects_list
List objects with optional type filter, status, and pagination
LABSCO SUMMARY
Permission by key format is crude, obvious, and hard to get wrong.
There is no scope negotiation to misconfigure: a connection either has the write key or it does not, and you can see which at a glance in the config file. For giving an agent read access to a content bucket, that clarity is worth more than a scope system nobody checks. The tools that edit object type schemas deserve a moment's thought before you hand over a write key — those change the content model every consumer of the bucket depends on.
What it is
Cosmic's endpoint, addressed per bucket: the URL contains your bucket slug. What makes it unusual is that permission is carried by the key format rather than by scopes.
What you get
- Objects: list with type filter and paging, get by id or slug, create, update, delete
- Media: list by folder, get details, upload from a URL or base64, delete
- Object types: list, get the schema, create, update, delete — the content model itself is editable
- AI generation: text, image and video, with the media uploaded into the bucket
- cosmic_blocks_list — the bucket's reusable rich-text content blocks
Requirements
A bucket-scoped bearer key. Send the read key alone and only the read tools work; send read_key:write_key — or add the write key as a header — and the writes unlock. There is no OAuth.
Setup effort
Get your endpoint, then paste it — add your endpoint to your client with your key
USE CASES
01
Reading content into an application
Connect with the read key alone, and the write tools are simply absent.
02
Publishing from a conversation
Create or update objects with the combined key, and upload media from a URL.
03
Generating an image straight into the bucket
AI generation uploads the result rather than returning it for you to move.
04
Changing the content model
Object type schemas are editable — deliberate work, not something to leave to an agent by default.
18 tools
Listed in project docs. Your client may show a different list.
cosmic_objects_get
Get a single object by ID or slug
cosmic_objects_create
Create a new object
cosmic_objects_update
Update an existing object
cosmic_objects_delete
Delete an object
cosmic_media_list
List media files with optional folder filter
cosmic_media_get
Get media details by ID
cosmic_media_upload
Upload media from URL or base64
cosmic_media_delete
Delete a media file
cosmic_types_list
List all object types in the bucket
cosmic_types_get
Get object type schema by slug
cosmic_types_create
Create a new object type
cosmic_types_update
Update object type schema
cosmic_types_delete
Delete an object type
cosmic_ai_generate_text
Generate text content using AI
cosmic_ai_generate_image
Generate and upload an AI image
cosmic_ai_generate_video
Generate and upload an AI video
cosmic_blocks_list
List the bucket's reusable rich-text Content Blocks ({{name /}} tokens)
BEFORE YOU INSTALL
What to know first
Tools you get
18 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- Bucket keys from your bucket's API Access settings in the Cosmic dashboard, sent as Authorization: Bearer <read_key> (read-only) or Bearer <read_key>:<write_key> (full access); the write key can go in an X-Cosmic-Write-Key header instead. No OAuth
INSTALLATION
Connect your client
Add your endpoint to your client with your key.
Server setup
ENDPOINT URL
https://mcp.cosmicjs.com/v1/buckets/<YOUR_BUCKET_SLUG>Requirements
- Bucket keys from your bucket's API Access settings in the Cosmic dashboard, sent as Authorization: Bearer <YOUR_READ_KEY> (read-only) or Bearer <YOUR_READ_KEY>:<YOUR_WRITE_KEY> (full access); the write key can go in an X-Cosmic-Write-Key header instead. No OAuth.
