itemit-mcp

itemit-mcp is an MCP server for asset tracking, providing a bridge between the itemit asset management API and the Model Context Protocol (MCP) ecosystem.

Built and maintained by the uminai MCP team.

Table of Contents

• Overview

• Prerequisites

• Obtaining itemit API Credentials

• Installation & Build

• MCP Client Configuration

• Environment Variables

• Available MCP Tools

• Example Usage

• Response Format

• Credits & Further Resources

Related MCP server: Trakt

Overview

itemit-mcp exposes a set of tools for interacting with the itemit asset management platform via the MCP protocol. It allows you to search, create, and manage assets and locations programmatically, making it easy to integrate itemit with other MCP-enabled systems. Following tools available:

• Get List of items

• Get item by name search

• Create item

• Location Search (With item list on it)

Prerequisites

• Node.js (v16+ recommended)

• Access to an itemit account (to obtain API credentials)

• MCP Client (see uminai MCP for more info)

Obtaining itemit API Credentials

To use this MCP server, you need API credentials from itemit:

• ITEMIT_API_KEY

• ITEMIT_USER_ID

• ITEMIT_USER_TOKEN

• ITEMIT_WORKSPACE_ID

You can obtain these by signing up or logging in at itemit and following their API documentation or contacting their support.

Installation & Build

Clone this repository and install dependencies:

Build the project:

MCP Client Configuration

Add the following to your MCP Client configuration (e.g., cline_mcp_settings.json):

Replace the placeholder values with your actual itemit credentials.

Environment Variables

• ITEMIT_API_KEY: Your itemit API key

• ITEMIT_USER_ID: Your itemit user ID

• ITEMIT_USER_TOKEN: Your itemit user token

• ITEMIT_WORKSPACE_ID: Your itemit workspace ID

These can be set in your environment or in a .env file.

Available MCP Tools

1. get-location-by-name

• Description: Get locations by name in itemit.

• Parameters:

  • name (string, required): Name of the location to search for

  • limit (integer, optional): Number of locations to retrieve (default 25, max 100)

  • skip (integer, optional): Number of locations to skip (default 0)

• Example:

  { "name": "Warehouse" }

2. search-item-by-name

• Description: Search for items by name in itemit.

• Parameters:

  • name (string, required): Name of the item to search for

  • size (integer, optional): Number of items to retrieve (default 15, max 100)

  • page (integer, optional): Page number (default 1)

• Example:

  { "name": "Laptop" }

3. create-item

• Description: Create an item in itemit.

• Parameters:

  • name (string, required): Name of the item

  • description (string, required): Description of the item

  • serial (string, required): Serial number of the item

• Example:

  { "name": "Projector", "description": "Epson HD Projector", "serial": "SN123456" }

4. get-reminders

• Description: Get reminders from itemit.

• Parameters: None

5. get-items

• Description: Get items from itemit.

• Parameters:

  • size (integer, optional): Number of items to retrieve (default 15, max 100)

• Example:

  { "size": 10 }

Example Usage

Use your MCP Client to invoke these tools. For example, to search for an item:

Response Format

All responses are returned as structured text or JSON, matching the itemit API's data model. For example, a successful search might return:

Credits & Further Resources

• Project by the uminai MCP team.

• Powered by itemit.

• Discover more MCP servers and integrations at mcp.umin.ai.