Meeting rooms have always sat slightly outside the rest of an organization’s IT workflow. Email, project boards, and CRMs have been connecting to AI tools for a while now. Rooms have not, largely because there was no standard way to give an AI agent access to what a room is doing. At InfoComm 2026, Neat introduced Neat Pulse MCP, an integration that closes that gap using Model Context Protocol, the open standard that lets AI agents connect directly to the tools and platforms an organization already runs.
What Model Context Protocol changes
MCP allows AI agents to retrieve information, take action, and coordinate workflows across connected systems. Neat has been explicit that Pulse MCP is not a proprietary AI layer or a Neat-specific assistant. It is an open standard applied to meeting room infrastructure, meaning it can work with the AI tools and models an organization already uses, including Claude.
In practice, that means an IT team no longer has to open the Neat Pulse dashboard to check on room health, provision new spaces, or run a status sweep. They can ask, in plain language, and the agent handles it using the same data and actions Neat Pulse already provides.
What it can do today
Neat Pulse MCP is available now as a locally-hosted beta, and setup takes about ten minutes. In beta, it supports:
- Listing and managing devices, including rebooting hardware remotely
- Creating and configuring new rooms
- Generating enrollment codes for new hardware
- Querying room, location, and sensor data
- Sending messages directly to a room’s display
Because the beta runs locally, it works with local MCP clients such as Claude Code and Gemini CLI.
What this looks like in practice
An admin managing rooms across multiple offices could ask whether every room in a set of locations is ready ahead of a company-wide meeting. The agent checks device status, connectivity, and sensor data across those locations, resolves what it can on its own, and flags anything that still needs attention. The same approach applies to setting up a new office: an admin can describe the rooms needed and the configuration profile to apply, and the agent creates them with enrollment codes ready before the hardware arrives.
It also opens the door to standing workflows, like a daily device health check that delivers a status report automatically, without anyone needing to open a dashboard first.
The bigger shift
Neat has positioned itself as among the first companies in the category to bring MCP-based management to meeting rooms. The significance is less about any single feature and more about what it signals: meeting rooms are starting to operate as connected systems inside an organization’s broader AI workflows, rather than as isolated hardware that IT checks on separately. For organizations running rooms across multiple sites, that is a meaningful shift in how much manual oversight a fleet actually requires.
Foire aux questions
What is Neat Pulse MCP?
Neat Pulse MCP is a Model Context Protocol integration that connects Neat’s device management platform, Neat Pulse, directly to AI agents such as Claude. It gives an AI agent access to the same room, device, and sensor data and actions that are available inside Neat Pulse itself, so IT teams can manage meeting rooms through plain-language requests instead of a dashboard.
Is Neat Pulse MCP available now?
It is available today as a locally-hosted beta to Neat customers. Because it runs locally, it works with local MCP clients such as Claude Code and Gemini CLI. Setup takes about ten minutes.
What can Neat Pulse MCP actually do?
In beta, it supports listing and managing devices, rebooting hardware remotely, creating and configuring rooms, generating enrollment codes, querying room, location, and sensor data, and sending messages directly to a room’s display.
What is Model Context Protocol (MCP)?
MCP is an open standard that allows AI agents, assistants, and automated workflows to connect directly to the tools, platforms, and services an organization already uses. Rather than a proprietary AI layer built by one vendor, MCP is designed so meeting room infrastructure can work with the AI tools and models an organization already relies on.
Is Neat Pulse MCP a Neat-specific AI assistant?
No. Neat has described it explicitly as an open standard applied to meeting room infrastructure, not a proprietary AI layer or Neat-specific assistant. It is designed to work with the AI tools and models an organization already uses.
How does this change day-to-day room management?
Instead of opening a dashboard to check on rooms across multiple offices, an admin can ask a question in plain language, such as whether every room in a set of locations is ready ahead of a meeting, and the agent checks status across devices, connectivity, and sensors, resolves what it can, and flags what needs attention.
Rédigé par Gianfranco, Directeur marketing numérique chez GAV MGMT