| 开发者 | flavorswp |
|---|---|
| 更新时间 | 2026年10月18日 07:39 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
https://example.com/wp-json/mcp/flavors-engineMCP (Model Context Protocol) is the standard AI clients such as Claude, ChatGPT and Cursor use to work with outside tools. With an MCP server on your site, you can ask your AI client to write a page, build a header or tidy up your menus, and it does the work in WordPress instead of giving you code to paste.
Open Flavors Engine, then Connect. Choose your client and follow the OAuth sign-in, or create an Application Password for clients that cannot open a browser. Your site's MCP address is shown on that screen.
The default Production Safe profile blocks raw developer operations, and each tool also checks the connected user and site policy. Content writes can be allowed. Recorded undo covers specific operations with snapshot and conflict limits; permanent deletions and external effects are not universally reversible. Pro can hold configured actions for human review.
The local MCP server does not sell AI credits. Your external client or configured Chat provider can have its own fees and limits. Admin Chat records usage counts and can be limited by the configured site policy.
They use Elementor’s widget and template APIs. Check your installed Elementor version, required vendor features and other addons on a staging site before relying on a particular combination.
No. The MCP server is fully functional without it. Elementor is only needed for the widget library and theme builder.
This Free plugin needs no paid activation key. AI generation still needs model access through an external client or a configured admin Chat provider. That client/provider may require its own account, API key or paid plan.
Your external MCP client connects to the self-hosted site endpoint and receives the data returned by the requested tools. Optional admin Chat sends generation data to its configured provider through the WordPress AI Client. Optional Cloud pairing has its own disclosed data flow. Review those service settings and consent before use.
The Free package works without a paid licence. Pro is a separate add-on with additional widgets, site plans and advanced integrations; required vendor plugins and AI services are separate. See the Free/Pro comparison above.
Yes, Consent Mode v2, and it is off by default. Turn on "Google Consent Mode v2" in the widget's Google Consent Mode section and the widget sets the analytics, advertising and personalisation consent types to denied before your Google tags run, then sends an update when a visitor accepts, rejects or changes a category. These signals only reach Google tags you have already installed yourself (for example Google Analytics or Google Ads through Site Kit or Tag Manager). The plugin loads no Google script, contacts no Google server and tracks no one.