The Challenge: Enterprise-Scale Support, Agency-Sized Team

Matt Schwartz founded Inspry in Atlanta in 2011. Since then, the agency has built a reputation for the kind of work other shops route around: complex WordPress builds, deep WooCommerce customizations, and long-term managed hosting and support for clients who need their sites to stay up and perform.

Today, Inspry manages more than 60 live sites on Pressable, with another 50 or so in staging at any given time. Waqas Qasim, the agency’s support manager, runs the day-to-day of that portfolio: triaging tickets, communicating with clients, and keeping a fast-moving fleet of custom WordPress and WooCommerce builds healthy.

That scale created a familiar bottleneck. Getting the full picture on any issue meant jumping between the Pressable dashboard, WordPress admin, server logs, and maintenance dashboards. Running any kind of fleet-wide check, scanning every site for a shared error pattern, verifying compatibility before a plugin push, reviewing log changes after a core update, meant hours of manual, site-by-site work. Generating a client audit meant creating a separate application password for every individual site first.

The Solution: A Custom Support Operations Engine on Pressable MCP

Inspry built its own agency-level MCP, a secure orchestration layer that sits in front of Pressable MCP, the WordPress REST API, and their internal maintenance dashboards. It gates access behind Inspry’s organizational credentials and includes guardrails to prevent accidental deletions, while giving Claude the ability to pull from multiple systems at once to diagnose issues from every angle.

Pressable MCP sits at the center of that stack. Because it surfaces hosting-level data across Inspry’s entire portfolio without requiring a separate application password for each site, it is what makes fleet-wide diagnostics and audits possible in the first place.

Key wins with Pressable MCP: 

• Fleet-Wide Update Verification: When Pressable pushed a WordPress 7.0 upgrade across Inspry’s fleet earlier than the team had planned to update, Qasim used Claude and Pressable MCP to pull PHP logs across all 60+ live sites and compare error states before and after the release. The scan surfaced two sites with fatal errors out of the entire fleet, with the rest confirmed clean, and the results were pulled directly into a tracking sheet as a remediation roadmap. What would have taken a full day checking each site manually was done before the end of the workday.

• Root-Cause Malware Detection: A recurring malware infection had been resisting cleanup through Inspry’s standard security tools, which could clear the symptoms but not identify the cause. Using Pressable MCP to dig into hosting-level logs, Claude identified the specific pattern driving the reinfection and then scanned the rest of the portfolio for the same signature in about 10 minutes, work that previously took an entire day.

• Plugin Releases Verified at the Hosting Layer: Inspry builds and sells CheckView, a SaaS tool that tests WordPress forms and checkout flows, and beta tests every new release on its own client sites first. That beta process now runs through Pressable MCP: each GitHub Actions deployment automatically checks Pressable’s logs to confirm no errors appear on beta sites before and after the push, catching issues that application-level testing alone would miss.

• Client Audits Without Per-Site Credentials: Rather than generating a separate application password for every site before pulling an audit, Inspry uses Pressable MCP to pull plugin versions, PHP compatibility, and configuration details for any site on the account in one step. That has made custom, data-backed audit reports a standard part of client communication instead of an occasional time-consuming exercise.

• Security Cross-Referencing: Qasim uses Pressable MCP to cross-check vulnerability flags from Inspry’s other security tools against real plugin activity in the hosting environment, catching issues that those tools surface but rarely resolve on their own.

The Impact: More Time for the Human Side of Support

For a team of Inspry’s size managing more than 60 active client relationships, the math is straightforward. Every hour Pressable MCP saves on bulk diagnostics, log reviews, and audit generation is an hour the support team gets back for the part of the job that actually keeps clients happy: communication, account management, and the kind of proactive outreach that gets put last when the team is buried in manual checks.

Inspry is now extending that same foundation into its ticket system through n8n, so that by the time a support ticket reaches a human, Claude has already pulled the relevant Pressable data and attached an initial diagnosis. The goal is the same one driving every other workflow: let Claude handle the diagnostic legwork, so the team can spend its time on the people.

Results

• • From a full day to under 10 minutes: fleet-wide diagnostic checks across 60+ sites, including post-update error scans and malware pattern detection, that previously required manual site-by-site review.

• • Zero application passwords required: client audit reports now pull plugin, version, and compatibility data across any site on the Pressable account in a single step.

• • 60+ live sites, 110+ including staging: managed through one support operations engine built on Pressable MCP.

• • A recurring malware infection resolved at the root cause: after standard security scanners failed to identify it.

• • AI-assisted ticket triage in development: to attach Pressable diagnostics to support tickets before a human ever opens them.

“AI is making it even more important to have that human touch. Having tools like the Pressable MCP allows us to communicate value more clearly, build better reports, and have more time to actually build the relationship, which is why clients have an agency in the first place.”

Matt Schwartz

Founder, Strategy, and Client Success, Inspry