メインコンテンツまでスキップ

FAQ & Troubleshooting

Frequently asked questions​

Do I need Chrome or a special browser?​

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.

Is it secure?​

Yes. Read tools for public content are public, like WordPress' own REST API. Write tools require a logged-in session and a same-session nonce. You control exactly which tools are exposed. See the security model.

Does it require WooCommerce?​

No. WooCommerce tools appear only when WooCommerce is active. On a plain WordPress site they are hidden entirely.

Does it send my data anywhere?​

MCPify's tools do not: no telemetry, everything runs inside your WordPress install. The one exception is the optional Pro upgrade, which bundles the Freemius SDK for licensing and updates (it contacts freemius.com); that usage tracking is opt-in and the free tools need no account.

Do I need Composer or a build step?​

No. MCPify is plug-n-play: upload the ZIP, activate, done.

Can developers add their own tools?​

Yes, with a documented PHP API (mcpify_register_tools) - no core files need editing. See the developer guide.

Troubleshooting​

The MCPify menu does not appear​

  • Confirm the plugin is activated under Plugins.
  • The admin screens require the manage_options capability - log in as an administrator.
  • Check that your site meets the requirements: WordPress 6.4+ and PHP 8.1+.

WooCommerce tools are missing from the manifest​

WooCommerce tools only register when WooCommerce is active. Activate WooCommerce, then reload the manifest. If they are still missing, check that the woocommerce group is not disabled in MCPify > Settings.

A tool is missing from the manifest​

  • It may be disabled in MCPify > Tools, or its whole group may be disabled in Settings.
  • The master switch in Settings may be off.
  • Pro-only tools (cart, checkout, orders, CPT) require the Pro edition.

A write tool returns a permission error​

Write tools require both a logged-in session and a valid X-WP-Nonce. If you call over REST:

  • Ensure you send session cookies for a logged-in user.
  • Ensure the X-WP-Nonce header carries a fresh wp_rest nonce.
  • Anonymous requests cannot use write tools by design.

Calls are being rejected with a rate-limit error​

You have hit the per-caller or global rate limit. Raise the limits in MCPify > Settings, or slow the agent's call rate.

An agent cannot discover the tools​

  • Confirm the manifest loads: https://your-site/wp-json/mcpify/v1/manifest.
  • For OpenAPI clients, point them at /wp-json/mcpify/v1/openapi.
  • Some security plugins or CDNs block /wp-json/. Allow the mcpify/v1 namespace if REST is otherwise restricted.

Still stuck?​

Open the Playground (MCPify > Playground) and run the tool directly - the raw request and response usually show the cause. If not, contact support.