Snipe-IT

Provides an MCP-based interface to manage assets, consumables, files, labels, maintenance, and licenses in a Snipe-IT instance.
  • python

0

GitHub Stars

python

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "wil-collier-snipeit-mcp": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/snipeit-mcp",
        "run",
        "python",
        "server.py"
      ],
      "env": {
        "SNIPEIT_URL": "https://your-snipeit-instance.com",
        "SNIPEIT_TOKEN": "your-api-token-here"
      }
    }
  }
}

You run a dedicated MCP server that connects to your Snipe-IT instance, giving AI assistants controlled access to manage assets, consumables, files, labels, maintenance, and more. This server provides a structured set of tools to perform CRUD operations and operational actions against Snipe-IT, letting you automate tasks and workflows with confidence and safety.

How to use

You interact with the Snipe-IT MCP Server through an MCP client. Start the local server and choose a transport that fits your workflow. If you prefer a local, synchronous setup, run the server directly in your environment. If you want to access the server from another tool or machine, run it in a mode that communicates over HTTP.

How to install

Prerequisites you need before starting: Python 3.11 or higher, the UV package manager, and a running Snipe-IT instance with an API token that has the necessary permissions.

  1. Clone the project and open the directory.

  2. Install dependencies using UV.

# Install dependencies and create virtual environment
uv sync

# This will:
# - Create a virtual environment at .venv
# - Install fastmcp, requests, and snipeit-python-api
# - Set up the project for development

If you prefer a manual setup without UV, create a virtual environment and install the dependencies directly.

# Create virtual environment
uv venv --python 3.11

# Install dependencies
uv pip install fastmcp requests /Users/work/Documents/Projects/Inventory/snipeit-python-api
  1. Configure environment variables for your Snipe-IT instance. You can export them in your shell or place them in a .env file.
export SNIPEIT_URL="https://your-snipeit-instance.com"
export SNIPEIT_TOKEN="your-api-token-here"

Additional configuration and startup notes

If you want to run the server directly with Python, ensure the environment variables are set and start the server script.

# Run the server directly
export SNIPEIT_URL="https://your-snipeit-instance.com"
export SNIPEIT_TOKEN="your-api-token-here"

python server.py

To run the server with a FastMCP client for HTTP-based transport, use the following command to expose an HTTP endpoint that other tools can reach.

# Start the MCP server via HTTP transport
fastmcp run server.py:mcp --transport http --port 8000

Configuration for clients and environment variables

Two example client configurations shown here illustrate how to connect to the MCP server from common MCP clients. Each configuration passes the required connection details and security tokens to the client.

{
  "mcpServers": {
    "snipeit": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/snipeit-mcp",
        "run",
        "python",
        "server.py"
      ],
      "env": {
        "SNIPEIT_URL": "https://your-snipeit-instance.com",
        "SNIPEIT_TOKEN": "your-api-token-here"
      }
    }
  }
}

Maintaining and troubleshooting

If you encounter authentication or connectivity issues, verify that the Snipe-IT URL is reachable and that the API token is valid and has the correct permissions. Ensure the environment variables are exported or defined in a .env file and that the server has access to the Snipe-IT instance.

If a tool reports validation errors, check that required fields exist (for example, status_id and model_id for assets), and ensure related IDs are valid in your Snipe-IT instance.

Notes on usage patterns

You can organize workflows by using the grouped tools for assets and consumables, and specialized tools for files, maintenance, and licenses. This design minimizes cognitive load while delivering comprehensive functionality.

Available tools

manage_assets

CRUD operations for assets: create, get, list, update, delete.

asset_operations

State-changing actions for assets: checkout, checkin, audit, restore.

asset_files

Manage file attachments: upload, list, download, delete for assets.

asset_labels

Generate printable PDF labels for assets or asset tags.

asset_maintenance

Create maintenance records for assets.

asset_licenses

Query licenses checked out to assets.

manage_consumables

CRUD operations for consumables.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational