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.
- Overview
- Prerequisites
- Obtaining itemit API Credentials
- Installation & Build
- MCP Client Configuration
- Environment Variables
- Available MCP Tools
- Example Usage
- Response Format
- Credits & Further Resources
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)
- Node.js (v16+ recommended)
- Access to an itemit account (to obtain API credentials)
- MCP Client (see uminai MCP for more info)
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.
Clone this repository and install dependencies:
npm install
Build the project:
npm run build
Add the following to your MCP Client configuration (e.g., cline_mcp_settings.json
):
{
"mcpServers": {
"itemit-mcp": {
"disabled": false,
"timeout": 60,
"type": "stdio",
"command": "node",
"args": [
"/Users/<user>/Documents/itemit-mcp/build/index.js"
],
"env": {
"ITEMIT_API_KEY": "<YOUR_API_KEY>",
"ITEMIT_USER_ID": "<YOUR_USER_ID>",
"ITEMIT_USER_TOKEN": "<YOUR_USER_TOKEN>",
"ITEMIT_WORKSPACE_ID": "<YOUR_WORKSPACE_ID>"
}
}
}
}
Replace the placeholder values with your actual itemit credentials.
ITEMIT_API_KEY
: Your itemit API keyITEMIT_USER_ID
: Your itemit user IDITEMIT_USER_TOKEN
: Your itemit user tokenITEMIT_WORKSPACE_ID
: Your itemit workspace ID
These can be set in your environment or in a .env
file.
- Description: Get locations by name in itemit.
- Parameters:
name
(string, required): Name of the location to search forlimit
(integer, optional): Number of locations to retrieve (default 25, max 100)skip
(integer, optional): Number of locations to skip (default 0)
- Example:
{ "name": "Warehouse" }
- Description: Search for items by name in itemit.
- Parameters:
name
(string, required): Name of the item to search forsize
(integer, optional): Number of items to retrieve (default 15, max 100)page
(integer, optional): Page number (default 1)
- Example:
{ "name": "Laptop" }
- Description: Create an item in itemit.
- Parameters:
name
(string, required): Name of the itemdescription
(string, required): Description of the itemserial
(string, required): Serial number of the item
- Example:
{ "name": "Projector", "description": "Epson HD Projector", "serial": "SN123456" }
- Description: Get reminders from itemit.
- Parameters: None
- Description: Get items from itemit.
- Parameters:
size
(integer, optional): Number of items to retrieve (default 15, max 100)
- Example:
{ "size": 10 }
Use your MCP Client to invoke these tools. For example, to search for an item:
{
"tool": "search-item-by-name",
"arguments": {
"name": "Laptop"
}
}
All responses are returned as structured text or JSON, matching the itemit API's data model. For example, a successful search might return:
{
"content": [
{
"type": "text",
"text": "Search results for \"Laptop\" (size=15):\n1. Dell XPS 13 (ID: 1234)\n2. MacBook Pro (ID: 5678)\n..."
}
]
}
- Project by the uminai MCP team.
- Powered by itemit.
- Discover more MCP servers and integrations at mcp.umin.ai.