CMS connectors

6 pre-built CMS connectors — 109 MCP tools in all: WordPress, Webflow, Contentful. Paste your credentials and your agent can call them. No MCP server to write.

// search the catalog
⌘K
6connectors
109total MCP tools
0No credentials
6
Filter
WordPress
CMS

AI-native publishing and content operations for any self-hosted WordPress site. Semantic tools for posts, pages, taxonomies, media metadata, users, comments, SEO meta and site health — plus documented multi-step recipes (SEO content pipeline, scheduled publishing, content refresh, internal linking, media optimisation).

38tools
Contentful
CMS

Let your AI work with your Contentful content: search entries and assets, read content types, locales and tags, and create, change, publish or unpublish entries. Delivery token for reads, management token for writes.

20tools
Directus
CMS

Connect to a Directus instance (self-hosted or Directus Cloud) to discover collections and fields, query items, and retrieve individual records through the read-only REST API.

5tools
Sanity
CMS

Let your AI work with your Sanity content: run GROQ queries, read documents, their revisions and change history, list document types, datasets and projects, and create, change and publish drafts after you confirm. API token with Viewer or Editor rights.

11tools
S5
Strapi 5
CMS

Connect to a Strapi 5 instance to check its availability, query documents from collection types, and retrieve individual documents through the read-only REST Content API.

3tools
Webflow
CMS

Let your AI work on a Webflow site: read the site, its pages and SEO settings, CMS collections and items, forms and submissions, assets, and e-commerce products and orders; draft and update CMS items, and publish items or the whole site once you agree. Uses a site API token.

32tools

Browse by category

All 6 connectors, A–Z
Contribute/~30 min

Missing a connector? Add it in a JSON.

Every adapter is a single JSON file under packages/backend/src/adapters/. Copy one, swap endpoint and auth, open a PR — validated by parameterized tests at build time.

// adapters/de/my-adapter.json
{
  "slug": "my-erp",
  "name": "My ERP",
  "category": "erp",
  "authType": "BEARER_TOKEN",
  "tools": [/* ... */]
}