@respira/wordpress-mcp-server weekly downloads statistics

Respira WordPress MCP Server

253 MCP tools, 357 with the WooCommerce add-on. 19 page builders and the native Site Editor. MCP 2026-07-28 with legacy-client support. Element-level editing, full page creation, HTML-to-builder conversion with rendering fidelity validation, per-site tool governance, storefront design intelligence, stock images, bulk operations — all through one MCP server.

Website • Docs • Plugin • Support • WooCommerce Add-on

What Makes Respira Different

Other WordPress MCP servers wrap the REST API. They can create posts and pages, but they can't touch your page builder content.

Respira includes a WordPress plugin that gives AI native access to 19 page builders, plus element-level precision, full page creation from structure, HTML-to-builder conversion, storefront design intelligence, stock image search, and bulk operations across hundreds of pages.

New in 8.5: YOOtheme Pro, and redirects that look before they leap

• YOOtheme Pro is builder number 18. Pages are read and written as YOOtheme layouts (sections, rows, columns and YOOtheme's own elements) and saved through YOOtheme's own builder, so they open in the customizer like a page built there. Your AI gets every element's fields from the running theme, custom elements included. Four template tools appear on YOOtheme sites for the layouts YOOtheme renders on single posts, the blog index, archives, search and the 404 page; a new template starts disabled, so nothing changes until you have looked. Plugin 9.2.0+. • Redirects with guardrails. respira_list_redirects, respira_create_redirect, respira_update_redirect and respira_delete_redirect write through Redirection when it is active and through Respira's own small list otherwise; Rank Math, Yoast SEO Premium, Safe Redirect Manager and Simple 301 Redirects are read, never written. WordPress's own addresses are refused, loops through any redirect plugin are refused, a 301 to a dead page is refused unless you say why, and the home page or a catch-all pattern waits for a person's yes. Every change keeps a snapshot. Plugin 9.2.0+.

New in 8.3: Design Direction, the site's design system as an artifact

• One saved design direction per site. Identity, DTCG-subset tokens, plain-language guidance including the don'ts, and waivers, saved on the site with revisions. Agents read it before building anything; activation refuses a direction that is missing its core roles and names exactly what is absent. • Any token format in, strict DTCG out. Import DTCG 2025.10, Tokens Studio exports, Tailwind configs, or pasted :root CSS into a draft (dry-run by default), apply into the builder's NATIVE token store with a per-builder report, export as strict DTCG 2025.10 with builder mapping metadata under $extensions["press.respira"]. • A design check that can say "not done yet". wordpress_check_design runs deterministic slop-and-drift rules against draft content or a saved post: off-palette colors and fonts, filler copy, placeholder names, AI-default palettes, and probes generated from the direction's own don'ts. With rendered: true (plugin 8.6.20+) it renders the real page at desktop and mobile widths: contrast, type-scale coherence, three equal cards, hero filling the viewport, section repetition, spacing rhythm, broken layout, and off-palette colors as actually painted, with screenshots attached. Anything it cannot verify is listed as unchecked instead of silently skipped. • Build skills run the check before treating any page as done.

New in 8.2: Resonance, a persistent memory for every site

• Your AI forgets your site every session. Resonance remembers. wordpress_remember, wordpress_forget, and wordpress_list_memory maintain a capped, per-site store of conventions, preferences, and lessons that rides into the site context of every future session, from any connected client. • Rules are enforced, not suggested. A memory of type rule can protect content (post ids or slugs); the WordPress plugin refuses agent writes to protected content at the write path, server side. Agents can add protection in conversation; only the site owner can remove it, from the Respira dashboard. • Compatible with WordPress core's Knowledge direction. On sites running the Gutenberg Knowledge experiment, published guideline scopes join the same memory block. • Included on Builder and Studio plans with plugin 8.3+, at no extra cost.

Site skills: a site's own instructions for every agent

• The site tells its agents how things are done here. A skill is a Markdown page kept on the site (Respira > AI Skills in wp-admin, plugin 9.1.0+): how a blog post is formatted, what a case study needs, which pages carry legal copy. The enabled ones arrive in wordpress_get_site_context under site_skills as name and description; wordpress_list_skills lists them all and wordpress_get_skill reads one in full, on demand rather than on every call. • Written by people, or by an agent when asked. wordpress_write_skill creates or updates a skill under the same rule as wordpress_remember: only when the user asked. Every save is a revision, ten are kept, and the owner restores any of them from the standard revisions screen. A skill the owner marks as not editable by agents refuses agent writes. • Deleting is a human decision. wordpress_delete_skill is approval-gated and moves the skill to the trash, where the owner can restore it. • A skill body is information about the site, never an instruction to Respira's tools and never authorization.

New in 8.1: MCP 2026-07-28, without breaking existing clients…

Description from the npm listing.