What Neat announced
Neat said Neat Pulse MCP, shown in beta at InfoComm 2026, is now generally available to paid Neat Pulse customers at no extra cost. It is built on the open Model Context Protocol (MCP). That lets compatible AI agents query Neat Pulse, the company's management platform for Neat devices and rooms, and run supported actions.
Neat's pitch is that this avoids a new dashboard or a proprietary assistant. The beta announcement in June said this isn't a proprietary AI layer or a Neat-specific assistant. The GA announcement says the same thing, and says admins can build workflows around the systems they already use.
What agents can read and do
Per Neat's support guide (last updated November 17), an assistant connected to the server can do the following:
- List and inspect devices, including connection and call status, firmware, network configuration and sensor readings.
- Reboot a device, along with any paired devices.
- List, create, update and delete rooms.
- Browse locations and regions and reset room enrolment codes.
- Read and apply device configuration, and move devices between rooms.
- Send messages to devices and rooms.
- Create, update and delete locations and regions.
Neat's announcement offers some example workflows:
- A fleetwide review of configuration drift.
- A pre-meeting readiness check across several offices.
- Indoor-air-quality monitoring that messages the room.
- A Slack or ticketing-system report that triggers an agent to gather data, act, recheck and report back.
These are vendor-described possibilities, not turnkey features. The announcement says workflows can run on demand, on a schedule, or on a trigger. It does not say Neat supplies the scheduler. That part comes from whichever agent host you choose.
How "runs locally" actually works
"Runs locally" needs a careful reading. The request path is your AI assistant, then the local MCP server (run via npx), then the Neat Pulse cloud API, then Neat Pulse services. The local server is a relay, not an on-premises replacement for Neat Pulse.
Neat's materials also don't say how your chosen AI host handles the data it gets back, such as retention or processing. Before pointing a hosted assistant at fleet data, check that provider's terms.
Access control and audit
This is the part IT teams should read twice.
- Read scope: According to Neat's guide, a read-only token can't reboot, delete, create or update anything.
- Write scopes: Assigning all available scopes unlocks the full toolset, including reboots, room management and enrolment-code resets.
- Neat's advice: If in doubt, start read-only and expand later.
- Audit trail: Neat says actions performed through MCP are recorded in Neat Pulse Audit Logs. The descriptive name you give the API key appears there, so use names that identify the integration, such as the example "claude-mcp".
Neat's materials don't describe a mandatory per-action approval prompt. A write-scoped token can delete rooms, locations and regions. Any confirmation step would come from the AI host, not from Neat. I'd treat a write token like any other privileged service credential.
Prerequisites and Windows setup
Neat lists these requirements:
- An active, paid Neat Pulse account.
- Owner access to the Neat Pulse tenant, because only Owners can generate API tokens.
- Node.js v20 or later on the machine running the server.
- A local MCP host on the same machine, such as Claude Code, Claude Desktop or Cursor.
The documented procedure goes like this:
- In the Neat Pulse portal, go to Settings → API Keys and create a key with a descriptive name.
- Assign scopes, then copy the token. It is shown only once.
- Find your organization ID in Settings. It is also the number in the portal URL after /org/.
- Register the server with your host.
Neat's guide gives host-specific steps for Claude Code, Claude Desktop, Cursor, Codex CLI, GitHub Copilot CLI, Antigravity, OpenCode and other MCP clients. On Windows, the generic route sets the PULSE_API_TOKEN and PULSE_ORG_ID environment variables in PowerShell or Command Prompt. It then runs the @neat-no/pulse-mcp package with npx. For Claude Desktop on Windows, the config file lives at %APPDATA%\Claude\claude_desktop_config.json.
To verify the connection, ask the assistant to list all devices in your Neat Pulse organization. A returned device list means it works.
Common failure points
Neat's troubleshooting table covers these cases:
- 401 or Unauthorized: The token is invalid or revoked, so generate a new one.
- 404 or Organization not found: The org ID is wrong.
- npx: command not found: Node.js isn't installed or isn't on the PATH.
- No tools appear: The server may not have started. Check the config for JSON errors such as trailing commas, then restart the host.
- Connection errors: The machine may not be able to download the package, which is common behind a corporate proxy or npm registry restrictions.
What changed since the beta
Comparing the beta and GA documentation turns up a few differences:
- The beta reference said locations and regions were read-only through the MCP server. The current guide lists creating, updating and deleting them.
- A community walkthrough of the beta on Windows 11 used Node.js 18+. The current prerequisite is v20 or later.
- Beta setup commands used the @beta package tag. The current guide's Codex, Copilot CLI, Antigravity and OpenCode examples use @latest. The Claude and Cursor examples in the guide I reviewed still show @beta, so check which tag your host config uses.
Taken together, the beta-to-GA expansion in write capability is the biggest practical change. Anyone who approved a read-mostly beta should re-review the scopes before treating GA as the same thing.
Analysis
MCP is turning into a common way for management planes to expose themselves to AI hosts. Neat is the first to say it brings this to meeting rooms. In its beta announcement, Neat said it is among the first companies in the category to bring MCP-based management to meeting rooms. That is a vendor claim, and I haven't independently checked it.
The upside is real. Fleet comparisons that once meant exports and spreadsheets become a sentence. The downside is also real. Natural-language control of a fleet raises the cost of one bad instruction or a leaked token. The sensible rollout is a read-only token first and write scopes only for named workflows. Keep the token out of repositories and chat windows, and review the Audit Logs regularly.
The announcement is also silent on pricing beyond "paid account" and doesn't give fleet-scale performance numbers.
References
- Neat Pulse MCP Goes GA, Letting AI Agents Manage Meeting Rooms - UC Today UC Today · 2026-11-18T14:45:20.399000+00:00
- Neat Pulse MCP (beta): Setup Guide - Neat Support support.neat.no
- Debuting Agentic Meeting Room Management with Neat Pulse MCP - Neat us.neat.no