Flatsome MCP server, with undo on every edit.
A Flatsome MCP server lets Claude, ChatGPT or Cursor read and edit Flatsome UX Builder pages on a live WordPress site, shortcode by shortcode, product grids included. With Respira every edit lands on a copy first, and you can undo it for 90 days.
7 days free. No card. Runs on the AI subscription you already have.
- Support
- Full
- Flatsome tools
- Core set
- Latest release touching it
- mcp-8.7.2
- Releases touching it
- 25
Respira is an independent MCP server. Not affiliated with, endorsed by, or sponsored by UX Themes / Flatsome.
What works today. What still needs you.
Read from the current MCP server release, first-class reads and writes across the builder structure.
Works now
- Flatsome UX Builder shortcodes parsed with full attribute preservation and nesting support.
- Per-element writes via the standard find/update flow work on rows, columns, sections, banners, sliders, and product-related elements.
- WooCommerce category, product, and shop-page edits work through the standard Woo addon tools alongside Flatsome layouts.
- UX Blocks, the reusable blocks Flatsome uses for headers, footers and mega menus, are posts of the
blockstype and go through the same shortcode reads and writes, by post ID. - Custom CSS at theme level (
flatsome_options[custom_css]) and per-page level are both writable.
Where a human still steps in
- Flatsome Studio, the library of ready-made layouts inside the UX Builder, is not connected. Importing from Studio goes through Flatsome's own UI; once a Studio layout is on a page it is ordinary UX Builder shortcodes and Respira edits it like any other.
- Flatsome's real-time UX Builder preview is not driven from the MCP. Respira writes; you refresh the editor to see results.
- Some legacy Flatsome 2.x layouts using unmaintained third-party shortcodes can lose attributes on round-trip. Duplicate first.
Hit one of these and the snapshot gives you a clean way back.
Flatsome runs on the universal tools.
Find, update, move and remove elements, build whole pages, snapshot and roll back. Reads return the builder structure and writes keep it intact.
Three prompts you can paste right now.
Each one assumes Respira is connected to a Flatsome site. Paste it into your AI tool and run.
-
Update product-category banners
For every WooCommerce product category, find the banner element in its Flatsome description and swap the headline from "Shop now" to "New collection". Snapshot each first. -
Refresh the homepage hero slider
On the homepage, find the first ux_slider element. Replace slide 1's headline with "Holiday edition" and update its CTA URL to /holiday. -
Audit color usage
List every distinct hex color value used in Flatsome shortcodes across all pages. Group by frequency.
More recipes, per builder, in the Prompt Book.
Connect a Flatsome site in two minutes.
Pick your client and paste. The site URL and key come from your setup page, or from Respira › Setup in wp-admin. Node.js 20 or newer for the local server.
Claude Code
claude mcp add respira-wordpress --env WORDPRESS_URL=https://yoursite.com --env WORDPRESS_API_KEY=respira_your_api_key_here -- npx -y @respira/wordpress-mcp-server@latest Put in your own site URL and key, run it, then check with /mcp. Every site at once: pass --env RESPIRA_CONFIG_B64=… from your setup page instead of the two values. The full Claude Code guide covers the first edit and undo.
Claude Desktop and Cursor
{
"mcpServers": {
"respira-wordpress": {
"command": "npx",
"args": ["-y", "@respira/wordpress-mcp-server@latest"],
"env": {
"WORDPRESS_URL": "https://yoursite.com",
"WORDPRESS_API_KEY": "respira_your_api_key_here"
}
}
}
} - Claude Desktop, macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Claude Desktop, Windows:
%APPDATA%\Claude\claude_desktop_config.json - Cursor:
.cursor/mcp.jsonin your project
The file is claude_desktop_config.json, not config.json. Every site at once: replace the two env values with RESPIRA_CONFIG_B64 from your setup page.
Codex
codex mcp add respira-my-site --url https://yoursite.com/wp-json/respira/v1/mcp
codex mcp login respira-my-site Run them one at a time. The second opens your browser to sign in to Respira; no key goes in the config. By hand, in ~/.codex/config.toml, then run the login command:
[mcp_servers.respira-my-site]
url = "https://yoursite.com/wp-json/respira/v1/mcp" Browser sign-in, no key
https://yoursite.com/wp-json/respira/v1/mcp Claude Desktop, claude.ai, ChatGPT and Cursor: add a custom connector, paste your site's MCP URL, leave Client ID and Client Secret blank, and approve the sign-in on respira.press. One connector per site.
Any other client
npx add-mcp "npx -y @respira/wordpress-mcp-server@latest" Detects Claude Code, Cursor, Codex, Windsurf and more, and writes the config. Set WORDPRESS_URL and WORDPRESS_API_KEY afterwards.
Common errors
- The server does not show up in /mcp, or the client says it failed to start.
- Cause Node.js is older than 20, or the site URL and key are missing.
- Fix Run
npx @respira/wordpress-mcp-server --doctorin the same shell. It names the missing setting, a bad URL or a refused key.node -vmust print 20 or newer. - ENOENT errors that mention
/_npx/ornode_modules. - Cause The npx cache is damaged, often by an interrupted install.
- Fix Run
rm -rf ~/.npm/_npxand restart the client. Or install once withnpm install -g @respira/wordpress-mcp-serverand userespira-wordpress-mcpas the command. - The browser sign-in opens a "Page not found" on
yoursite.com/authorize. - Cause A Client ID was filled in on the connector, usually the
respira_site_key. - Fix Remove the connector and add it again with the MCP URL only. Leave Client ID and Client Secret blank. Sign-in happens on respira.press, never on your site.
- The MCP address returns 404.
- Cause WordPress is on plain permalinks, so
/wp-json/addresses do not resolve. - Fix In wp-admin open Settings › Permalinks, choose Post name and save once.
- Calls fail with 401, 403, or HTML where JSON belongs.
- Cause A firewall, a bot filter or a challenge page answers before WordPress does, or the host strips the Authorization header.
- Fix Open Respira › Troubleshoot in wp-admin. It runs the checks from the site's own server, names what is in the way and writes a report for your host.
- The agent says it saved, and the live Flatsome page looks the same.
- Cause The edit is on a draft duplicate, waiting for your approval. That is the default on a published page.
- Fix Approve the duplicate in wp-admin under Respira, or from its preview page. Until then the live page stays as it was.
Still stuck? Troubleshooting in the docs, or write to word@respira.press with the first error line.
What changed for Flatsome lately.
The last 5 releases that mention Flatsome, filtered from the same changelog the releases page reads.
-
- Template conditions (plugin 9.3.1+): wordpress_get_template_conditions and wordpress_set_template_conditions read and set where a site template applies, in the same plain words on every builder with the builder's own value beside them.
-
- A generic section on a Beaver Builder page shows its content. The shape agents send to every builder, a section holding a heading and text, was saved on Beaver with "section" and "text" as module names. Beaver has neither, so the page showed nothing but its title while the write said success.
- Exhale on Flatsome writes Flatsome's own shortcodes. Converting HTML to Flatsome wrote the page as [container], [text], [heading], [image] and [leaf], none of which Flatsome registers, so the page showed them as text with curly quotes inside.
- Fidelity mode runs on Flatsome. A designed page now converts in fidelity mode on Flatsome, as it does on Divi, Elementor, Bricks and the others: one root section carries the page, the source sections, rows and boxes become Flatsome rows and columns with their own classes and ids, each element keeps its markup and its classes in an HTML element, forms stay real forms, and the page's stylesheet travels with it, scoped to the page.
-
- WPBakery pages with many addon elements can be read and edited again. On a WPBakery site running The7 with Ultimate VC Addons, Revolution Slider, Go Pricing and WooCommerce, every builder tool failed: finding an element, reading the page's structure, duplicating it, and every edit, even a one word change on a small draft.
-
- Every builder says what it can write. get_builder_info now carries write_capabilities for every builder: whether it builds pages, adds elements or only edits text, and whether a new element is native, written as core blocks, or partial.
-
- find_element by content, text or class works on every builder. A search for text that was not on the page answered HTTP 404, which agents read as a broken tool, and a class search on Elementor never read the custom class setting.
Questions people ask about Flatsome and MCP.
Is there an MCP server for Flatsome?
Yes. Respira is an independent MCP server that reads and writes Flatsome in its own format, with first-class reads and writes across the builder structure. It is not made by the Flatsome team.
Which tools does it use for Flatsome?
Flatsome runs through the universal tools: find, update, move and remove elements, build pages, snapshot and roll back. Reads return the builder structure, and writes keep it.
What happens when the agent gets an edit wrong?
Nothing on the live page. The agent edits a copy first, you approve it inside WordPress, and every write is snapshotted with 90 days of undo.
Do I need a developer or a terminal?
No. Sign in with your browser from Claude, ChatGPT or Cursor and approve the connection once. Coding tools get a one-line command.
Does it work with a Flatsome site that also runs WooCommerce?
Yes. The WooCommerce add-on adds 104 store tools on the same connection, with the same duplicate-first approval flow.
Looking for the Flatsome overview, with visuals and the conversion story? Flatsome features
The other builders, same server.
Start with one site. Free for 7 days.
Maker is €9 a month after the trial. No card for the trial, and it runs on the AI plan you already have, so there is no extra AI bill.