The stories I get to hear and tell are my favorite thing about my work at Strety. My love for these stories is the reason I wrote around 10 case studies in my first two months here, and why even though my function is mostly communicating 1:many, I still talk 1:1 with customers as much as possible — whether that’s in case study interviews or User Groups or at the upcoming Integrator Summit (shoutout!).
A new addition to the roster of people I get to talk to: beta testers. When I started here and for much of the last two years, the only beta testers for new releases was us, the Strety team. Brian notoriously told me I had to manage all my work (aka an entire marketing function) in Strety before we had Projects… before we even had To Do Lists… making me the ultimate guinea pig. (Imagine the chaos.) Everything a customer sees has been tested and tested and tested again by the heaviest Strety users — those of us who get to call Strety our professional home.
When one of our devs, Orlando, threw out the idea of an MCP connecter, the first iteration was a version just for us, as per usual. He absolutely crushed it and the next step was something (fairly) new to us: beta testing with a handful of customers, which led to my new favorite customer story, featuring Shaz Khan.
Table of contents:
- The 0-60 beta tester
- How the MCP fits into the Strety story
- What you can do with the Strety MCP connection
- Integrator’s Executive Dashboard, limitless-style
- EOS Implementer post-session checklist
- Integrator’s best friend
- A Project maniac’s most special assistant
- What will you do with the Strety MCP?
The 0-60 beta tester
Shaz reached out via our LinkedIn company page 6+ months ago genuinely just complimenting the product and team. I saw he was a restaurant operator and as a former chef, I needed that case study. In the time since, he’s run my favorite customer gamut: case study, User Group attendee, future Integrator Summit attendee and panelist, and lots of hype to share in the company group chat along the way.
About a month ago, we reached out about the MCP beta, and he was excited as I hoped he would be. I was equally excited to see what he would do with the MCP as an Integrator, EOS self-implementer, and former engineer.
I spoke to him last week, and what he showed me blew my mind. He’d built an insane Mission Control center where he was hooking up all his MCP-ready tools to have a single source of truth into his business across dozens of tools (not to mention over a dozen business locations). The comprehensive view, actionable insights, and creativity was astounding. I was so excited to see it, and asked the obvious question:
“So you already were working on this dashboard and then you hooked Strety in when we added the MCP?”
His answer was not so obvious: “No. To be honest I didn’t know what an MCP was when you guys emailed me. I learned a bit about it, saw how powerful it could be, and set about making something so I’d have some feedback for you for this call.”
[Insert 10 sobbing emojis — tears of joy, to be clear!]
When we say we love our customers, we mean it. When our customers say they love Strety, they mean it. And after hearing dozens of customer stories (and especially one like Shaz’s), it’s obvious why there’s so much love: we genuinely love the software and experience we’re building — and that shines through every feature, integration, UI choice, and customer interaction our team creates.
How the MCP fits into the Strety story
When I started and to this day, integrations have been one of our three uniques as software builders. Brian and Larry learned the importance of integrations firsthand when they built a business intelligence software for MSPs, and doubled down when they started with Strety, first by creating an app directly in Microsoft Teams, and then exploding Strety’s integration capabilities from there.
Why integrations? Because a tool without integrations is “almost like a whiteboard, where you go write something down in the conference room and then go back to your desk and forget about it until you had another meeting in the conference room.” (Direct quote from the first case study I wrote at Strety, and still one of my top 5 favorite customer quotes.)
All due respect to Microsoft Teams (😅) — the MCP integration is hands-down my favorite. It connects my favorite tool (Strety <3) with my second-favorite tool (Claude) which also connects to tools that are more or less favored but all necessary. The MCP has made my interconnected tool stack even more connected — the dream!
What you can do with the Strety MCP connection
I really think that when it comes to how to use the Strety MCP integration, the possibilities are #limitless
You know this guy MCPs.
That being said, figuring out where to start can be a bit overwhelming! For your consideration and inspiration, here are a handful of our favorite use cases so far, from the Strety team and a couple of our beloved beta testers.
Integrator’s Executive Dashboard, limitless-style
The Mission Control center from Shaz that I described above is kind of like an executive dashboard — if a mere dashboard could help you surface issues, connect all work to your core values, ideate and create surprising new workflows, and give enhanced visibility not just to your leadership, but every team member.
How he did it: he used Claude to build a dashboard with a page that lists all of his team’s tools, each labeled as to connectability status: MCP connected, MCP ready, API available, no connectors. The ones he could connect, he started connecting. He built multiple dashboards for what mattered the most to him as an integrator, pulling in from any and all connected data sources that he once had to connect and manage through exports and Excel work.
He’s still iterating, but one of my favorite use-cases he mentioned is a thing that seems small but could be the kind of incremental change that makes a big difference for a small(ish) business. There’s a weather-based change to demand for his business that is somewhat unpredictable, and in order to take advantage of the change, they’d have to act fast. He’s connected a weather info service to his Mission Control via API, and now can get notifications if that weather change happens, where, and can build workflows around it, like relevant email campaigns. Magic!
EOS Implementer post-session checklist
One of our EOS Implementer partners, Eric Dykes, got his client added to the beta, and then got himself added too. In addition to needing to stay up on tools so he can be a great advisor for his clients, he was curious about how the MCP could help streamline his own workflows. He has a free Strety account to manage his practice (available to all Strety partners, BTW!). He also uses a CRM and the Google suite for his business.
When he finishes a session with his clients, he has a pretty comprehensive checklist to follow that includes information, updates, and touches across all his main tools. Now, with the Strety MCP and connections into the other tools he uses, he can run through the checklist as a conversation in Claude — doing all the context work in one place, and getting everything set up and ready for him to review and confirm across tools, including calendar invites and email drafts.
The MCP also just makes it easier for him to keep flowing when he’s working on business development. When I spoke with him, he’d literally just gotten off a prospect call and so he updated his call Scorecard in Strety with a simple message in Claude, and kept going with his day.
Integrator’s best friend
It may not surprise you to hear that Brian Dosal, our cofounder, product nerd, and Integrator, has gotten a ton of mileage out of our MCP. In addition to all he does at Strety (and frequently because of Strety work), he’s out and about and on the road a lot.
It used to be that when he was on the go, he couldn’t do much of his in-Strety work, a lot of which can be found in beautiful comments and messages — the guy is a writing/communication machine, as a great Integrator should be. Now with the MCP, he doesn’t even need a keyboard to do his thing. He can ask questions, comment, and write via voice-to-text into Claude. Integrating sans keyboard? Sounds pretty #limitless to me!
He also does more nitty gritty Integrator work more easily than he used to. If he wanted to check out how Rocks were looking and if they were set up for success, he used to have to click into each one… with a mouse. Talk about old-fashioned. Now, he can ask Claude to look at our Company Rocks, flag the ones that aren’t set up to be SMART, and leave comments on each one with his (and Claude’s) feedback on how to make them better for the Rock owner. And he can do it all in one easy conversation, instead of many, many minutes of clicking around and typing.
These are the kinds of incremental wins that add up in a small and/or bootstrapped business like us! And remind me of another favorite case study quote 😀
“Every time we can avoid having to manually enter something, we’re getting back seconds and minutes. MSPs, like most businesses, especially service businesses, are games of inches. You’re not hitting home runs every day. On your best days, you’re hitting singles constantly. It’s hard to focus on the small wins sometimes — with a very entrepreneurial mindset you want to do big things. But the best businesses really focus on the little things, too, like 10 minutes back here and 7 minutes back there. When the small daily wins are compounded over the year, you’re making some massive changes in the business.”
You read that right: the small wins are what make you LIMITLESS.
A Project maniac’s most special assistant
Finally, I will leave you with my own favorite MCP use case: using it to make Claude my personal assistant/project manager/sanity checker.
Like I mentioned above, I have been managing all of my work in Strety since the day I started. Through all of the improvements and building of Projects, I have been a power-user, and power-feature-requester 🙂
When I first set up the MCP, my main use case came fast: To Dos and Projects. I have more active To Dos than I care to mention, and am leading many, many Projects. There are dozens of ideas and initiatives in flight across brand, demand, product, customer, content, and partner marketing. This became a lot for my poor, human-sized brain unless I spent 30 minutes a day — and sometimes way more — organizing my To Dos and Projects. You know what’s super annoying? Organizing the work when you have so very little time on this earth to actually do the work.
Enter: Strety + Claude, together at last.
With Claude’s help, now, the mountain of tasks that didn’t fit cleanly into any project, Rock, or Team space all have a home, no matter what. Nothing is on my list without having a connection to a bigger purpose — no more “onesy, twosy” To Dos, which took way more mental load than their payoff justified.
Speaking of Projects — did you know you can build an entire project using the MCP? [Insert hand-bruisingly grateful applause for Orlando.] This was one of the first blockers I ran into on the earliest iterations of the MCP because the initial endpoints were all communication and/or EOS-focused. Fortunately for all my fellow To Do and Project-heads out there, my power-feature-requester status is still strong, and Orlando pushed out this and so many other project-management related improvements.
Our sick internal workflow while he was working on the MCP and I was testing it (so meta): when I ran into a blocker with the MCP, I would ask Claude what wasn’t working the way I wanted it to and what exactly the need was and have it create a To Do in Orlando’s MCP Project backlog for him to review — and I would make sure with Claude’s help that I wasn’t requesting anything that he already had in his queue. The To Dos were written by Claude at great length and with explanations that I would not have had access to as a non-technical person. Orlando would then fetch these To Dos in Claude, right next to where he’s working on the code. I can’t quantify the hours we saved here, but would guess it’s approximately a jillion.
Now when I have a Rock (SMART, of course, Brian!) I can have Claude help me build a correspondingly sweet Project. When I have 20 minutes before my next meeting, Claude can help me find and execute the best To Do I can knock out in that window. When I suddenly have a pile of 20 To Dos due today because my eyes are always bigger than my stomach, Claude can help me prioritize, organize, and set things right in my task world, in just a few minutes.
A fun tip for when you’re needing some robot hand-holding while powering through To Dos: you can ask Claude what you’ve got cooking today and ask it to make your list a pinned artifact in the chat where you can mark your To Dos done and have a pretty progress bar and everything (hat tip to who else but Orlando who came up with this awesome idea and suggested it to me).
And like Shaz and our Implementer friend, connecting Claude to my other MCP-available tools alongside Strety has helped drive even more efficiency for me and my tiny team, which is a life-saver. I’ve been able to consolidate workflows and therefore cut down on additional tools and logins — while getting more done in less time. Chef’s kiss!!
This MCP is the most helpful release for me personally since Strety Projects came out, and if you’ve ever been forced to manage an entire project in an EOS software Rock, you know that’s pretty dang helpful.
What will you do with the Strety MCP?
Now that you’ve been inspired and absolutely delighted by how four very different people have used the Strety MCP, it’s time to write your own story — and ideally, share it with us! Note that everyone in this blog happens to be a Claude stan, but our MCP also connects with ChatGPT, or any other AI agent tool that supports remote MCP servers. So whatever you’re using, you should be able to give the Strety MCP a shot!
Email me at samantha at strety dot com if you have something cool to share, or connect with me on LinkedIn to tell your story. And as always, our support chat is open and populated entirely by humans who are ready to help.
PS — one thing I’m not using the MCP for? Writing semi-unhinged product blogs like this. Sorry but Claude could never!!! For a more detailed, technical, and professional overview of the Strety MCP, find the official Help Doc here.