snipeit-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SNIPEIT_URL | No | Your Snipe-IT instance URL. Overrides the value saved in ~/.config/snipeit-mcp/config.json by `npx -y snipeit-mcp setup`. | |
| SNIPEIT_API_TOKEN | No | Your Snipe-IT personal API token (Snipe-IT: avatar > Manage API Keys). Overrides the value saved in ~/.config/snipeit-mcp/config.json. | |
| SNIPEIT_READ_ONLY | No | Set to 1 to hide every write tool (read-only mode). Useful for less-trusted agents. | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listA | List or search Snipe-IT records of one resource type. Returns {total, offset, rows}. Pass user_id to get hardware, accessories or licenses checked out to a user. filters = resource-specific query params (see describe). |
| getC | Fetch one Snipe-IT record by numeric id. |
| lookupA | Resolve a hardware asset by asset_tag or serial, or a user by username, email or employee_num, to full records with numeric ids. |
| describeB | Fields accepted by create/update and the list filters for a resource. For hardware also lists the instance's custom fields. |
| createA | Create a Snipe-IT record. Call describe first for required fields. |
| updateC | Partially update a Snipe-IT record (only the given fields change). |
| deleteA | Delete a Snipe-IT record (soft delete where Snipe-IT supports it; see restore). Requires confirm: true. |
| restoreB | Restore a soft-deleted record. Snipe-IT supports this for hardware, users, models and manufacturers. |
| checkoutA | Check an item out. hardware -> user|asset|location; accessories, consumables -> user; components -> asset; licenses -> user|asset (first free seat is used). |
| checkinA | Check an item back in. hardware: just the id. accessories/licenses: pass from_user_id (or from_asset_id for licenses). components: pass from_asset_id. |
| auditB | Record an audit for a hardware asset, optionally moving it and setting the next audit date. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool maps to a distinct operation: list/search vs get-by-id vs lookup-by-human-identifier, plus CRUD, restore, checkout/checkin, and audit. Descriptions clearly differentiate retrieval modes and checkout/checkin semantics, leaving little risk of misselection.
All tool names are concise lowercase verbs (list, get, lookup, create, update, delete, restore, checkout, checkin, audit), following a consistent action-oriented convention. No mixed casing or competing naming styles.
Eleven tools is well-scoped for a Snipe-IT API wrapper, covering core record and lifecycle operations without excessive per-resource duplication. Generic resource-type tools keep the surface compact.
The set covers discovery/description, CRUD, soft-delete/restore, checkout/checkin, and auditing, which are the core Snipe-IT asset-management lifecycle operations. Remaining gaps, such as reporting or label printing, are peripheral rather than dead ends in the primary workflow.