Snipe-IT MCP Server
This Snipe-IT MCP server lets Claude query and, when explicitly enabled, manage Snipe-IT IT asset data through the Snipe-IT API.
Check Snipe-IT connection status/API credentials and discover available tool domains.
List, search, filter, sort, and paginate hardware assets; get assets by ID or asset tag.
With write tools enabled: check assets in/out, record audits, create assets, and update asset fields.
List/get users and list assets assigned to a user.
List/get locations and list assets at a location.
List/get licenses and list license seat assignments.
List/get asset models, categories, manufacturers, and status labels; list assets by status label.
Operates read-only by default, with optional company scoping, field allowlists, and explicit write-tool opt-in.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Snipe-IT MCP Server list all unassigned laptops in the Austin office"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Snipe-IT MCP Server
A Model Context Protocol server for Snipe-IT — lets Claude query and manage your IT assets, users, locations, licenses, and more via natural language.
Built and maintained by TEC Building Systems LLC. Community contributions welcome!
Quick Start
// claude_desktop_config.json (or ~/.claude/settings.json for Claude Code)
{
"mcpServers": {
"snipeit": {
"command": "npx",
"args": ["-y", "@tecpabs/snipe-it-mcp"],
"env": {
"SNIPEIT_URL": "https://your-snipeit-instance.com",
"SNIPEIT_API_TOKEN": "your-api-token-here"
}
}
}
}Get your API token from Snipe-IT → Profile → API.
Secure by default: the server starts read-only and returns only an allowlisted set of fields. Enabling write tools, restricting the server to specific companies, and unlocking extra fields are all explicit operator settings — see Security configuration.
Related MCP server: Snipe-IT MCP Server
Configuration
Variable | Required | Description |
| Yes | Base URL of your Snipe-IT instance. Must be |
| Yes | Bearer token from your Snipe-IT profile |
| No | Write tools to enable: comma-separated names or |
| No | Restrict the server to these Snipe-IT company IDs. Default: unrestricted |
| No | Extra response fields to unlock, as |
| No |
|
| No |
|
| No | Request timeout in milliseconds (default |
Available Tools
Tools that create, update, check out, check in or audit are write tools: they are hidden and refused unless enabled with
SNIPEIT_WRITE_TOOLS.snipeit_reports_activityis unavailable whileSNIPEIT_ALLOWED_COMPANY_IDSis set.
Meta
Tool | Description |
| Check connection and credentials |
| Discover available domains |
Hardware (Assets)
Tool | Description |
| List assets with filters (status, category, location, search) |
| Get asset by ID |
| Get asset by asset tag |
| Get asset(s) by serial number |
| Check in an asset |
| Check out to user, location, or asset |
| Record an asset audit |
| Create a new asset |
| Update asset fields |
Users
Tool | Description |
| List users |
| Get user by ID |
| List assets assigned to a user |
| List accessories checked out to a user |
| List licenses assigned to a user |
Locations
Tool | Description |
| List locations |
| Get location by ID |
| List assets at a location |
Licenses
Tool | Description |
| List licenses |
| Get license by ID |
| List seat assignments |
Accessories
Tool | Description |
| List accessories with filters |
| Get accessory by ID |
| Who has an accessory (rows include the |
| Check out a unit to a user |
| Check in a unit (takes the assignment row ID, not the accessory ID) |
| Create / update accessories |
Consumables
Tool | Description |
| List consumables with filters |
| Get consumable by ID |
| Users a consumable has been issued to |
| Issue a unit to a user (no check-in — consumed) |
| Create / update consumables |
Components
Tool | Description |
| List components with filters |
| Get component by ID |
| Assets a component is installed in |
| Check out units to an asset |
| Check in units (takes the assignment row ID) |
| Create / update components |
Reports
Tool | Description |
| Activity audit trail (checkouts, checkins, updates, audits) filterable by item or user |
| Assets whose scheduled audit is due soon |
| Assets whose audit date has passed |
| Accessories/consumables/components below their minimum quantity (computed) |
Snipe-IT's web-UI "Custom Reports" CSV builder and depreciation report have no REST API equivalents, so they are not exposed here.
Models, Categories, Manufacturers, Status Labels
Tool | Description |
| Asset models |
| Categories |
| Manufacturers |
| Status labels |
| Assets with a given status |
Note: responses are filtered to a per-resource field allowlist (see Security configuration) and then compacted — null/empty fields and redundant
formatteddate strings are stripped. Ifhardware.custom_fieldsis unlocked, it is flattened to a{name: value}map.
Built-in Prompts
Use these with Claude's prompt selector:
asset-audit-report— Summarize all assets by location and statusexpiring-licenses— Find licenses expiring soonunassigned-assets— List deployable assets with no assignee
Local Development
git clone https://github.com/TECPabs/snipe-it-mcp.git
cd snipe-it-mcp
npm install
npm run build
# Point Claude Code at your local build:
# command: node, args: ["D:/Claude/snipe-it-mcp/dist/index.js"]Releasing
Releases are published to npm automatically by GitHub Actions when a version tag is pushed (via npm trusted publishing, so no npm tokens are stored in CI):
npm version minor # or patch / major — bumps package.json and creates the vX.Y.Z tag
git push --follow-tagsThe workflow refuses to publish if the tag doesn't match package.json, and the
prepublishOnly script runs build + tests + lint before any upload.
Security configuration
Every restriction in this section is enforced by the server's own code on every request — not by tool descriptions and not by instructions to the model. All defaults fail closed, and an invalid setting stops the server at startup with a non-zero exit code and a clear message on stderr.
Variable | Default | Effect |
| required | Must be |
| unset |
|
| empty = read-only server | Comma-separated write-tool names to enable, or |
| unset = no company restriction (warning logged at startup) | Comma-separated Snipe-IT company IDs the server may read and change. |
| empty = built-in field allowlist only | Comma-separated |
A placeholder-only .env.example lists all of them.
Transport
SNIPEIT_URLis rejected unless it ishttps://. Plainhttp://is accepted only forlocalhost,127.0.0.1or[::1], or withSNIPEIT_ALLOW_INSECURE_HTTP=true.URLs that do not parse, contain embedded credentials (
user:pass@host), or carry a query string or fragment are rejected.HTTP redirects are never followed (a redirect could downgrade to
http://or leave the configured host). SetSNIPEIT_URLto the final address.
Write tools — SNIPEIT_WRITE_TOOLS
The server is read-only unless you opt in. A tool is a write tool when it is
not annotated readOnlyHint: true; there is no separate hand-kept list.
"SNIPEIT_WRITE_TOOLS": "snipeit_hardware_checkout,snipeit_hardware_checkin" // or "*"Write tools that are not enabled are absent from
tools/listand rejected by the call handler (... is disabled by server policy).Defence in depth: the HTTP client itself refuses every
POST/PATCHunless the call is running inside an enabled write tool, so a mis-annotated tool cannot write.A name that is not a real tool stops the server at startup (typo protection).
Only API paths on a built-in route allowlist can be called at all.
Company scope — SNIPEIT_ALLOWED_COMPANY_IDS
When set, the server only shows and changes records whose company.id is in the
list. A record with no company is out of scope.
Path | Enforcement |
Lists and searches | Every row is checked on its own |
Get by ID / tag / serial | Fetched, then checked. An out-of-scope record returns |
Sub-resources (license seats, accessory check-outs, consumable users, component assets, a user's assets / accessories / licenses, a location's assets) | The parent record's company is checked first; nothing is fetched for an out-of-scope parent. Rows that carry their own company are filtered again. |
Writes | The target record, any check-out target (user / asset / location), any |
Reference data (categories, manufacturers, models, status labels) | Not company-specific, so still available — but instance-wide |
| Disabled while scope is active: activity rows carry no company and embed changed values of arbitrary fields, so they cannot be scoped soundly. |
Things to know before turning it on:
Locations are treated as company-owned. Snipe-IT releases whose locations have no
company(v6.x) therefore expose no locations while scope is active: the location tools return nothing, and check-outs to a location or writes that setlocation_idare refused. Assets still show their location as{id, name}.Check-ins by assignment row (
snipeit_accessories_checkin,snipeit_components_checkin) additionally requireid— the accessory / component the row belongs to — so the server can verify the row's owner.Nested references on an in-scope record (for example
assigned_to) are shown as{id, name, …}without a scope check of their own.This complements, and does not replace, a least-privilege API token and the Full Multiple Companies Support setting in Snipe-IT.
Field allowlist — what responses contain
Every response — lists, single records, sub-resources, reports and the payload
of write responses — passes through one central per-resource allowlist. Anything
not listed is dropped, including fields added by future Snipe-IT versions. Nested
references are reduced to {id, name} plus type / asset_tag / serial /
username where present.
Resource | Fields returned by default |
| id, name, asset_tag, serial, model, model_number, category, manufacturer, status_label, company, location, rtd_location, assigned_to, purchase_date, warranty_months, warranty_expires, asset_eol_date, eol, last_audit_date, next_audit_date, last_checkout, last_checkin, expected_checkin, user_can_checkout, created_at, updated_at, deleted_at |
| id, name, first_name, last_name, username, email, jobtitle, department, location, company, assets_count, licenses_count, accessories_count, consumables_count, created_at, updated_at, deleted_at |
| id, name, company, manufacturer, category, seats, free_seats_count, min_amt, reassignable, maintained, purchase_date, expiration_date, termination_date, user_can_checkout, created_at, updated_at, deleted_at |
license seats | id, license_id, name, assigned_user, assigned_asset, location, reassignable, user_can_checkout |
| id, name, model_number, company, manufacturer, category, location, qty, min_qty, min_amt, remaining_qty, remaining, users_count, checkouts_count, purchase_date, user_can_checkout, created_at, updated_at |
accessory check-outs | assigned_pivot_id, id, name, username, first_name, last_name, type, assigned_to, last_checkout, created_at |
| id, name, item_no, model_number, company, manufacturer, category, location, qty, min_qty, min_amt, remaining_qty, remaining, purchase_date, user_can_checkout, created_at, updated_at |
consumable users | id, name, user, admin, created_at |
| id, name, serial, company, category, location, qty, min_qty, min_amt, remaining_qty, remaining, purchase_date, user_can_checkout, created_at, updated_at |
component assets | assigned_pivot_id, id, name, asset_tag, qty, type, created_at |
| id, name, parent, company, assets_count, assigned_assets_count, rtd_assets_count, users_count, created_at, updated_at |
| id, name, model_number, manufacturer, category, eol, min_amt, requestable, assets_count, created_at, updated_at, deleted_at |
| id, name, category_type, item_count, assets_count, accessories_count, consumables_count, components_count, licenses_count, created_at, updated_at |
| id, name, url, support_url, support_phone, support_email, warranty_lookup_url, assets_count, licenses_count, consumables_count, accessories_count, created_at, updated_at, deleted_at |
| id, name, type, default_label, assets_count, created_at, updated_at |
| id, action_type, action_date, next_audit_date, item, target, admin, location, created_at, updated_at |
Never returned by default: license product_key, license_name,
license_email; notes on every resource; custom_fields; purchase cost, order
numbers and supplier data; user phone, address, city, state, zip, country,
employee number, manager, permissions, two-factor fields, avatar, last login,
notes, activation and LDAP flags; activity note, log_meta, IP and user agent.
Because the search, sort and filter parameters of the Snipe-IT API also
reach hidden columns, the server closes those side channels too: only a fixed set
of query parameters is forwarded, sort is limited to visible fields, and a
search result row is returned only if the term matches a field you can
actually see.
SNIPEIT_EXTRA_FIELDS
The one operator-controlled extension. Each entry is resource.field and must
come from this list — anything else stops the server at startup:
Resource | Unlockable fields |
| custom_fields, notes, order_number, purchase_cost, book_value, supplier, requestable, byod, age, checkin_counter, checkout_counter, requests_counter |
| phone, employee_num, manager, address, city, state, zip, country, notes, last_login, activated, ldap_import, vip, start_date, end_date |
| notes, order_number, purchase_order, purchase_cost, supplier, license_name, license_email, depreciation |
| notes, order_number, purchase_cost, supplier |
| address, address2, city, state, zip, country, phone, fax, manager, currency |
| notes, depreciation, fieldset |
| notes, color |
| note |
licenses.product_key can never be unlocked, nor can user permissions,
two-factor fields, avatars, or the log_meta of the activity report.
"SNIPEIT_EXTRA_FIELDS": "hardware.custom_fields,hardware.notes"Errors and logging
Upstream response bodies (HTML, stack traces, JSON) are never placed in an error. A failed request becomes
Snipe-IT request failed (HTTP 404) [ref: a1b2c3d4]; the same correlation ID is written to stderr with the method, path and status only.Snipe-IT
{"status":"error","messages":…}text is passed on only after sanitizing: one line,field: messagepairs, bounded length and count, with URLs, SQL, file paths and anything token-like removed.snipeit_statusreturns only connected / not connected and the instance host.Logs go to stderr and pass through central redaction: values of keys matching
token|authorization|password|secret|api_key|cookie,Bearer …strings and the live API token are replaced, and string length and nesting depth are capped.LOG_LEVEL=debuglogs the method, the path and query parameter names — never values, headers or bodies.
Still your responsibility
Use a least-privilege API token. Snipe-IT tokens inherit every permission of the user who created them. Create a dedicated user (e.g.
claude-mcp) with only the permissions you want Claude to have and generate the token from that account, not from a superadmin. The settings above limit what this server will do with the token; they do not limit the token itself.Write tools send only their documented fields. Bodies for create, update, checkout, checkin, and audit are filtered against an allowlist, so unexpected extra arguments are never forwarded to the API.
Treat asset data as untrusted. Names stored in Snipe-IT are shown to the model; anyone who can edit them can attempt prompt injection. Keep write confirmation enabled in your MCP client.
Upgrading from 1.4.x
These defaults are intentionally stricter than earlier releases:
All write tools are disabled until listed in
SNIPEIT_WRITE_TOOLS.Responses no longer include
notes,custom_fields, cost / order / supplier data, license keys or user contact and HR fields (seeSNIPEIT_EXTRA_FIELDS).An
http://SNIPEIT_URLfor a non-loopback host stops the server at startup, and redirects are no longer followed.snipeit_statusno longer reportstotal_assets, and error messages no longer contain upstream response text.Query parameters that are not part of a tool's documented inputs are dropped, and
searchonly returns rows that match on a visible field.
Contributing
Pull requests welcome! Areas that would benefit from community help:
Companies and departments lookups
License seat checkout/checkin
Asset maintenance records
Custom fields support (writing; reading is available via
SNIPEIT_EXTRA_FIELDS=hardware.custom_fields)Bulk operations
Please open an issue first for major changes.
License
MIT — see LICENSE
Available Tools
28 toolssnipeit_categories_getA
Get a category by ID
Inputs: id (required).
snipeit_categories_listB
List asset categories
Inputs: sort, limit, order, offset, +1 more.
snipeit_hardware_auditC
Record an audit on an asset
Inputs: asset_tag (required), note, location_id.
snipeit_hardware_by_tagB
Get a hardware asset by asset tag
Inputs: asset_tag (required).
snipeit_hardware_checkinB
Check in an asset (unassign it)
Inputs: id (required), note.
snipeit_hardware_checkoutB
Check out an asset to a user, location, or another asset
Inputs: id (required), checkout_to_type (required), note, assigned_user, +3 more.
snipeit_hardware_createB
Create a new hardware asset
Inputs: model_id (required), asset_tag (required), status_id (required), name, +6 more.
snipeit_hardware_getC
Get a hardware asset by ID
Inputs: id (required).
snipeit_hardware_listB
List hardware assets with optional filters
Inputs: sort, limit, order, offset, +6 more.
snipeit_hardware_updateC
Update fields on an existing asset
Inputs: id (required), name, notes, serial, +5 more.
snipeit_licenses_getC
Get a license by ID
Inputs: id (required).
snipeit_licenses_listC
List software licenses
Inputs: sort, limit, order, offset, +3 more.
snipeit_licenses_seatsA
List all seats for a license (who has it assigned)
Inputs: id (required).
snipeit_locations_assetsA
List assets at a location
Inputs: id (required).
snipeit_locations_getB
Get a location by ID
Inputs: id (required).
snipeit_locations_listC
List all locations
Inputs: sort, limit, order, offset, +1 more.
snipeit_manufacturers_getC
Get a manufacturer by ID
Inputs: id (required).
snipeit_manufacturers_listC
List manufacturers
Inputs: sort, limit, order, offset, +1 more.
snipeit_models_getA
Get an asset model by ID
Inputs: id (required).
snipeit_models_listC
List asset models
Inputs: sort, limit, order, offset, +3 more.
snipeit_statusA
Check Snipe-IT connection status and API credentials
Inputs: no named parameters.
snipeit_statuslabels_assetsA
List assets with a given status label
Inputs: id (required).
snipeit_statuslabels_getC
Get a status label by ID
Inputs: id (required).
snipeit_statuslabels_listC
List status labels
Inputs: sort, limit, order, offset, +1 more.
snipeit_users_assetsA
List all assets assigned to a user
Inputs: id (required).
snipeit_users_getC
Get a user by ID
Inputs: id (required).
snipeit_users_listC
List users with optional search/filter
Inputs: sort, limit, order, offset, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 28 tools
Tools are clearly namespaced by resource and action, so hardware, users, locations, licenses, and status labels are easy to distinguish. The only mild overlaps are hardware_get versus hardware_by_tag and resource-specific asset listing versus hardware_list, but the descriptions clarify the different identifiers and filters.
The dominant pattern is snipeit_<resource>_<action>, which is applied consistently across most tools. Exceptions like snipeit_status, snipeit_navigate, and snipeit_hardware_by_tag break the strict pattern but are still intuitive and do not create confusion.
28 tools is heavy for an MCP server, but the breadth of Snipe-IT domains—hardware, users, locations, licenses, models, categories, manufacturers, and status labels—partly justifies the count. Still, many resources only have list/get pairs, which inflates the surface without adding much capability.
Hardware lifecycle coverage is strong with create, update, read, checkin, checkout, and audit. However, users, locations, licenses, models, categories, manufacturers, and status labels are mostly read-only, so the server cannot fully manage the asset database or create new assignable entities.
Related MCP Connectors
Connect Claude to your Platform7n workspaces: chat, links, work and decks. One-click OAuth.
Connect Claude to your Platform7n workspaces: chat, links, work and decks. One-click OAuth.
Create contacts, move deals, send proposals and invoices, read your inbox, from Claude or ChatGPT.
Connect your Odoo to Claude and ChatGPT: ask about sales, stock, customers and invoices.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Snipe-IT inventory systems through comprehensive asset and consumable operations. Supports creating, updating, tracking, and managing IT assets, consumables, maintenance records, file attachments, and generating labels.1-
- AlicenseAqualityAmaintenanceEnables AI assistants to perform full CRUD operations on Snipe-IT inventory systems, managing assets, users, licenses, and more via 39 tools.4041MIT
- FlicenseCqualityDmaintenanceConnects Claude to your Freshservice ITSM instance, enabling management of tickets, changes, assets, knowledge base, and more through natural language.701-
- FlicenseNot gradedqualityDmaintenanceConnects Claude Desktop to the IT Asset Tracker backend, enabling natural language management of assets, users, requests, and reports via 70+ auto-generated tools.-