Mantle is a WordPress plugin by Linchpin that streamlines site administration. It bundles sixteen modules — caching, monitoring, security hardening, user and capability management, plugin synchronisation, single sign-on, an AI chatbot, and more — behind one React-based admin dashboard and one versioned REST namespace.

WordPress administration toolkit

One plugin, sixteen modules, one admin surface

Mantle gives every Linchpin-managed site the same administration layer regardless of host: unified cache clearing, uptime and performance monitoring, capability management, and a modular architecture you can extend without forking.

github.com/repo

docs/

index.mdquickstart.mdapi.md

DocsPresskeeps one source

For readersWordPress PagesNative Gutenberg

For agents/llms.txtExact page.md routes

Reviewable pull requestWordPress edits return to GitHub

Where to start

Install and configure Mantle

Requirements, installation, the setup wizard, and the settings that control each module.

Build or extend a module

Operate and troubleshoot

WP-CLI commands, the REST surface, capability synchronisation, and how to diagnose a module that is not loading.

Getting started — requirements, installation, and configuration.
Guides — module management, extending the admin UI, and writing your own module.
Reference — REST API, WP-CLI, capabilities, settings keys, abilities, constants, hooks, and SlotFills.
Architecture — how the bootstrap, module loader, and admin UI fit together.
Troubleshooting — diagnose common failures.

What Mantle does

Mantle replaces a pile of per-site snippets and single-purpose plugins with one modular system. Each capability is a module: a self-contained unit that registers its own settings schema, capabilities, REST controllers, and admin UI, and that can be switched on or off per site.

Modules register their settings and capability schemas even when disabled; only enabled modules initialise and register REST routes.

The practical consequence of that flow: a disabled module still contributes its settings keys and capability definitions, so stored values are never orphaned and the capability reference stays complete. Only its behaviour and REST routes go away. See Architecture for the detail.

Modules at a glance

Three modules are core and cannot be disabled. The remaining thirteen are functional and are toggled per site.

Module ID	Type	Purpose
`client_info`	core	Client contact and branding details
`dashboard`	core	The Mantle dashboard view
`welcome`	core	Setup and welcome experience
`ai_chatbot`	functional	AI assistant backed by the WordPress Abilities API
`communication`	functional	Slack chat channels and messaging
`convergence_cache`	functional	Unified cache clearing across hosts and CDNs
`linchpin_licenses`	functional	Linchpin product licence visibility
`maintenance`	functional	Maintenance mode
`monitoring`	functional	StatusCake uptime, PageSpeed, and SSL monitoring
`optimizations`	functional	Front-end and admin cleanup toggles
`plugin_sync`	functional	Plugin and theme inventory reporting and remote commands
`security`	functional	Security hardening controls
`site_code_snippets`	functional	Global header, body, and footer snippets
`sso`	functional	Single sign-on with role mapping
`user_management`	functional	Role and capability management
`white-label`	functional	Login and admin branding

Full metadata, including each module's capabilities and settings keys, is in the module reference.

Requirements

WordPress string required: Requires at least 7.0. Tested up to 7.0.

Values7.0+
PHP string required: Plugin header declares 8.0 as the minimum. Composer constrains the package to ^8.0 || ^8.2.

Values8.0+
Composer string: Needed for development and to build the autoloader from a source checkout. Not needed for a packaged release zip.
Node.js string: Needed only to build the admin interface from source via npm run build.

Mantle relies on WordPress 7.0's bundled PHP AI Client for its AI features. When a copy of that library is also present in the plugin's own vendor/ directory — for example after installing dev dependencies — mantle.php unregisters the plugin's PSR-4 prefix so core's copy wins and the two cannot conflict.

Licence

GPL-2.0-or-later. Source and issue tracker: github.com/linchpin/mantle.

Mantle