Can Lyro create or change a booking in Storeganise?

No. All three connected actions are reads on the admin side - Get Admin Site by ID or Code, Get Admin User By ID or Email, and Get Admin Users By IDs. Bookings, billing, and unit changes are made in Storeganise itself.

Does Lyro need the site ID, or will the site code do?

Either works. Get Admin Site by ID or Code accepts both, and can optionally include related resources such as units, so the short code your team uses day to day is enough to pull the full site record.

Can Lyro look up a storage customer, or only staff?

Only admin accounts. Get Admin User By ID or Email and Get Admin Users By IDs both resolve admin users, so end-customer records are outside what this connection reaches.

Is there a faster path than resolving admin users one at a time?

Yes. Get Admin Users By IDs returns several accounts in one call once the IDs are known, which is what Lyro uses when a request references a list of accounts rather than a single person.

Storeganise MCP integration

Looks up a storage site by ID or code with its related units, and resolves admin accounts individually or in bulk.

Connect Storeganise See all integrations

3actions available

What your agent can do with Storeganise

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

Retrieve a specific site by ID or code.

See all 3 actions

How businesses use Storeganise + Lyro

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

Pull a site's record, units included
Lyro retrieves the site by its ID or its short code and can include related resources such as units, so a question about one facility is answered from the live record rather than from a spreadsheet of sites.
Get Admin Site by ID or CodeGet Admin Users By IDs
Match an internal request to a real admin account
Lyro resolves the admin user by email or ID when a request comes in, so the person asking is identified against Storeganise before anything is acted on or escalated.
Get Admin User By ID or EmailGet Admin Site by ID or Code
Resolve a whole set of admin accounts at once
Lyro fetches several admin users by their IDs in a single call, turning a list of identifiers from a report or an audit into named accounts without a lookup per row.
Get Admin Users By IDsGet Admin User By ID or Email
Escalate with the site and the account already resolved
When a request needs a person, Lyro hands over the site record and the matched admin account alongside the conversation, so the colleague picking it up does not repeat the same two lookups.
Get Admin Site by ID or CodeGet Admin User By ID or Email

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 Storeganise actions it has and picks the ones a request needs.

01
Connect Storeganise
Authorize the Storeganise 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 Storeganise 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

Storeganise · Lyro

Everything else about Storeganise

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

No. All three connected actions are reads on the admin side - Get Admin Site by ID or Code, Get Admin User By ID or Email, and Get Admin Users By IDs. Bookings, billing, and unit changes are made in Storeganise itself.