Neat Pulse MCP: Data Model and Tool reference
Last updated November 16, 2026
Overview
Neat Pulse MCP (@neat-no/pulse-mcp@latest) is a Model Context Protocol (MCP) server that connects AI assistants such as Claude or Cursor to Neat Pulse. This article is the companion reference to the Neat Pulse MCP: Setup Guide. It explains how Neat Pulse organizes your fleet and lists the tools your AI assistant can use once connected.
Not connected yet? Start with Neat Pulse MCP: Setup Guide, then come back here.
Contents
Concepts
This section explains the Neat Pulse data model. Understanding how your fleet is organized helps you (and your assistant) use the tools effectively, especially when filtering by location or working with devices across rooms.
Tip for AI assistants: This conceptual information is also exposed directly as an MCP resource at pulse://domain-guide. If your assistant seems confused about the hierarchy or ID formats mid-conversation, you can prompt it: “Read the domain guide.”
Resource hierarchy
Organization
└── Region (geographic grouping, e.g. "Europe")
└── Location (physical site, e.g. "Oslo HQ")
└── Room (meeting space, e.g. "Loft")
└── Device (physical Neat hardware)
- Organization — the top-level account, identified by your
PULSE_ORG_ID. All resources belong to one organization. - Region — a named geographic grouping of locations. Not every location needs a region.
- Location — a physical site, such as an office, building, or campus. A location belongs to at most one region.
- Room — a meeting space within a location. Devices are enrolled in rooms. A room belongs to at most one location.
- Device — a physical Neat device (Bar, Pad, Board, etc.). A device belongs to exactly one room at a time.
IDs
Every resource has a unique ID. You won’t normally need to handle these yourself (your assistant looks them up from the names you mention), but it helps to recognize them.
| Resource | ID type | Example |
|---|---|---|
| Device | UUID (string) | "0708f94f-e610-4c75-8f11-33f27212df3e" |
| Room | Integer | 42 |
| Location | Integer | 7 |
| Region | Integer | 3 |
Key relationships
- A device belongs to exactly one room.
- A room can contain multiple devices.
- Devices in a room may be paired to a “master” device (shown as
pairing_serialon the device). Rebooting the master reboots its paired devices too e.g. Neat Pad and Neat Center paired to a Neat Bar Pro. - Deleting a room unenrols every device in it from Neat Pulse, and those devices must be re-enrolled before you can manage them again. This is the most significant destructive operation in the system.
Device enrolment codes
Each room has a device enrolment code (DEC). A new device is enrolled into a room by entering this code on the device during setup.
The code has no expiry until it is first used. Once used for the first time, a countdown begins. The server sets the exact expiry, which appears in the get_room response as device_enrollment_code_expires_at. The code continues to work for additional device enrolments until that expiry time passes.
You can reset a room’s enrolment code at any time with the reset_enrolment_code tool. This immediately invalidates the existing code and issues a new one with no expiry.
Device Models
The model field on a device contains a hardware model code. The human-readable product names are:
- NF19A1: Neat Pad
- NF25J1: Neat Pad Pro
- NF19B1: Neat Bar
- NF22E1: Neat Bar 2
- NF21D1: Neat Bar Pro
- NF21F1: Neat Frame
- NF20C1: Neat Board
- NF25M1: Neat Board 32
- NF22H1: Neat Board 50
- NF23K1: Neat Board Pro
- NF23L1: Neat Center
Tools
Each tool below acts on one of the resources described previously: a device, room, location, or region. You won’t call these tools directly; you tell the agent what you want to achieve or the problem you want to solve, and your assistant picks the right tool and supplies the IDs.
Reading vs. changing:
- Most tools simply read information from Neat Pulse.
- Some tools update Neat devices and rooms such as moving a device or updating a config.
- A few make changes that can’t be undone: rebooting a device, resetting an enrolment code, and deleting a device, room, location or region. These are flagged with a warning where they appear.
Device Tools
These tools let you inspect and manage Neat devices in your organization. Your assistant starts with list_devices to find a device, then works with it from there, so you can simply refer to a device by its name or location.
list_devices
Lists every Neat device in the organization.
- Returns: For each device: its UUID, serial number, model code (see Device Models section below), assigned room, and current connection and call status.
get_device
Gets the full details for a single Neat device, including the latest sensor readings.
- Returns: Hardware info, firmware version, connection status, network configuration (type, IP addresses, MAC address, gateway), and room assignment.
Where the device has the sensors, you’ll also get temperature, humidity, CO₂, and people count.
reboot_device
Reboots a device remotely. Your assistant should ask for confirmation before rebooting.
- Warning: This reboots the device immediately. Any active call on that device will be dropped. Paired devices (e.g. a Neat Pad paired to a Neat Bar) will also reboot.
- Returns: A confirmation message that the reboot command was accepted. The device itself does not send a response.
delete_device
Removes a device from Neat Pulse.
- Warning: This is permanent. The device is removed from Neat Pulse and will no longer be manageable until it is re-enrolled. Re-enrolment requires physical access to the device and a valid room enrolment code.
- Returns: Confirmation with the deleted device’s UUID.
get_device_config
Gets the current configuration for a Neat device.
- Returns: The device’s full configuration, such as display, audio, framing, timezone and language.
apply_device_config
Apply configuration settings to a Neat device. Only the fields you provide are changed; omitted fields are left unchanged. Use get_device_config first to see the current configuration.
- Returns: The resulting configuration, such as display, audio, framing, timezone and language.
move_device
Moves a Neat device (and any devices paired to it) to a different room. Paired devices, such as a Neat Bar and its Neat Pad, move together.
- Returns: The IDs of all devices that were moved. If the destination room has a profile assigned and assign_room_profile is omitted, the device is not moved. A profile_confirmation_needed status is returned instead, so your assistant can ask whether to apply the profile and then repeat the request.
send_message_to_device
Displays a message on a Neat device’s screen. Your assistant should ask for confirmation before sending.
- Returns: A confirmation containing the device ID.
open_remote_control
Open the Pulse remote-control page for a Neat device in your browser. The session includes any devices paired to it, so you can interact with their screens.
- Returns: The remote-control URL. You must be signed in to the matching organization in Neat Pulse in your browser for the session to load and the device must be configured to allow remote control.
Room Tools
These tools let you list, inspect, create, and manage rooms in your organization. Rooms are containers for devices — when you enrol a device into a room, it inherits the room’s location and settings.
list_rooms
List all rooms in the organization.
- Returns: A list of room IDs and names. g
get_room
Gets details for a single room, including its devices and the latest sensor reading.
- Returns: Room name, location, list of enrolled devices (ID, serial, model, connection status), and active device enrolment code (if one exists), including its expiry time if the code has been used. Sensor readings (temperature, humidity, CO₂, people count) are included when available — rooms without active sensor devices will not have these fields.
create_room
Creates a new room in the organization.
- Returns: The new room’s ID, name, location (if assigned), and its device enrolment code.
update_room
Updates a room’s name and/or location.
- Note: If you omit
location_id, the room’s current location assignment is removed. Always include the existinglocation_idvalue if you only want to rename the room.
- Returns: The updated room details.
reset_enrolment_code
Resets the device enrolment code for a room.
- Warning: This immediately invalidates the existing code. Any in-progress device enrolment using the old code will fail.
- Returns: The new device enrolment code for the room.
delete_room
Permanently deletes a room from the organization.
- Warning: This is permanent and cascades to devices. All Neat devices enrolled in the room will be permanently deleted from Neat Pulse. They will need to be physically re-enrolled to be managed again. Check which devices are in the room before
- Returns: Confirmation with the deleted room’s ID.
send_message_to_room
Displays a message on the screens of all devices in a room. Your assistant should ask for confirmation before sending.
- Returns: A confirmation containing the room ID.
Location and Region Tools
These tools let you browse, update, and manage your location hierarchy.
list_regions
List all regions in the organization. Takes no inputs.
- Returns: A list of region IDs, names, and locations.
list_locations
List all locations in the organization. Takes no inputs.
- Returns: A list of location IDs, names, and regions. Use a location ID when calling
create_roomorupdate_roomto assign a room to a location.
create_location
Creates a location in the organization. A region can optionally be assigned.
- Returns: The new location.
update_location
Updates a location’s name and/or region.
- Returns: The updated location.
delete_location
Permanently deletes a location.
- Warning: This is permanent. If rooms are assigned to the location, the deletion still succeeds and the rooms lose their location assignment.
- Returns: Confirmation with the deleted location’s ID.
create_region
Creates a region in the organization.
- Returns: The new region.
update_region
Update a region’s name.
- Returns: The updated region.
delete_region
Permanently deletes a region.
- Warning: This is permanent. If locations are assigned to the region, the deletion still succeeds and the locations lose their region assignment.
- Returns: Confirmation with the deleted region’s ID.