Skip to main content
Connect your CMS to let Semji’s AI agents work directly on your content — list and read what’s there, create new drafts, and update existing pages. Each integration is connected once by a workspace owner from Settings → Integrations and is typically shared with the whole workspace (custom MCP servers can also be connected per user).

WordPress

Connect with an application password over the WordPress REST API. Compatible from WordPress 5.6.

Drupal

Connect through JSON:API and Basic Auth. Compatible from Drupal 8.7.

Contentful

One-click OAuth through Contentful’s hosted MCP server — no keys to copy.

Strapi

Connect your instance’s MCP endpoint with an admin token. Compatible from Strapi 5.47.0.

Custom MCP server

Bring your own MCP server — a custom CMS bridge or internal tool — via OAuth or an API key.

Send to CMS webhook

Semji posts each draft to your endpoint when an editor clicks Send to CMS; you place it and return a review link, synchronously or via a callback.

​
At a glance

Behind a firewall or WAF? Semji’s requests can be blocked before they reach your CMS — the most common cause of failed connections. Each guide above has a dedicated network section explaining what, if anything, to allow — including Semji’s outbound IP addresses.

​
Push content to your CMS yourself

If you’d rather push content to your CMS instead of letting Semji’s agents work on it directly, two options work with any backend:
  • Send to CMS webhook — Semji posts a draft to your endpoint when an editor clicks Send to CMS; you place it and return a review link, synchronously or through a callback.
  • Sync drafts to your CMS — an API-based publishing flow you drive on a schedule.