ExpressionEngine MCP Server & AI Connector
The Model Context Protocol is the open standard assistants use to reach outside tools. ExpressionEngine AI Agent acts as an MCP server for your ExpressionEngine 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 ExpressionEngine.
Where this one stands
ExpressionEngine channel entries are reachable in principle, but not through an interface documented well enough to build on without a live installation to check against.
Authentication and permissions
The assistant authorises through OAuth 2.1 with PKCE, and is granted scopes rather than an open door. Your ExpressionEngine 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. ExpressionEngine AI Agent is that server for ExpressionEngine, and the boundary of what it will do is set by what you authorised.
Does the assistant see my ExpressionEngine 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 ExpressionEngine product?
No. ExpressionEngine AI Agent is an independent product that uses ExpressionEngine’s own published interfaces. It is not affiliated with or endorsed by ExpressionEngine.
Getting started with ExpressionEngine AI Agent
ExpressionEngine AI Agent is not on sale yet. The product page tracks where it stands, and nothing is advertised before it works.