| 开发者 | themesic |
|---|---|
| 更新时间 | 2026年10月19日 13:56 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
document.modelContext (with fallbacks)./wp-json/themesic-agent/v1/manifest, /execute and /openapi - for any HTTP agent and for Custom GPT Actions, plus RFC 8288 Link discovery.themesic_agent_register_tools) - no core files need editing. Custom tools get the same security gate, validation, rate limiting and delivery surfaces as the built-in ones. Hooks are also provided for adding REST routes, resolving a caller's identity, narrowing which tools are allowed, and extending the admin screens.
Privacy
This plugin makes no external calls at all. Every tool runs inside your WordPress install, nothing is sent anywhere on activation or afterwards, and the optional activity log stores recent tool calls with no personal data (and can be cleared or turned off). There is no account, no licence check and no telemetry.
A separate paid add-on exists
The author also sells a separate commercial plugin that adds write tools (cart, checkout, orders), a server-side MCP endpoint, per-agent API keys and integrations with other plugins. It is a different plugin, sold and distributed from the author's own website.
It is not part of this package, in whole or in part. Its code is not here, switched off or otherwise; nothing in this plugin downloads, installs or checks for it; and nothing anyone can buy changes what the files in this package do. Everything described above works on its own and always will.
No. The REST and OpenAPI endpoints work everywhere. The in-page WebMCP registration lights up automatically in browsers that support it; every other agent uses the REST API.
Read tools for public content are public, in the same way WordPress' own REST API is. Write tools require a same-session nonce, and tools that touch an account require a real login - a nonce alone is never treated as one. You control exactly which tools are exposed, denied attempts are logged, and rate limiting is applied before the permission check so failed guesses still cost the caller quota.
No. WooCommerce tools appear only when WooCommerce is active; on a plain WordPress site they are hidden entirely.
Not through this plugin. Every tool it registers reads public content. The engine supports write tools because custom and third-party tools can register them, and it holds those to a stricter standard - a same-session nonce, and a real login for anything touching an account.
No. This plugin contacts nothing. The tools run inside your WordPress install, there is no telemetry, no licence check and no call home - not on activation, not later. See the Privacy section.
Yes, with a documented PHP API (themesic_agent_register_tools) - no core files need editing. Custom tools get the same security gate, validation, rate limiting, and all delivery surfaces.