Statamic is a Laravel-based CMS used to run marketing sites, blogs and landing pages. Until now there was no way to ask your agent "what entries exist in the blog collection?" or "which taxonomy terms are already covered?" without opening the Statamic control panel and paging through content by hand. That changes today.

Statamic is a live MCP integration in Cogny. Connect a token and your site URL, and Claude (or any MCP client on app.cogny.com/mcp) can read your site's content in natural language.

TL;DR

Statamic is live now. Connect it with a STATAMIC_API_AUTH_TOKEN and your site URL from Settings → Cogny Managed MCPs.
Read tools across the whole CMS: get_site_info (ping + sites), list_collections, list_entries, get_entry, get_collection_tree, list_navs, get_nav_tree, list_taxonomies, list_taxonomy_terms, get_taxonomy_term, list_globals, get_global, list_forms, get_form, list_asset_containers, list_assets, list_users.
Strictly read-only by design. Statamic's Content REST API is a Pro feature with no public write endpoint, so Cogny can read your content but cannot create, edit, publish or delete entries through this connector — there are no write tools.
Resources you don't enable in config/statamic/api.php are simply not visible, and a missing or disabled resource surfaces a clear "resource not enabled" hint.
The Content Intelligence scheduled template now recognizes Statamic as a content-inventory signal alongside Search Console.
Works from any MCP client on app.cogny.com/mcp.
Included in Cogny Solo ($9/mo).

What you can do with it

Area	What Claude can do
Site	Ping the API and list the configured sites (health + which context is reachable)
Collections & entries	List collections, page through entries (with limit/page), sort, select fields, filter, and read one entry by id or slug
Entry trees	Fetch the entry tree of a structured collection
Navigations	List navigations and read a nav's tree
Taxonomies & terms	List taxonomy vocabularies and their terms, and read one term by slug
Globals	List global sets and read a single global set's variables
Forms	List forms and read one form's title and field definitions
Assets	List asset containers and the assets inside one container
Users	List users (when the users resource is enabled)

In plain terms: "What collections does the site have?" "List the last 20 blog entries." "Which taxonomy terms are already published?" The answers come straight from the Statamic Content REST API without opening the control panel.

How to connect it

Confirm your Statamic licence is Pro — the Content REST API is a Pro feature.
Set STATAMIC_API_ENABLED=true in your site's .env.
In config/statamic/api.php, enable each resource you want the agent to reach (collections, taxonomies, navs, globals, forms, assets, users, sites). All are disabled by default.
If you want filtering, opt fields into allowed_filters per sub-resource.
Set STATAMIC_API_AUTH_TOKEN to a long random string in your site's .env.
In Settings → Cogny Managed MCPs, click Connect on the Statamic card, paste the token and your site base URL (e.g. https://www.example.com).

One credential set per workspace. It's stored encrypted and sent as the Authorization: Bearer header to your site's Content REST API, scoped to your single Cogny workspace.

On trust

This integration is read-only by construction — Statamic's Content REST API has no documented public write endpoint, so there is no code path through which an agent could publish or edit entries. Every tool here is a GET against your site's already-served content. Components you haven't enabled in config/statamic/api.php are invisible to the agent and answered with a clear "not enabled" message rather than a generic failure.

Works with the Content Intelligence template

The Content Intelligence scheduled template now recognizes Statamic as a content-inventory signal. Where the template previously relied on Search Console's pages data to infer what content already exists, a connected Statamic site lets it call list_collections and list_entries directly for an authoritative inventory — while Search Console (or Google Ads keyword data) still drives the keyword-gap sizing itself.

Enable it from your warehouse Scheduled → + New scheduled prompt → Content Intelligence.

If your content lives in Statamic, this is the connector that puts your CMS inventory on the same footing as every other source in your Cogny workspace. Connect it from your Cogny dashboard and ask your first question.