MODX MCP Server & AI Connector
The Model Context Protocol is the open standard assistants use to reach outside tools. MODX AI Agent acts as an MCP server for your MODX site: the assistant asks it for a capability, it checks what you have authorised, and only then does it touch your site. This page covers the technical side for MODX.
Where this one stands
MODX exposes its content through its own connectors rather than a documented public API, so an Extra of our own would have to provide the interface first.
Authentication and permissions
The assistant authorises through OAuth 2.1 with PKCE, and is granted scopes rather than an open door. Your MODX credential is encrypted at rest, tied to the one website it belongs to, and never sent to the assistant. Every operation is recorded, and an operation outside what you granted is refused before it reaches your site.
Common questions
What is an MCP server, in plain terms?
A service an AI assistant can call to do real work. Rather than describing a change to you, the assistant asks the server to make it. MODX AI Agent is that server for MODX, and the boundary of what it will do is set by what you authorised.
Does the assistant see my MODX password or token?
No. The credential is encrypted and bound to the single website it was given for, so a copy of it elsewhere is useless. The assistant asks for an action; it never receives the way in.
Is this an official MODX product?
No. MODX AI Agent is an independent product that uses MODX’s own published interfaces. It is not affiliated with or endorsed by MODX.
Getting started with MODX AI Agent
MODX AI Agent is not on sale yet. The product page tracks where it stands, and nothing is advertised before it works.