Expose custom post types to WebMCP (Pro)

RankReady publishes a WebMCP manifest at /.well-known/mcp.json, which is how an AI agent discovers what it can read on your site. Free exposes posts and pages. Pro lets you choose any public post type.

Why the split exists

Posts and pages cover almost every blog, and they are exposed in Free permanently. Choosing among arbitrary post types is an agency and WooCommerce concern: product catalogues, documentation libraries, portfolios, custom directories. That picker is the Pro surface.

Using it

1. Open the AI Visibility screen, WebMCP section.
2. With Pro licensed, the post type picker is editable. Select the public post types you want exposed.
3. Save, then fetch /.well-known/mcp.json and confirm the new types are listed.

Verify by reading the manifest, not by trusting the checkbox. That is the only check that proves the output changed.

Choose deliberately

Exposing a post type tells agents that content is there to be read. That is what you want for products and documentation. It is not what you want for internal post types that happen to be public, or for anything thin, templated or half-finished. Expose what you would be pleased to be quoted on.

Your settings survive

The underlying option is owned by the free plugin, which means your selection is registered, saved and read by the free base. If Pro is ever deactivated, the setting is not destroyed; the picker simply becomes read-only again while the manifest falls back to the Free default of posts and pages.

If the manifest will not load

A 403 on /.well-known/mcp.json is almost always an nginx server-configuration issue rather than a plugin one, and no plugin release can override it. See /.well-known/mcp.json returns 403 on nginx.

Related

How to add a WebMCP manifest, Agent discovery (Pro), which lists the manifest in a standard catalog once it is switched on.