Get the plugin
WP MCP/Integrations/Operations

Operations integration

Relevanssi MCP

WP MCP adds five free Relevanssi ops on the theme dispatcher pair, so it adds no new tools. get-relevanssi-settings returns the search and indexing settings from an allowlist: operator, fuzzy matching, weights, indexed post types, excerpts, highlighting and logging. get-relevanssi-index-status says whether the index is built, with the document and term counts Relevanssi keeps and a live count of documents and rows in its index table. list-relevanssi-top-searches reads its search log aggregated per query (how often, the most results, when last), never user ids or IP addresses, and masks any query that holds an email address or a phone-length run of digits; zero_hits:true lists the searches that found nothing. rebuild-relevanssi-index runs Relevanssi's own indexer, the same as its Build the index button. The index is rebuilt from the posts, so this op is not snapshotted and needs confirm:true after a preview of how many documents it empties. update-relevanssi-settings changes an allowlist of settings, each validated by kind, snapshots the touched options as one undo point and says when the change needs a rebuild. Logging visitor IP addresses is not writable. Settings writes are off until a site opts in with the wpmcp_enable_search_write filter, and every op needs manage_options.

theme-readtheme-write

What your AI can do

Real Relevanssi operations, every write reversible.

  • Read the Relevanssi search and indexing settings
  • Check whether the index is built, with document, term and row counts
  • List the top searches, or the searches that found nothing, with personal data masked
  • Rebuild the index with Relevanssi's own indexer (confirm:true)
  • Change search settings such as fuzzy matching, weights and indexed post types (opt-in)
  • Roll a settings change back with rollback-operation

Example prompts

Example Relevanssi prompts.

Is the Relevanssi index built, and how many documents are in it?

What did visitors search for this month that found nothing?

Turn fuzzy matching on always and boost titles to 10, then tell me if I need a rebuild.

Under the hood

The Relevanssi calls, under the hood.

wpmcp, relevanssi

theme-read({ operation: "list-relevanssi-top-searches", args: { days: 30, zero_hits: true } }), aggregated per query; emails and long digit runs masked

theme-write({ operation: "update-relevanssi-settings", args: { settings: { fuzzy: "always", title_boost: 10 } } }), opt-in; snapshotted as one undo point

theme-write({ operation: "rebuild-relevanssi-index", confirm: true }), derived data; not snapshotted

In the free plugin

The Relevanssi integration is in the free plugin.

The core Relevanssi tools ship in the free, GPL plugin with the full snapshot and undo engine, and no trial clock. Pro adds 133 more tools, including Elementor deep editing, the other page builders, the forms adapter pack and, for some integrations, extra operations. The pricing page lists what each tier includes.

Frequently asked

Relevanssi MCP: questions, answered.

With Relevanssi, can the agent see who searched for what?

No. Top searches are grouped per query with a count, the most results and the last time, and user ids, IP addresses and session ids are never selected. A query that holds an email address or a phone-length number is masked, and the answer says masked:true.

Why is the index rebuild not reversible?

The index is derived data that Relevanssi builds from your posts, so there is nothing to restore: running the rebuild again gives the same result. That is why it is not snapshotted and needs confirm:true, with a preview of how many documents it empties first.

Which settings can it change?

An allowlist of toggles, choices and numbers, among them the default operator, fuzzy matching, title, content and comment weights, indexed post types, excluded posts, excerpts, highlighting and query logging. Each value is checked before anything is saved. Logging visitor IP addresses is deliberately not writable.

Point your AI at Relevanssi.