Conectores de CMS

6 conectores de CMS listos para usar — 109 herramientas MCP en total: WordPress, Webflow, Contentful. Pega tus credenciales y tu agente podrá llamarlos. Sin servidor MCP que escribir.

// buscar en el catálogo
⌘K
6conectores
109herramientas MCP totales
0Sin credenciales
6
Filtrar
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).

38herramientas
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.

20herramientas
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.

5herramientas
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.

11herramientas
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.

3herramientas
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.

32herramientas

Explorar por categoría

Los 6 conectores, de la A a la Z
Contribuir/~30 min

¿Falta un conector? Agrégalo en un JSON.

Cada adaptador es un único JSON en packages/backend/src/adapters/. Copia uno existente, cambia endpoint y auth, abre un PR — validado por tests parametrizados en build.

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