Connettori CMS

6 connettori pronti all'uso nella categoria CMS — 109 strumenti MCP in totale: WordPress, Webflow, Contentful. Inserisci le credenziali e il tuo agente può richiamarli. Nessun server MCP da scrivere.

// cerca nel catalogo
⌘K
6connettori
109tool MCP totali
0Senza credenziali
6
Filtra
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).

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

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

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

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

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

32tool

Sfoglia per categoria

Tutti i 6 connettori, dalla A alla Z
Contribuisci/~30 min

Manca un connector? Aggiungilo in un JSON.

Ogni adapter è un singolo file JSON in packages/backend/src/adapters/. Copia un esistente, sostituisci endpoint e auth, apri una PR — validato dai test parametrizzati al build.

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