If you run more than one WordPress site, the goal is simple: connect them all once, then sit in a single AI conversation and say "update the homepage on the bakery site" or "audit the law firm site," and have it just work. This guide explains how that connection works, how seats and plans fit together, and the one billing question that trips people up: when to upgrade your plan versus when to add a second one.
The mental model
Think of Respira as one control panel that sits between your sites and your AI. Your WordPress sites connect up into it, and your AI assistant connects down into it. You manage the whole thing from a single account.
The key idea: your sites are not tied to a particular computer or a particular AI app. They live on your Respira account. Whatever AI you point at the account can reach the sites you have connected.
Connecting your sites
Each site connects the same way, once. You install the Respira plugin on the site and paste your license key. From that moment, the site is registered to your account and shows up in your dashboard.
When you set up your AI, your dashboard hands you a single config file (Dashboard, then MCP Setup). That one file lists every site on your account. You do not set up each site separately in your AI. You connect once, and all your sites come along.
Using them in your AI
In Claude Desktop, Claude Cowork, Cursor, and OpenAI's Codex, this is the whole experience. You connect Respira once, then you talk in plain English. Your AI can see the list of sites on your account, so you point it at the one you mean by its web address, or the recognizable part of it:
As long as what you say matches one of your connected sites, Respira switches to it and keeps working there for the rest of the conversation. You jump from one client site to another just by saying which one. Every edit is snapshotted first and validated after, on whichever site you switched to, so moving between sites never means losing the safety net.
The ChatGPT exception
ChatGPT is the one place this works a little differently today, and it is worth being clear about.
Claude, Cowork, Cursor, and Codex run a small local connector that reads that single config file, which is why they can hold every site at once. ChatGPT instead connects to a site through a remote connector, and a connector points at one site. So in ChatGPT today, the pattern is one connector per site: you add each site you want to edit, then tell ChatGPT which one you mean.
The dashboard, step by step
Everything starts in one place: your Respira dashboard, under MCP Setup (respira.press/dashboard/mcp). It is the single screen where you connect an AI, manage which sites it can reach, and set what it is allowed to do. Here is the whole thing, start to finish.
1. Pick your AI, get your connection
Choose the assistant you use, Claude Desktop, claude.ai, Claude Cowork, ChatGPT, Cursor, Codex, and a few more, and the page gives you the exact step for that one. There are two connection styles, and the difference matters:
- A connection link. For Claude Desktop, claude.ai, ChatGPT, Cursor, and Codex, you copy a link, paste it into that app's connector settings, and approve it. Quick, and it connects the one site you picked.
- A config file that already holds every site. Claude Cowork uses this by default, and it is also available for Cursor, Codex, and Claude Desktop under "other ways to connect." You download one file, drop it in once, and every site on your account is reachable with no key to paste. This is the path that gives you the connect-once, switch-by-name experience from earlier in this post.
2. Choose what the AI is allowed to do
Every connection is scoped, so it can be as cautious or as capable as you want:
- Read only looks but never changes anything.
- Content edits posts, pages, and media.
- Builder, the default, is content plus your page-builder layouts.
- Full is everything, including site options and plugins.
Pick the least you need. You can always add a second, more capable connection later for the rare job that requires it.
3. Group sites with Site Packs
On the Studio plan, you can bundle a chosen set of sites into a named Site Pack and export them together. Click New pack, name it, add the sites you want, and you get two one-click exports:
- Registry, a single JSON file listing just that pack's sites.
- Configs, a zip of ready-to-drop config files for those sites.
Packs are useful when you want to hand one teammate, or one machine, a specific slice of your roster instead of the whole account. You can keep up to twenty of them.
4. Set the rules on the site itself: Tool Governance
The dashboard controls the connection. The final say lives on each WordPress site, in wp-admin, then Respira, then Tool Governance. There you decide which tools any connection may use, and what needs your approval before it runs. It applies to every connection to that site, no matter which AI or which key reached it.
How seats work
Every plan comes with a number of seats, and each connected site uses one seat. Maker is 1 site. Builder is 5. Studio scales from 25 upward. Connect a site, and it takes one seat on your plan.
The simplest way to picture a plan is a membership card with a set number of check-ins. Your Builder card is good for 5 sites. When you install Respira on a site and paste that card's key, the site checks in against that card. Your dashboard adds up all your cards and shows you one combined total, so you mostly never have to think about which card a site sits on.
Two ways to grow: upgrade vs stack
When you need more sites than your current plan covers, there are two different moves. They are both valid, and they are not the same thing. Picking the right one is the difference between paying for what you need and paying twice.
Upgrade in place
Change your current plan to a bigger one. Same subscription, more seats.
- Your plan moves from, say, Builder to Studio.
- Seats jump from 5 to 25 on the plan you already have.
- One bill, prorated. Nothing is bought twice.
- Your sites stay exactly where they are.
Stack a second plan
Keep your plan and add another. The seats pool together.
- Two Builders give you 10 seats, not 5.
- A Builder plus a Studio gives you 30, in one shared pool.
- Two separate bills, two plans, combined capacity.
- Useful for large or growing rosters.
Quick answers
Can one ChatGPT app edit all my sites and switch between them by name?
In ChatGPT today, you connect one site per connector. For one connection that reaches every site by name, use Claude, Claude Cowork, Cursor, or OpenAI's Codex. It works there today.
Do I have to set up each site in my AI separately?
No. The config file from your dashboard already lists every connected site. You connect once and all of them come along.
If I have two plans, do their seats combine?
Yes. Seats pool across all your active plans into one combined total. Two Studios is 50 sites. A Builder plus a Studio is 30.
How do I get more sites without paying for two plans?
Upgrade your existing plan to a larger tier. That raises the seat count on the plan you already have, on one bill. Only stack a second plan if you actually want the combined capacity.
I think I bought the wrong thing. What now?
Just reach out. Billing fixes, plan changes, consolidating two plans into one, refunds for accidental doubles, all handled directly.
The short version: connect every site once, work from a single AI conversation, and when you grow, upgrade the plan you have unless you genuinely want to stack a second one. If anything about your plan or your seats looks off, ask. It is almost always a five-minute fix.
A personal note
Thank you for reading all the way to here. If you use Respira, you are not just a name on a list to me. You are walking this road alongside me, and I do not take that lightly.
There is no big company behind this product. There is me, and there is you. The principle that became clear to me not long after I started building Respira is a simple one: I am here to help you be more successful in your WordPress work, and to keep you current with what today's technology can actually do for you. That is the whole job, and it is the part I care about most.
So when you use Respira, send a note about what is missing, or tell me what would make your day easier, you are doing more than improving a tool. You are helping a father build something he believes in and move closer to a vision he has carried for a long time. That means a great deal to me.
If you have a question, an idea, or a way you think we could work together, write to me at word [at] respira.press. I read every message myself, and I would genuinely like to help. Leave a comment below as well. I want to hear how you are using this, and where it can be better.
And above all, we are here to learn together.
Mihai
Join the conversation
0 comments · Respira accountNo comments yet. Be the first to weigh in.