Snipe-IT MCP server
Snipe-IT in any MCP client, through Memtro: Snipe-IT does not publish this server. Memtro's Snipe-IT connector reads Snipe-IT through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Snipe-IT IT asset management (self-hosted or hosted): hardware assets by search, status or tag and who holds them, a person's assets, licences, maintenances, the activity log and asset notes. Can add a note to an asset, create an asset, change an asset's name, serial, status or notes, delete an asset, check assets, licence seats, accessories, consumables and components out and in, record and delete maintenances, audit and restore assets, create locations, models, categories, manufacturers, status labels, licences and components, change a licence or a person's job details, and deactivate or reactivate a person.
Reads
snipeit_list_assetsSnipe-IT hardware assets, most recently updated first: tag, name, serial, model, category, status, who or where it is checked out to, location…snipeit_get_asset_by_tagOne Snipe-IT asset by its asset tag, with who holds it and its status.snipeit_list_usersSnipe-IT people: id, name, username, department, location, manager, and how many assets and licences they hold.snipeit_list_user_assetsThe assets currently checked out to one Snipe-IT user, by user id.snipeit_list_licensesSoftware licences in Snipe-IT: name, manufacturer, category, seats and free seats, expiry and termination dates, maintained.snipeit_list_maintenancesAsset maintenances (repairs, upgrades, calibrations): title, asset, supplier, type, start and completion dates, warranty.snipeit_list_activityThe Snipe-IT activity log, newest first: when, action (checkout, checkin, update, note added, audit…), who did it…snipeit_list_asset_notesNotes added to one Snipe-IT asset, newest first, with who added them (Snipe-IT 8.3.0 or later).snipeit_list_status_labelsSnipe-IT status labels (ids for creating or changing an asset's status) and whether each is deployable, pending, archived or undeployable.snipeit_list_modelsSnipe-IT asset models (ids for creating an asset): name, manufacturer, category, model number.snipeit_list_license_seatsThe seats of one Snipe-IT licence: seat id, and the user or asset it is assigned to.snipeit_list_accessoriesSnipe-IT accessories (keyboards, cables…): id, name, category, total and remaining quantity, location.snipeit_list_consumablesSnipe-IT consumables (toner, paper…): id, name, category, total and remaining quantity, location.snipeit_list_locationsSnipe-IT locations (ids for creating, checking in or auditing assets): id, name, parent location, manager, and how many assets are there.snipeit_list_categoriesSnipe-IT categories (ids for creating models, licences, accessories, consumables and components): id, name, and what kind of item each is for (asset…snipeit_list_manufacturersSnipe-IT manufacturers (ids for creating models and licences): id and name.snipeit_list_suppliersSnipe-IT suppliers (ids for licences and maintenances): id and name.snipeit_list_departmentsSnipe-IT departments (ids for snipeit_update_user): id, name, location, manager and how many people are in each.snipeit_list_componentsSnipe-IT components (parts such as RAM or drives, installed into assets): id, name, category, total and remaining quantity, location, model number.snipeit_list_component_assetsThe assets one Snipe-IT component is checked out to, with the quantity in each.
Acts, when you ask
These change something in Snipe-IT. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
snipeit_add_asset_noteAdds a note to a Snipe-IT asset's history, as the token's user (Snipe-IT 8.3.0 or later).snipeit_create_assetCreates a Snipe-IT hardware asset: a model id and status label id (see snipeit_list_models and snipeit_list_status_labels), an asset tag…snipeit_update_assetOVERWRITES.snipeit_checkout_assetNOTIFIES PEOPLE.snipeit_checkin_assetNOTIFIES PEOPLE.snipeit_create_maintenanceRecords a maintenance (repair, upgrade, calibration…) against a Snipe-IT asset: a title, the maintenance type id (from Snipe-IT's settings)…snipeit_checkout_license_seatNOTIFIES PEOPLE.snipeit_checkin_license_seatNOTIFIES PEOPLE.snipeit_create_accessoryCreates a Snipe-IT accessory record: a name, an accessory category id, a quantity, and optionally a location, model number and notes.snipeit_checkout_accessoryNOTIFIES PEOPLE.snipeit_checkin_accessoryNOTIFIES PEOPLE.snipeit_create_consumableCreates a Snipe-IT consumable record: a name, a consumable category id, a quantity, and optionally a location, item number and notes.snipeit_checkout_consumableNOTIFIES PEOPLE.snipeit_audit_assetLogs an audit of a Snipe-IT asset by its asset tag, as the token's user: records that it was seen today, sets the next audit date (the one given…snipeit_restore_assetRestores a soft-deleted Snipe-IT asset by id, bringing it back into every list with its history.snipeit_create_locationCreates a Snipe-IT location: a name, and optionally a parent location, manager (a Snipe-IT user id), company, address, currency and LDAP OU.snipeit_create_modelCreates a Snipe-IT asset model: a name and an asset category id (see snipeit_list_categories), and optionally a manufacturer id, model number…snipeit_create_categoryCreates a Snipe-IT category for assets, accessories, consumables, components or licences.snipeit_create_manufacturerCreates a Snipe-IT manufacturer by name.snipeit_create_status_labelCreates a Snipe-IT status label: a name and its type (deployable, pending, undeployable or archived), and optionally notes, a hex colour…snipeit_create_licenseCreates a Snipe-IT software licence record: a name, a seat count and a licence category id, and optionally a manufacturer, supplier, company…snipeit_update_licenseOVERWRITES.snipeit_create_componentCreates a Snipe-IT component stock record (parts such as RAM or drives): a name, a quantity and a component category id, and optionally a location…snipeit_checkout_componentChecks a quantity of a Snipe-IT component out to an asset (installs it), with an optional note.snipeit_checkin_componentChecks a quantity of a component back in from an asset, by the checkout's id (checkout_id from snipeit_list_component_assets…snipeit_update_userOVERWRITES.snipeit_set_user_activeCHANGES ACCESS.snipeit_delete_maintenanceDESTRUCTIVE.snipeit_delete_assetDESTRUCTIVE.
Connect it
First connect Snipe-IT on Dashboard → Connections, then add Memtro to your client once. The Snipe-IT tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Snipe-IT connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › 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
Questions
- Is this an official Snipe-IT MCP server?
- No. It is Memtro's MCP server with Memtro's Snipe-IT connector behind it: the connector reads Snipe-IT through its API with the credentials you connect on Dashboard → Connections, and Snipe-IT publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Snipe-IT?
- 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. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.