Introducing Interact MCP: the enterprise intranet, in every AI assistant

Today we’re introducing Interact MCP, the most capable MCP server of any intranet vendor: one permission-aware connection, built for large enterprises on the foundation of Cue and Conductor, that brings your intranet into the AI assistants your people already use, and brings the systems your business runs on into Interact.

Employees no longer start every task on the intranet. They ask Copilot, Claude, ChatGPT or Gemini, and more of them now have agents acting on their behalf. Those assistants are only as useful as what they can reach, and most can reach very little of what your organization actually knows and does.

Interact MCP uses the Model Context Protocol (MCP), the open standard for connecting AI to tools and data, and it works in both directions:

• Interact in every assistant. Approved AI assistants can search, read and act in Interact, with each person’s own permissions.
• Every system in Interact. Conductor connects out to the MCP servers your organization relies on, from Workday and SAP to the tools your own teams build.

Interact is a Leader in the 2026 Gartner® Magic Quadrant™ for Intranet Packaged Solutions for the fourth consecutive year.* Interact MCP is built for the same customers: large, complex organizations with strict permissions, many audiences and regulated data, not small teams looking for a lightweight connector.

Built on Cue and Conductor, not bolted on

Interact MCP isn’t a thin connector added to a chatbot. It runs on the same foundation as Cue and Conductor, which we launched in September.

That foundation is what makes it a true power tool. External agents get the same 700 capabilities, the same permission checks, and the same version history and audit trail that Interact’s own AI uses every day. Every capability we add to Cue and Conductor becomes available to the assistants your people use too.

Interact in the assistants your people already use

Your employees don’t need to learn a new tool. Interact MCP connects to the assistants and agent platforms they already have:

Assistant	How it connects
Claude	Custom connector on Pro, Max, Team and Enterprise
ChatGPT	Custom MCP app on Business, Enterprise and Edu, including write actions (currently in beta)
Microsoft 365 Copilot	Federated MCP connector, with Copilot Studio for task-specific agents
Gemini Enterprise	Custom MCP data store
Workday Sana	Remote MCP connection
SAP Joule	MCP server in Joule Studio
ServiceNow Now Assist	External MCP server in AI Agent Studio
Slackbot	MCP server in a Slack app
Atlassian Rovo	MCP server for Rovo agents
Salesforce Agentforce	External MCP server with per-user authentication
Your own agents	Any client that supports remote MCP with OAuth sign-in

“Your employees already have a favorite AI assistant, and soon each of them will have agents working on their behalf. The intranet has to serve both. With Interact MCP, the place where your organization’s knowledge, communications and processes live becomes something every approved assistant can use, at enterprise scale and without giving up the governance that makes it trustworthy.”

Simon Dance, CEO, Interact

Read and write, not just search

Interact MCP gives agents 700 capabilities across 26 areas of the intranet, each designed for AI agents rather than wrapped around a raw API. They are the same checked tools that power Cue and Conductor.

That breadth makes Interact MCP the most capable MCP offering in the intranet market. Many intranet MCP servers are read-only or limited to a few content types. Interact MCP lets agents search, create, edit and act across the whole intranet, and it connects out to other systems too.

That means an assistant can do real work, not just point people toward it:

• An employee asks whether they can accept a gift from a supplier. The assistant reads the attached policy and answers with a link to the source.
• An internal comms manager asks for a new parental leave page. The assistant drafts it, updates the approved wording and saves a new version.
• A platform owner asks which regions need attention. The assistant compares adoption by audience and reports what the data can and can’t show.

It also changes how employee self-service works. People can find policies, raise and track IT and HR requests in connected systems, and reach the right owner without leaving the assistant they started in. Routine questions get answered before they become tickets for your IT and HR teams.

Every system in Interact

MCP works both ways. As well as bringing Interact into other assistants, Conductor connects out to the MCP servers your organization already relies on, so third-party systems and homegrown tools work inside your intranet too:

• Interact’s MCP catalog. Switch on ready-made connections, with admins deciding which servers and tools are available.
• Any OAuth-enabled MCP server. Add remote MCP servers from SaaS vendors such as ServiceNow, Salesforce, Atlassian, Asana and Notion, or from your own platform team.
• Homegrown tools. Expose internal systems as MCP tools once, then use them in Conductor alongside Interact’s own capabilities.
• Workday Sana. Conductor connects to Workday’s Agent-Ready Tools through Workday’s Agent Gateway, bringing HR and finance capabilities into the intranet with Workday’s permissions, business rules and approvals intact.
• SAP Joule. Your team exposes the SAP APIs it chooses as governed MCP tools through SAP Integration Suite’s MCP Gateway, and Conductor uses them with each person’s own access.

“Most MCP announcements stop at letting an assistant search your content. We built Interact MCP on the same checked tools that power Cue and Conductor, so an agent can read the policy, update the page and tell the right people, all as the person who asked. And because MCP works both ways, Conductor can reach into Workday, SAP, ServiceNow and the tools your own teams build. The intranet stops being a destination and becomes the place work gets done, whichever assistant you start in. That’s what enterprise customers need, and it’s why we believe Interact MCP is the most capable in the market.”

Tom Walters, VP, Product, Interact

Enterprise-grade governance, by design

The assistant changes. Your permissions don’t. Every connection runs as the signed-in person, and AI clients never receive new Interact privileges.

• Your identity provider. People connect through the single sign-on your intranet already uses, such as Microsoft Entra ID or Okta, so Conditional Access and multi-factor authentication still apply.
• Each person’s permissions. Every call carries that person’s own token, so an assistant can only see and do what they already can in Interact.
• Checked, versioned changes. Writes go through Interact’s own validation, land in version history and are attributed to the person who asked.
• Admin controls. People only see the tools your organization has enabled, API access can be switched off for each intranet, and impersonated sessions can’t connect.
• Agent Insights. One view of agent activity across Cue, Conductor and MCP clients, separating successful actions, blocked requests and outcomes Interact can verify.

MCP or A2A? Both, and it matters less than you think

MCP and A2A solve different problems. MCP connects an AI agent to tools and data. A2A (Agent2Agent), an open protocol started by Google and now hosted by the Linux Foundation, lets one agent hand a task to another.

Most enterprise platforms will use both. SAP, for example, connects outside agents to Joule over A2A and exposes SAP tools over MCP.

For an intranet, the protocol matters less than what sits behind it. The questions worth asking are which assistants it works with, what agents can actually do, and whether every action runs with the right person’s permissions. MCP is the standard the assistants above already support, which is why we built on it first.

Availability

Interact MCP comes with Cue or Conductor, with no separate connector fee. Full availability is planned for later this year, and customers who are ready can start sooner. Employees connect through Cue, with no Conductor license needed; publishing and operational tools come with Conductor access and the person’s role. Each AI provider’s own subscription still applies.

See every capability, assistant and safeguard on the Interact MCP page, or book a tailored demo to see it working with the assistants your people already use.