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.
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.
- 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
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.
Paste a URL with a key — add the endpoint to your client