

Dashboard: recent AI activity, connected clients and tool status at a glance.
EMCP Lite, the free edition of EMCP Tools, lets your AI assistant design pages on your site, not just write posts. Ask Claude, ChatGPT, Cursor or Claude Code to “build a pricing page in our brand colors”, and it lays out the page with Elementor containers and widgets or block editor blocks and patterns, using your brand kit.
It works by turning your site into a WordPress MCP server through the Model Context Protocol (MCP), the open standard AI assistants use to work with external tools. The same tools handle everyday work too: drafting posts, organizing media and updating menus.
Every request acts as the connected WordPress user, within that user’s permissions and only through the tools you enable. Changes are logged, and supported changes can be undone from History.
Turn modules on or off on the Modules screen. All of these are included in EMCP Lite:
EMCP Lite registers 165 tools as WordPress abilities through the Abilities API, and also exposes three read-only WordPress core abilities (site, user and environment info). Tools for Elementor, block plugins, themes and integrations appear only when that product is active, and a few Elementor widget and template tools also need Elementor Pro. Browse every tool in the EMCP tool catalog, which also lists tools from other EMCP editions.
WordPress (37 tools)
Elementor (64 tools)
Block editor (32 tools)
Themes (5 tools)
Plugin integrations (21 tools)
History and safety (6 tools)
EMCP Lite does not install, update or remove plugins or themes, manage users, change site settings or run custom code.
EMCP Lite uses the free, official MCP Adapter plugin from WordPress.org to provide the MCP endpoint. If it is not active yet, EMCP Lite shows a notice with a one-click button that installs and activates it for you.
The Connection screen then guides you through setup for Claude Desktop, Claude.ai, Claude Code, Cursor, ChatGPT, Antigravity and other MCP clients, using OAuth sign-in or a WordPress Application Password.
Walkthroughs from the EMCP community:
Build a full site without opening the Elementor editor
Use EMCP with open models such as DeepSeek, Kimi and MiniMax
Build Elementor websites with Claude Code
Build a website with Claude and Elementor
Design Elementor pages with Claude Code
Step-by-step guides are on the EMCP documentation site:
The documentation covers every EMCP edition, so some pages describe tools that EMCP Lite does not include.
Elementor is optional: the WordPress and Gutenberg tools work without it, and some integrations need their respective plugins. EMCP Lite is independently developed and is not affiliated with WordPress, Elementor, Anthropic or OpenAI.
EMCP Lite does not send data anywhere until you connect an AI client or enable an optional service.
AI clients. A direct MCP connection communicates only with the AI client you choose. The client receives the results of the tools it calls, which can include site content or personal data the connected WordPress user can access. Check your AI client’s privacy policy before connecting it. Activity and History records are stored on your own site.
EMCP Cloud (optional). Local tools work without a Cloud account. Choosing Connect sends your site URL, site name, an installation identifier and OAuth registration and authorization details to emcptools.com. Once connected, the plugin exchanges and refreshes tokens, including a background renewal about once a week so an idle site stays connected, and can request account and service status. Settings sync sends supported EMCP preferences, including tool toggles, modules and your free-text site context. Credentials are excluded, but site-context text is not redacted, so do not put passwords or API keys in it. Hosted services may require a paid plan. A developer or administrator can configure a different Cloud endpoint.
Gateway access (optional). Gateway is a separate opt-in that is off by default. Enabling it creates a revocable EMCP OAuth token for the authorizing WordPress user and sends it to the EMCP service. It does not send a WordPress password or Application Password. The token works only on the EMCP MCP endpoint, not wp-admin, the WordPress REST API or EMCP settings. Gateway requests act as that user, within the enabled tools and that user’s permissions, and can include write operations. Gateway relays MCP requests and responses, including any content or personal data the selected tools return. You can turn off Gateway and disconnect Cloud on the Connection screen at any time.
Stock photos (optional). Unsplash, Pexels and Pixabay are contacted only after you add that provider’s API key and request a search or download. Requests send your API key, search terms and selected image identifiers, and images are downloaded from the provider’s servers. Unsplash download notifications are sent when its API requires them. Provider terms and image licenses apply:
Other requests. When you click Install and activate MCP Adapter, the plugin is downloaded from WordPress.org. Plugin and theme search uses the WordPress.org API, sending your search terms and page number. When a security check runs, it looks up your installed plugins’ slugs on the WordPress.org API to compare versions. Page inspection and media import tools request only the URLs you provide or select. Tutorial videos open on YouTube only when you click them; their thumbnails are bundled with the plugin.
The full source code, including the uncompressed admin interface source in the admin-src folder, ships with the plugin and is available on GitHub.
To rebuild the admin scripts, run npm ci and then npm run build with a current Node.js LTS release. Composer dependencies are included in the vendor folder, with composer.json and composer.lock.
Bundled libraries:
License notices are included in the assets/licenses, assets/fonts and assets/lib/swiper folders.