Matterport
for LuumenAI
Search your Matterport models, check details, and archive the ones you are done with
Connect Matterport and your 3D capture library becomes something you can query from the terminal. Search models across sites, pull the details on a single scan, check which room classifications are in use, and see what webhook callbacks are registered for model events. When a model needs to be archived or removed, that change is previewed and approved first. Luumen authenticates with basic auth.
The Matterport toolbox
6 tools: 4 read, 2 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Model by IDRetrieve detailed information about a single Matterport 3D model by its ID.
- ReadGet Model Event Webhook CallbacksRetrieve a list of registered webhook callback configurations for model events.
- ReadQuery Matterport ModelsRetrieve a page of Matterport models with optional search and filtering.
- ReadList Room ClassificationsList all room classifications defined for Matterport room classification models.
- WriteDelete Matterport ModelPermanently delete a Matterport model. Approval by default
- WriteUpdate Model StateChange a Matterport model between active and inactive (archived) states. Approval by default
One prompt, start to finish
What a governed Matterport run looks like inside Luumen.
Questions
Authorize once with Basic auth. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — delete matterport model, update model state — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Matterport — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Matterport to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.