| 开发者 | fgelio |
|---|---|
| 更新时间 | 2026年9月28日 18:24 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 or later |
| 版权网址: | 版权信息 |
define('ELIODATA_SNIPPET_HUB_SAFE_MODE', true); to wp-config.php to stop running all snippets.[readonly] in the password name to block every write request made with it.No. Eliodata MCP Bridge includes its own native snippet engine.
Yes. The plugin exposes generic MCP endpoints and works with compatible IDE companions such as VS Code, Trae, and similar tools.
Yes. Custom MCP tools are stored per WordPress site, so every connected site can expose its own actions and schemas.
Yes, when used with standard WordPress security practices and Application Passwords. Test new snippets on a staging site first.
A snippet that causes a fatal error is deactivated automatically and the error is shown in the admin. If the site is still unavailable, add define('ELIODATA_SNIPPET_HUB_SAFE_MODE', true); to wp-config.php: no snippet runs, and you can fix or deactivate the snippet from the plugin screens.
Snippets that target all content now run on init, also during REST API, cron and AJAX requests. Call conditional tags such as is_page() inside a hook, and check the permission_callback of REST routes declared in snippets. To keep the previous timing, add define('ELIODATA_SNIPPET_HUB_LEGACY_TIMING', true); to wp-config.php.
Non. Eliodata MCP Bridge intègre son propre moteur natif.
Oui. Le plugin expose des endpoints MCP génériques et fonctionne avec des extensions IDE compatibles comme VS Code, Trae et outils similaires.
Oui. Les outils MCP custom sont stockés par site WordPress, ce qui permet à chaque connexion IDE d’exposer ses propres actions et schémas.
Oui, en appliquant les bonnes pratiques WordPress et les mots de passe d’application. Testez les nouveaux snippets sur un site de recette.
Un snippet qui provoque une erreur fatale est désactivé automatiquement et l’erreur est affichée dans l’administration. Si le site reste indisponible, ajoutez define('ELIODATA_SNIPPET_HUB_SAFE_MODE', true); dans wp-config.php : aucun snippet ne s’exécute et vous pouvez corriger ou désactiver le snippet depuis les écrans du plugin.
/mcp/tools, /mcp/call)./mcp/custom-tools.[readonly] to the password name: every write request made with it is refused on the whole REST API (not only the plugin routes), and XML-RPC is blocked.define('ELIODATA_SNIPPET_HUB_SAFE_MODE', true); to wp-config.php to stop running snippets./ide/v1/ routes, so a broken snippet can always be fixed.init on every request, including REST API, cron and AJAX requests. Snippets that target post types or specific posts still wait for the main query on the front end. Conditional tags such as is_page() must be called inside a hook. To keep the previous timing, add define('ELIODATA_SNIPPET_HUB_LEGACY_TIMING', true); to wp-config.php.eliodata-snippet-hub), instead of a temporary file on every request.manage_network_options capability (super admins). Filterable with eliodata_snippet_hub_required_capability.eliodata_snippet_hub_manage capability, filterable via eliodata_snippet_hub_api_capability and eliodata_snippet_hub_mcp_capability.code_b64) to avoid transport issues with special characters.