Agent API and MCP
Use the Agent API or MCP to work inside a Skayle organization. It exposes the approved Skayle operation catalog for organization settings, content, collections, taxonomies, publishing, analytics, AI Search Visibility, Site Audit, and integrations. The MCP server and/v2 Agent API use the same operation definitions,
permission scopes, confirmation rules, row-level security, and audit log.
Every app procedure is explicitly classified as agent-exposed or intentionally
excluded, so the agent surface cannot silently drift behind the application.
This interface works whether the organization uses Skayle CMS or an external
connector. For example, an agent can create and publish an item through the
Agent API, and Skayle can then deliver it through Skayle CMS or push it to the
configured external CMS.
Set up the Agent API and MCP →
Skayle CMS Content API
Use the/v1/{organizationId} API to retrieve content for a website or
application when the organization’s connector mode is set to Skayle CMS.
It provides JSON:API-style collections, articles, collection items, taxonomies,
and media.
The CMS Content API does not create, edit, publish, or delete content. Use the
Skayle application, Agent API, or MCP for those management actions.
Read the Skayle CMS API reference →
External CMS connectors
WordPress, Sanity, Webflow, and Contentful connectors are outbound publishing destinations. Skayle uses each provider’s management API to push content into that CMS. They are not another version of the public Skayle CMS Content API:- Choose Skayle CMS to retrieve content from Skayle through
/v1. - Choose an external connector to have Skayle publish content into that CMS.
- Use the Agent API or MCP to let authenticated AI clients and automations manage either workflow.