Looks up a storage site by ID or code with its related units, and resolves admin accounts individually or in bulk.
3actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Retrieve a specific site by ID or code.
Each card is one request a support team gets, and the Storeganise actions Ayro runs to close it.
Ayro 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.
Ayro 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.
Ayro 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.
When a request needs a person, Ayro 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.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Storeganise actions it has and picks the ones a request needs.
Authorize the Storeganise account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Storeganise actions that close it and chains as many as the request needs.
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 freeStoreganise · Ayro
What can you do in Storeganise without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro 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.
All 3 actions your agent can call on Storeganise, straight from the live MCP connection.
Retrieve a specific site by ID or code.
Retrieve a specific admin user by ID or email.
Fetch multiple admin users by their IDs.
Same connection, same setup. Pick the next one your team already uses.
Reads and writes Coda table rows, creates pages and folders, manages doc permissions, and triggers the automations and buttons a doc already has.
Creates and edits forms in atomic batches, publishes them, reads submissions incrementally, and keeps Pub/Sub watches renewed.
Searches and reads 3D models, archives or restores them, and shows which webhook callbacks are registered for model events.
Pulls a subscriber's plan and invoices, quotes an upgrade before it is created, corrects billing details, and checks what their plan entitles them to.
Reports where a job and its balance stand, books shoots with their events and contacts, takes payments against orders, and shares galleries.
Answers where a task stands and what blocks it, files requests as tasks with attachments, moves approvals along, and launches blueprints for repeat projects.

Authorize the account and your agent has all 3 actions from the first conversation.
