Enterprise ITSM has always been a walled garden — every tool talking to nothing, every workflow requiring a custom integration ticket. Freshworks just put an MCP Gateway inside Freshservice and called it the antidote.
The Problem It's Solving
IT support has a ghost shift problem. Freshworks pulled telemetry from millions of service interactions and found that 47% of all IT tickets now come in outside standard business hours. Response times in that window run more than an hour slower, with SLA rates dropping as much as 5%. The workforce is distributed and always-on. The service desk isn't.
The deeper issue is architectural. Enterprise ITSM platforms — ServiceNow, Jira Service Management, and yes, older versions of Freshservice — were built as centralized systems of record. When AI started getting bolted on, it ran into the same problem every new layer runs into: it had no real access to the live context sitting across your HR system, your project tools, your incident logs. The AI was smart in isolation and blind in practice.
Freshworks is betting that the gap isn't a model problem. It's a context problem.
How Freddy AI Agent Studio Actually Works
The centerpiece announcement from Freshworks' Refresh 2026 conference is Freddy AI Agent Studio — a no-code environment for building and deploying custom AI agents inside Freshservice. But the more technically interesting piece is what sits underneath it: an MCP Gateway.
Model Context Protocol, for context, is the emerging standard for letting AI agents pull live data from external systems without custom integration code. Freshworks has implemented it as a native layer in Freddy AI, which means agents can now reach into Notion, ClickUp, Linear, Workday, Rippling, and the rest of the enterprise stack — not through brittle webhooks or bespoke connectors, but through a standardized protocol call.
The practical result: a Freddy AI agent handling an employee onboarding request can pull HR data from Workday, create a task in ClickUp, and update a Notion doc — all inside a single workflow, without an engineer writing glue code for each handoff.
On top of that, the studio ships with pre-built domain-specific agents for IT, HR, finance, and facilities, plus a library of agentic workflow templates. Agents meet employees where they already are — Microsoft Teams and Slack — rather than requiring portal logins.
The measurement layer is called AI Insights, paired with Experience Level Agreements (xLAs). The framing is: stop tracking ticket close times, start tracking whether employees actually got their problems solved. The xLA system uses weighted computation and AI analysis to connect service delivery metrics directly to employee sentiment scores.
Freshservice's unified data layer — which now includes the reimagined Freshservice ITAM and FireHydrant incident management products — is what gives the agents clean, reliable context to work with. The pitch is that Freddy doesn't need a months-long data cleanup project before it can run. The foundation is supposed to be ready on day one.
What IT and Service Teams Are Actually Using It For
The announced use cases cluster around two areas: employee self-service at scale, and cross-departmental workflow automation.
On the self-service side, the ghost shift problem is the clearest target. An employee submitting a payroll question at 11pm shouldn't wait until 9am for a human to look at it. A Freddy AI agent with access to Rippling and Workday can resolve that class of request without any queue time.
For cross-departmental automation, the MCP Gateway is doing the work that would previously have required a dedicated integration project. New hire onboarding — which typically touches IT provisioning, HR systems, facilities access, and project management — is the flagship example. The agent orchestrates across all of them through a single workflow definition.
Amerisure's IT Service Management team offered a concrete data point: ticket trend analysis that used to take an hour each morning now takes three minutes with Freddy Insights. That's the kind of mundane-but-real efficiency number that actually lands in a budget conversation.
Why This Is a Bigger Deal Than It Looks
MCP is moving fast as an enterprise standard, but most of what's been announced so far has lived at the developer tooling layer — IDEs, coding agents, local model setups. Freshworks embedding MCP as a production capability inside an ITSM platform used by companies like Bridgestone, New Balance, and S&P Global is a different category of deployment.
It's the first time MCP has been packaged as a no-code enterprise feature for IT ops teams who will never touch a config file. That changes who can deploy AI agents with live cross-system context — from platform engineers to service desk managers.
The governance angle matters too. The announcement specifically calls out "embedded governance" and deployment in "weeks, not quarters" as differentiators from legacy platforms. That's positioning against ServiceNow, which has its own agentic AI story but carries the implementation complexity that comes with it. If Freddy AI Agent Studio actually delivers on that timeline claim, the competitive pressure on the ITSM incumbents gets real.
Keith Kirkpatrick at The Futurum Group put it clearly: the market is shifting from AI pilots to production deployments, and the platforms that combine integration breadth, deployment speed, and governance tooling in one package are the ones that will win the next wave of enterprise deals.
Availability and Access
Freddy AI Agent Studio and the MCP Gateway are available now as part of Freshservice. The FireHydrant incident management integration and the reimagined ITAM module are included in the unified platform. Freshworks published a Futurum Group report showing 168% ROI over three years for enterprises moving off legacy ITSM platforms, available on their site. More detail on the May launch is at freshworks.com.
MCP just moved from developer infrastructure into enterprise service operations. The question now is how fast the other ITSM platforms respond — and whether ServiceNow's complexity becomes the thing that costs it the mid-market.
Follow for more coverage on MCP, agentic AI, and AI infrastructure.
Top comments (0)