CMS Integrations
Semji connects natively to WordPress, Drupal, Contentful and Strapi, and to any other CMS through a custom MCP server or the Send to CMS webhook. A workspace owner connects once, and you decide what AI agents can read, create or update.
Which CMS platforms does Semji integrate with?
Four native connectors and two bring-your-own lanes. Connect once for the whole workspace — you decide what agents can read, create or modify.
WordPress
Connects over the WordPress REST API with an application password, from WordPress 5.6 — with Yoast SEO support.
Drupal
Connects through JSON:API with Basic Auth. Compatible from Drupal 8.7.
Contentful
One OAuth sign-in through Contentful’s hosted MCP server — no keys to copy.
Strapi
Connects to your instance’s MCP endpoint with an admin token. Compatible from Strapi 5.47.
Custom MCP server
Bring your own MCP server — a custom CMS bridge or an internal tool — and authenticate it with OAuth or an API key.
Send to CMS webhook
Semji posts each staged draft (content_staged) to your HTTPS endpoint, and your CMS answers with a review link — synchronously or through the tokenised callback.
How does a CMS connection work?
- 01
Connect from Settings → Integrations
A workspace owner connects the CMS once, from the CMS tab of Semji’s integration settings — the connection is then shared with the whole workspace. WordPress asks for three fields: the site URL, a username and an application password.
- 02
Choose what agents can do
Pick the tools AI agents may use on your site — on WordPress: create, read, list and update posts — each one individually toggleable, and changeable at any time.
- 03
Publish from Semji
An agent creates the optimized draft directly in your CMS and hands back the CMS ID with preview and back-office links. Nothing goes live until you ask it to publish.
The flagship connector
How does the WordPress + Yoast integration work?
Semji connects to WordPress through the REST API with an application password — generated in WordPress under Users → Profile — and works from WordPress 5.6. The site URL must start with https://, and Semji does not follow redirects.
On a site running Yoast SEO, the SEO title and meta description travel with the draft, so what you optimized in Semji is what WordPress serves.
- Create posts — always as a draft, unless an agent is explicitly asked to publish
- Read posts — fetch a post’s full content, as stored in the editor
- List posts — search and browse posts, with filters by status
- Update posts — change only the fields it edits: title, content, status
Frequently Asked Questions
What are the minimum CMS versions Semji supports?
WordPress 5.6, Drupal 8.7 and Strapi 5.47. Contentful connects through its hosted MCP server, with no version requirement to check. The custom MCP and webhook lanes depend only on your own endpoint.
How does each CMS connector authenticate?
WordPress uses an application password over the REST API. Drupal uses Basic Auth over JSON:API. Contentful signs in with OAuth through its hosted MCP server. Strapi takes an admin token on its MCP endpoint. A custom MCP server authenticates with OAuth or an API key, and the Send to CMS webhook secures its response with a tokenised callback.
What can AI agents do in my CMS once connected?
List, read, create and update posts — and you choose which of those tools are enabled, per integration, changeable at any time. New posts are always created as drafts unless you explicitly ask an agent to publish, and updates change only the fields being edited: title, content, status.
Does one connection cover my whole team?
Yes. A workspace owner connects the CMS once from Semji’s integration settings, and the connection is shared with the whole workspace. You decide what agents can read, create or modify.
What if my CMS is not in the catalog?
Two lanes work with any backend. A custom MCP server — a CMS bridge or an internal tool you run — connects with OAuth or an API key. The Send to CMS webhook has Semji post each staged draft (content_staged) to your HTTPS endpoint, and your CMS answers with a CMS ID plus a preview or back-office link, synchronously or through the tokenised callback.
Publish from Semji into the CMS you already run
Connect WordPress, Drupal, Contentful or Strapi in minutes, or bring your own lane over MCP or webhook. See the full loop — from optimized draft to CMS — in a demo.