Can Lyro upload a new scan or create a share link for a space?

No. The six actions here query, read, archive, and delete models that already exist. Capturing or uploading a scan and generating share links stay in Matterport's own apps, so Lyro works with the library rather than adding to it.

What is the difference between archiving and deleting a model?

Update Model State moves a model between active and inactive and is idempotent, so it can be run again safely and reversed. Delete Matterport Model removes the model from the platform permanently and cannot be undone - archive first, delete only behind human approval.

Can Lyro register a new webhook for model events?

No, Get Model Event Webhook Callbacks only reads the callbacks already configured. It is useful for diagnosing why a downstream system stopped hearing about created, deleted, updated, processed, or transferred events, but registering a new one happens in Matterport.

Does List Room Classifications tell Lyro which rooms are in a specific space?

Not quite. It returns the room types and associated keywords defined for Matterport's room classification models - the vocabulary, not the per-model result. For details about one space, Lyro reads the model itself through Get Model by ID.

Matterport MCP integration

Searches and reads 3D models, archives or restores them, and shows which webhook callbacks are registered for model events.

Connect Matterport See all integrations

6actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Update model state
Lyro changes a 3D model between active and archived status. Support teams quickly hide outdated models from view.
Get model by ID
Lyro retrieves detailed information about a Matterport 3D model. Agents confirm model details when customers reference them.
Query matterport models
Lyro searches Matterport models with filters and keywords. Support agents locate specific properties for customers quickly.

See all 6 actions

How businesses use Matterport + Lyro

Each card is one request a support team gets, and the Matterport actions Lyro runs to close it.

Find the right space out of a large model library
Lyro searches and filters the organisation's models, then opens the match to report its publication state, spatial details, and the room types it was classified against.
Query Matterport ModelsGet Model by IDList Room Classifications
Archive the spaces nobody is touring any more
Lyro identifies the models that have gone quiet and flips them to inactive, keeping the working library short while the scans themselves stay recoverable.
Update Model StateQuery Matterport ModelsGet Model by ID
Confirm which model events are being listened for
Lyro lists the registered webhook callbacks so a team can see whether created, updated, processed, or transferred events are actually reaching their downstream system.
Get Model Event Webhook CallbacksQuery Matterport ModelsGet Model by ID
Clear out duplicate scans from a reshoot
After a space is rescanned, Lyro checks the superseded model's details, archives it for a grace period, and removes it once the replacement is confirmed published.
Get Model by IDUpdate Model StateDelete Matterport Model

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Matterport actions it has and picks the ones a request needs.

01
Connect Matterport
Authorize the Matterport account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Matterport actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Matterport · Lyro

Everything else about Matterport

Setup, permissions, and the limits of what Lyro can do inside Matterport.

No. The six actions here query, read, archive, and delete models that already exist. Capturing or uploading a scan and generating share links stay in Matterport's own apps, so Lyro works with the library rather than adding to it.

Every action available in Matterport

All 6 actions your agent can call on Matterport, straight from the live MCP connection.

Delete matterport model
Permanently delete a Matterport model.
Get model by ID
Retrieve detailed information about a single Matterport 3D model by its ID.
Get model event webhook callbacks
Retrieve a list of registered webhook callback configurations for model events.
Query matterport models
Retrieve a page of Matterport models with optional search and filtering.
List room classifications
List all room classifications defined for Matterport room classification models.
Update model state
Change a Matterport model between active and inactive (archived) states.