Introducing Multi-Org MCP: AI Tools for EOS Implementers and Fractional Integrators

It’s Sunday night. You’ve got a session day Monday, a 90-minute meeting on Tuesday, and a Quarterly on Thursday, and you have to switch your AI tool off and on just to reach the right company’s data. Disconnect, reconnect, remind it which client you’re talking about, and finally ask your question. Then the loop starts all over again for the next one.

We kept hearing about that loop from Implementers, fractional Integrators, coaches, and partners. As I’ve begun the journey into becoming an Implementer, I’ve seen for myself how much info you need to carry across clients and systems. So we built a multi-org MCP, an update to the Strety MCP server that connects Claude, ChatGPT or Microsoft Copilot to every Strety organization you work in, with one sign-in. One conversation, every company, and every answer labeled by the company it came from.

If you’ve been waiting on this one, it’s finally live! 🎉 Let’s look at what changes in your week, what you can ask, and how to keep every client’s data in its own lane.

Table of Contents

• Implementers and Integrators asked for the multi-org MCP
• What changes in your week
• What can you ask across all your companies?
• How do you keep every client’s data separate?
• Common mistakes when you run AI across clients
• One client or a whole book of them
• Claude, ChatGPT, or Copilot?
• How to turn on multi-org MCP
• Frequently asked questions
• Where to start this week

Implementers and Integrators asked for the multi-org MCP

Until now, your Strety MCP connection could see one company at a time. Great if you run one company. A lot less great if you’re an Implementer working with a dozen clients, or a fractional Integrator splitting your week across three leadership teams. Every switch meant reconnecting, and asking your AI tool to compare two clients side by side was off the table.

You told us. A lot. Implementers, coaches, and fractional Integrators kept bringing the request up, and our Success team kept fielding them. And we love listening (seriously, keep the requests coming). When the people who run EOS across most companies all ask for the same thing, it goes straight to the top of our list.

What changes in your week

Picture Monday morning. You open Claude, ask how your clients’ Rocks are tracking this quarter, and get one answer that covers all of them, with each Rock tagged with the company it belongs to. No logins, no tab-hopping, no “wait, which client was this again?”

On the sign-in screen, you pick the Strety organizations you want your AI tool to reach and decide whether it can make changes or only read. From then on, your AI tool tells Strety which company it’s working in with every request, so a chat that spans five clients keeps each one straight. It can pull a client’s V/TO or company overview when you want context for a question, and you’ll only ever see what’s relevant from the client workspace.

Already connected to a single company? Nothing changes for you.

What can you ask across all your companies?

If you manage multiple EOS clients, checking on one used to mean logging into their workspace and clicking through tabs. Now it’s a question. A few of our favorites to get you started:

If you’re an EOS Implementer:

• “Which of my clients have off-track Rocks this quarter?”
• “I have session days with two clients this week. Pull each one’s Scorecard and open Issues so I can prep.”
• “Check every Quarterly I facilitated this year. Which clients still have unresolved Issues from Q1 or Q2?”

If you’re a fractional Integrator:

• “Give me a rundown of my To-Dos grouped by company.”
• “Prep me for Thursday’s L10 at each of my companies. What Issues are still open?”
• “Which Rocks are at risk across my companies this quarter, and who owns them?”

Follow-up gets easier, too. Back in June, EOS Implementer Eric Dykes showed us how he runs his post-session checklist as one conversation in Claude. With multi-org MCP, you can run that same kind of flow for whichever client you just left, without reconnecting first.

And if you love to tinker, you can go bigger and build a full cross-client dashboard in Claude Code on that same single sign-in. Need more inspiration? We rounded up nine ways our team and customers use AI to run EOS.

How do you keep every client’s data separate?

Your clients trust you with their numbers, and that trust has to come along when an AI tool joins the party. Multi-org MCP is built with that in mind. Every request names the company it’s working in, every answer carries a company label, and your connection can only see what you can already see in each Strety workspace.

You also get to decide how much your AI tool can do. Drop write access when you connect, and you get a read-only view of every client with zero risk of editing their data by accident. You can revoke the connection whenever you want, and our Security page covers how we handle data.

Common mistakes when you run AI across clients

A few habits make a big difference once you have several companies connected.

Leaving the company out of your prompt. “Show me open Issues” works fine with one client. With six connected, say which one you mean. We recommend naming the company any time you work across organizations, so your AI tool never has to guess.

Granting write access you don’t need. If you mostly want to check in between sessions, a read-only connection gives you the visibility without the worry.

Skipping the gut check. Your AI tool reads live Strety data, and it’s still worth a quick sanity check against what you heard in the room before you bring a number to a client session.

One client or a whole book of them

Maybe today it’s one client and one AI tool. Next year it’s a second company, a subsidiary, or a full practice. Your connection grows with you.

You’d be in good company. Fractional Integrator Tiffany Keegan runs Fox Ops and every EOS client in one place on Strety, and Suzy Joeckel holds two seats at once as an EOS Implementer and fractional Integrator. Multi-org MCP brings that same everything-in-one-place feeling to your AI tool.

The same goes for operators. If you run more than one company or a group of subsidiaries on Strety, you get the same one-connection setup.

Claude, ChatGPT or Copilot?

All of them! Strety’s multi-org MCP works in Claude (including Claude Code), ChatGPT, and Microsoft Copilot. You can pick several organizations when you sign in. Go with whichever already lives in your browser tabs.

How to turn on multi-org MCP

If you already use Strety in Claude, ChatGPT or Microsoft Copilot, you know the drill. Connect Strety, pick your companies on the sign-in screen, choose read-only or read and write, and you’re in. The Strety MCP Complete Guide has the step-by-step with screenshots in its “Multi-Organization Access via MCP” section, and there’s no extra cost, since the Strety MCP is included with your Strety plan.

Are you an Implementer who’s new to Strety? As a Strety partner, you get a free account to run your own practice, plus a Coaches Portal for setting up client accounts and referrals. Once a client adds you as a coach, you can also check their EOS reporting between sessions.

Frequently asked questions

Where to start this week

Pick the three companies on your calendar this week, connect them in one go, and ask your AI tool one question: “Which of these companies has a Rock in trouble?” You’ll have your answer before you finish your coffee.

Implementers and fractional Integrators, this one’s for you 💜

Connect the Strety MCP if you’re already a Strety user, or start your 30-day free trial, no credit card required, to see what’s the hype about!