Wagtail MCP
OfficialProvides tools to interact with a Wagtail CMS instance, enabling agents to read content, create pages, upload images, publish and revert changes through the Wagtail v3 API.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Wagtail MCP
🚧🤖 this is an early vibe-coded prototype of an MCP server for Wagtail. Proceed with caution! Until this is ready, you might prefer to use the wagtail-cli. See CMS with AI, not AI CMS: Wagtail 8.0’s new API for context.
A Model Context Protocol (MCP) server for Wagtail, exposing the Wagtail v3 API operations as model-callable tools.
Capabilities
60 curated tools covering the full shipped v3 operation surface: pages (incl. revisions, move/copy/revert, aliases, translations), images, documents, snippets, redirects, sites and locales — plus
api_call/api_schema, an OpenAPI-backed escape hatch for anything else.In-process dispatch — tools call the mounted v3 API inside the process via Django's test client, so auth, permissions, validation and action logic are the real thing. No network hop, no half-reimplemented client.
Bearer-token auth with Wagtail
APIToken; the v3 API stays the single authority for authorization.Stateless Streamable HTTP — a Django view that works under WSGI and ASGI, with no extra processes.
Related MCP server: WordPress MCP Server
Quickstart
wagtail-mcp is a Django app: add wagtail.api.v3 and wagtail_mcp, mount
/api/v3/ and /mcp/, create an API token, point a client at /mcp/. See the
full getting started.
Point a remote MCP client at the endpoint:
{
"mcp": {
"wagtail": {
"type": "remote",
"url": "http://localhost:8000/mcp/",
"headers": {
"Authorization": "Bearer <your-api-token>",
"Content-Type": "application/json"
}
}
}
}Try the demo
The repo ships demo/, a Wagtail site that mounts both the API and the MCP
endpoint and seeds a demo token:
just demoThen use demo/'s token (see demo/README.md) in your client config. The
editorial scenario test is a complete
worked example an agent can follow.
Documentation
Using the package: docs.
Changing the package: contributing.
Supported versions
This package supports Wagtail 8.0 and up (the v3 API preview), Django 5.2/6.0, and the compatible Python versions.
Development
Install dependencies, run the tests, lint, and run the demo (asgiref.sync
handles the transport, so just test and just lint are the normal gates):
just install
just test
just lint
just demoSee CONTRIBUTING.md for setup, tests, and releases.
This server cannot be deployed
Maintenance
Related MCP Connectors
Draft, edit, organise, schedule and publish a Writavo Site's content from any AI assistant.
Manage your WordPress site from your AI assistant: posts, pages, media, comments and WooCommerce.
Find, write, publish and check pages and API references in your DeveloperHub docs from an AI client
Manage WordPress blogs and WooCommerce shops from Claude, ChatGPT, Cursor and other MCP apps.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage WordPress sites via ~74 capabilities including content, media, plugins, themes, and more.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage WordPress content (create, retrieve, update posts) via the WordPress REST API with secure authentication.3 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage WordPress posts, pages, media, taxonomies, comments, users, settings, and custom fields through the WordPress REST API. Supports secure authentication, OAuth deployment, search, and safe write controls.MIT
- AlicenseBqualityCmaintenanceEnables AI agents to read and edit a Django site's content over its API, creating tools at startup from whatever resources the site registers so no code changes are needed. Works with any site running django-agent-content, with HTTPS-only API key authentication and no delete operations.1246 PyPI3MIT