WebMCP Bridge

No. The REST API endpoints work in every browser and environment. The native WebMCP browser registration is only available in Chrome Early Preview (experimental), but the fallback JavaScript API ( window.webmcpBridgeTools ) and REST endpoints work everywhere.

Read-only tools (search, get post, Markdown, llms.txt) are publicly accessible by default, matching WordPress’s own REST API behaviour. Write-action tools (add to cart, apply coupon, submit form) require a logged-in session or a WordPress REST nonce from the same browsing session as the site (the nonce is printed on the page for the frontend bridge). There is no public /nonce endpoint. You can customise which tools require authentication via the webmcp_bridge_protected_tools filter.

Yes. Paste the MCP URL into Claude as a remote MCP server (Streamable HTTP):

https://your-site.com/wp-json/webmcp-bridge/v1/mcp

This is JSON-RPC ( initialize , tools/list , tools/call ), not OpenAPI. Optionally require a Bearer API key from Settings → WebMCP Bridge. Cart and form tools are omitted: they need a storefront session.

Yes. Import /wp-json/webmcp-bridge/v1/openapi as a GPT Action. The schema lists public read tools as separate POST operations under /wp-json/webmcp-bridge/v1/call/{tool} . Cart and form tools are omitted from that schema because GPT Actions run server-side and have no WooCommerce cookie session.

Yes. WooCommerce tools are automatically registered when WooCommerce is active and the WooCommerce option is enabled in settings.

When Mescio for Agents is active alongside WebMCP Bridge, three extra tools become available: retrieve (RAG search with snippets and Markdown URLs), get_markdown_content (full document as Markdown) and get_llms_txt (site-wide context). These are detected automatically — no configuration needed.

Yes, in the live-retrieval sense. Agents first read llms.txt , then call retrieve to find relevant pages, then get_markdown_content for the documents they need. There is no separate embedding index: WordPress remains the corpus, always up to date. Retrieval is full-text (WordPress search), not vector similarity.

WebMCP Bridge does not register /llms.txt . Rank Math’s LLMS Txt module and Mescio for Agents both do. From Mescio 1.7.4, if Rank Math’s module is on, Mescio yields /llms.txt to Rank Math and keeps /llms-full.txt . WebMCP’s get_llms_txt tool still reads Mescio’s generated index. To let Mescio own the public URL: Rank Math → Dashboard → disable LLMS Txt , then flush permalinks.

Absolutely. Use the PHP API:

add_action( 'plugins_loaded', function() { if ( ! class_exists( 'WebMCP_Bridge_Tool_Registry' ) ) return; $registry = WebMCP_Bridge_Tool_Registry::instance(); $registry->register( 'my_tool', [ 'description' => 'Does something useful.', 'group' => 'custom', 'inputSchema' => [ 'type' => 'object', 'properties' => [] ], 'callback' => function( $params ) { return [ 'ok' => true ]; }, ] ); } );

https://your-site.com/wp-json/webmcp-bridge/v1/manifest

OpenAPI (GPT Actions):

https://your-site.com/wp-json/webmcp-bridge/v1/openapi

MCP (Claude / MCP clients):

https://your-site.com/wp-json/webmcp-bridge/v1/mcp

You can also find both URLs on the Settings → WebMCP Bridge page with a one-click copy button.

No. WebMCP Bridge does not collect, store, or send any data to external servers. See the Privacy section above.