Cosmic Hosted MCP (agent scope)

other

Agent-driven content work in Cosmic CMS needs its own access boundary — you don't want an agent creating projects with the same permissions as a human admin. The agent-scope version of Cosmic's hosted MCP connection gives Neotask exactly that: it can create and manage AI agent sessions that read and write structured content, and provision new agent-created projects and content buckets, all scoped specifically to agent-level access rather than full account control.

What you can automate

Cosmic Hosted MCP (agent scope)Create and manage AI agent sessions that read and write structured content within a Cosmic-hosted project, scoped to agent-level access. Provision new agent-created projects and content buckets for automated workflows.

Real workflows

Spin up a new automated content project

Ask Neotask to provision a new Cosmic project and content bucket for an automated workflow, and it creates the agent-scoped session and structures needed without touching your admin-level project setup.

Frequently asked questions

How is agent scope different from full account access?

Agent scope limits what the connection can do to agent-created sessions, projects, and buckets, rather than full admin control over your Cosmic account.

Can it create new buckets on its own?

Yes, provisioning new agent-created projects and content buckets is part of what this scope supports.