Skip to content

AI Chat

New in v3.1.0. Pro. AI Chat isn’t just a chat window bolted onto WordPress, it’s an AI agent that lives inside your editor and can actually build. It shows up two ways: an admin AI Chat tab for general conversations, and a floating panel (with a chat-bubble launcher) inside both the Elementor editor and the WordPress block editor, scoped to whatever page you’re currently editing.

Turning the module off is a true kill switch: the tab, both editor panels, the REST routes, and the cron all stop.

Hosted providers: Anthropic (Claude), OpenAI, OpenRouter, Google Gemini, DeepSeek, Moonshot, and Z.ai. Add your API key on the AI Chat admin tab. Keys are encrypted at rest per user (AES-256-GCM, authenticated) and are only ever sent to the provider you chose, never to EMCP’s own servers.

Local runtimes (v3.5.1): Ollama and LM Studio are auto-detected, no API key at all, your prompts and page content never leave the machine running the model. Useful for privacy-sensitive sites or just avoiding hosted-API cost.

A refresh-models button pulls a provider’s current model list on demand, so a newly-installed local model shows up without reconnecting. Your last provider/model selection is remembered across reloads instead of resetting to the default each time. If the selected model has no vision support, images are handled two ways: a local vision model (private, if one’s configured) or a built-in, dependency-free image reader as a fallback.

The chat has tool-calling access to the same MCP tools an external agent like Claude Desktop would use, discovery, page building, widgets, globals, templates, and more. To keep the per-turn request small, it doesn’t advertise all 238+ tools at once: a lean core set (~35 tools covering discovery, pages/layout, widgets, globals/templates) is always available, and the model pulls in additional tool groups on demand via a load_tools meta-tool as the conversation needs them. Every tool call still goes through the same permission checks as an external MCP client, the chat has no special privilege.

New in v3.2.0. The chat’s model can read a URL you give it: a reference design, a competitor page, documentation, a JSON endpoint, or a stylesheet.

  • format: "text" (the default) returns the page’s readable text, cheap, and usually all you need.
  • format: "html" returns sanitized markup including the <head>, when the model needs class names to reason about layout.
  • Fetching an HTML page also returns a stylesheets array of absolute CSS URLs. Ask the AI to read one, and it lifts the design’s color tokens and type scale straight from source, far cheaper and more accurate than inferring them from a rendered page.

It cannot search the web: you have to give it a URL. Only text is readable (HTML, CSS, JSON, XML, Markdown, plain text). Images, fonts, and scripts are refused.

EMCP Tools → AI Chat: a full-page conversation view with a provider/model picker and a conversation sidebar for switching between past chats. Good for general questions or work that isn’t tied to one specific page.

EMCP Tools → AI Chat admin screen with the conversation sidebar and provider/model picker

A floating window and chat-bubble launcher appear in the Elementor editor’s footer. The panel shares the same chat engine and config as the admin tab, plus embed context: the current page’s id and a page-context sentence, so the model already knows what you’re editing without you explaining it.

Elementor editor with the AI Chat floating panel and chat-bubble launcher open

Same floating-window treatment, in the WordPress block editor’s admin footer, with block-editor embed context (current post id) instead of Elementor’s.

WordPress block editor with the AI Chat floating panel open

Both editor panels require edit_posts and only load on their respective editor screens. The admin tab and API key management require Pro plus the capability to manage the plugin’s settings.