A leaver's equipment
Before Dan Fletcher's last day IT asks what he holds. Memtro reads his assets: a laptop, a monitor and a phone, plus two licence seats, and lists the asset tags so they can be checked in.
Ask Snipe-IT who has a laptop, and which licences are running out.
Connect Snipe-IT with your host and an API token and Memtro reads hardware assets with who holds them, a person's assets, licences with free seats, accessories, consumables, components, maintenances and the activity log. Licence keys are never read. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted them by name, it can check assets, licence seats, accessories and consumables out or in, which may email the person, create and change assets, licences and catalogue records, log audits and maintenances, and deactivate a person's sign-in. Deleting a maintenance record is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Snipe-IT tool, reads what it needs, and answers with the source cited.
These tools change something in Snipe-IT. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Snipe-IT is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Who has the laptop with tag ACME-0042?
What equipment does Dan Fletcher have checked out?
Which software licences expire in the next 60 days?
Which assets are ready to deploy?
Check laptop ACME-0117 out to Priya Nair
Before Dan Fletcher's last day IT asks what he holds. Memtro reads his assets: a laptop, a monitor and a phone, plus two licence seats, and lists the asset tags so they can be checked in.
The IT lead asks Memtro to check a ready laptop and a licence seat out to Priya Nair. With both actions granted, Memtro checks them out to her, and Snipe-IT may email her a checkout notice or an acceptance request under the category's settings.
The teams that lean on Snipe-IT most, a question each of them asks, and what they connect beside it.
A record in Snipe-IT is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Snipe-IT open (your name, top right) → Manage API Keys, using a dedicated user with only the permissions Memtro should have: view assets, licences, accessories and consumables, and create, update, check out, check in or delete only where you want those actions
Create New Token, name it Memtro, and copy it: it is shown once
In Connections → Snipe-IT in Memtro type your server's name in Host only, public over https with a trusted certificate, plus the Install path and port if needed, and paste the API token
Ask what Priya Sharma has checked out
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Snipe-IT tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note to an asset; create an asset, without checking it out; overwrite an asset's name, serial, status or notes; delete an asset that is not checked out (restorable by an administrator); check an asset out to a user, location or asset (may email the user); check an asset back in (may email the holder); create a maintenance record for an asset; assign a licence seat to a user or asset (may email the user); free a licence seat; create an accessory; check accessories out to a user, asset or location (may email the user); check an accessory checkout back in; create a consumable; hand consumables out to a user (may email the user); log an audit of an asset; restore a deleted asset; create a location; create an asset model; create a category (EULA and check-in emails off unless asked); create a manufacturer; create a status label; create a licence record, without its product key; overwrite a licence's name, seats, dates, cost or notes; create a component; install a quantity of a component in an asset; check a component checkout back in; overwrite a person's job title, department, location, manager, end date or notes; deactivate or reactivate a person's Snipe-IT sign-in; delete a maintenance record (permanent). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Host and API token. In Snipe-IT open (your name, top right) → Manage API Keys, using a dedicated user with only the permissions Memtro should have: view assets, licences, accessories and consumables, and create, update, check out, check in or delete only where you want those actions.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time