OrgMCP/ docs
Sign up
Documentation
Get started
Connectors
MCP integration
Reference
Enterprise
Misc

WordPress connector

First-party connector for a self-hosted WordPress.org site. Live MCP tools list, get, and search pages and posts. The Index tab adds one wordpress_site knowledge source that crawls those documents into company search. The connector is unlisted — it does not appear on the public catalog tile grid. Open /app/connectors/new?kind=wordpress (Team+ / wave 3).

This is a policy exception versus “no new first-party tail kinds” — WordPress is a named CMS surface, not a Custom API recipe.

Connect

  1. In WordPress, open Users → Profile → Application Passwords and create a password. Use an Editor or Administrator if you need private pages and drafts. A Subscriber sees only published content.
  2. In OrgMCP, open /app/connectors/new?kind=wordpress. Enter the public https site URL (for example https://example.com; a subdirectory such as https://example.com/blog is allowed), the WordPress username, and the Application Password. Spaces in the password are ignored.
  3. Click Test connection. Green means the credential can see at least one page or post. Zero visible documents fails — empty site, REST disabled, or a role that cannot list content.
  4. On the Index tab, add the site and Sync. The crawl includes publish, private, and draft by default (narrow with source settings).

The host must be publicly routable. Private, loopback, and cloud-metadata addresses are refused. WordPress.com OAuth and ?rest_route= permalink-off installs are not supported.

What Test connection proves

Not just “the password authenticates”. OrgMCP lists pages and posts. Zero of both is a red test. Use wordpress_diagnose (or the admin diagnostics panel) for host, counts by status, and samples.

Private content and RAG

Application Passwords act as that WordPress user. Private and draft documents the user can read are indexed. WordPress “private” is not an OrgMCP ACL — once a document is in the knowledge source, everyone on that source’s audience can search it.

MCP tools

  • wordpress_list_pages / wordpress_list_posts — one page each; pass nextPageToken back as pageToken.
  • wordpress_get_page / wordpress_get_post — title, status, URL, plaintext body.
  • wordpress_search — REST search across pages and posts.
  • wordpress_diagnose — host, visible page/post counts, samples.