Integrate with itemit Asset Management
MCP server bridging itemit's asset management API - search, create, and locate physical assets, plus reminders, through 5 conversational tools.
Maintainer of this project? Claim this page to edit the listing.
ProductionAdd to Favorites
Why it matters
Programmatically manage your assets and locations within the itemit platform. This connector allows for searching, creating, and retrieving asset data, streamlining your asset tracking operations.
Outcomes
What it gets done
Search and retrieve assets by name.
Create new items with descriptions and serial numbers.
Get a list of items with pagination.
Search locations with item lists.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/vb-itemit-mcp | bash Capabilities
Tools your agent gets
Get locations by name in itemit
Search for items by name in itemit
Create an item in itemit
Get reminders from itemit
Get items from itemit
Overview
itemit MCP Server
An MCP server bridging the itemit asset management API, exposing five tools to search assets and locations by name, create new asset records, list items, and check reminders through an MCP-enabled AI assistant. Use for conversational itemit asset search, creation, and browsing. Requires an itemit account and four API credentials; scoped to the five documented operations, not updates, deletion, or check-in/out workflows.
What it does
itemit-mcp bridges the itemit asset management platform's API to the Model Context Protocol, letting an MCP client search, create, and manage physical assets and their locations programmatically instead of through itemit's own web or mobile interface. It's built and maintained by the uminai MCP team.
Five tools are exposed. get-location-by-name searches for locations by name, with optional limit (default 25, max 100) and skip parameters for pagination. search-item-by-name searches for assets by name, with optional size (default 15, max 100) and page parameters. create-item registers a new asset, requiring name, description, and serial number. get-reminders retrieves reminders from itemit with no parameters. get-items lists items with an optional size parameter (default 15, max 100).
{
"tool": "search-item-by-name",
"arguments": { "name": "Laptop" }
}
Responses come back as structured text or JSON matching itemit's own data model - for example, a search for "Laptop" might return a numbered list of matching assets with their itemit IDs ("1. Dell XPS 13 (ID: 1234)\n2. MacBook Pro (ID: 5678)").
When to use - and when NOT to
Use this connector when you want an AI assistant to search for or register physical assets and locations in itemit conversationally - finding equipment by name, creating new asset records with serial numbers, checking reminders, or browsing the asset inventory - rather than navigating itemit's own UI. It requires an existing itemit account and four API credentials issued by itemit (ITEMIT_API_KEY, ITEMIT_USER_ID, ITEMIT_USER_TOKEN, ITEMIT_WORKSPACE_ID), obtained by signing into itemit and following their API documentation, so it cannot be used without an active itemit workspace. Its scope is limited to the five documented operations - it does not cover asset updates, deletion, check-in/check-out workflows, or other itemit features beyond search, creation, item listing, location lookup, and reminders.
Capabilities
Location search by name with pagination; asset search by name with pagination; new-asset creation with name, description, and serial number; reminder retrieval; and paginated item listing. Responses come back as structured text or JSON matching itemit's own data model, listing matched assets/locations with their itemit IDs, or confirming a newly created item. Wraps the itemit REST API directly.
How to install
Requires Node.js v16 or later and an existing itemit account for the four API credentials (ITEMIT_API_KEY, ITEMIT_USER_ID, ITEMIT_USER_TOKEN, ITEMIT_WORKSPACE_ID), obtained by signing into itemit and following their API documentation. Clone the repository, run npm install followed by npm run build to produce the build/index.js entrypoint, then set the four credentials in the shell environment, a .env file, or the MCP client's server configuration (e.g. a cline_mcp_settings.json entry running build/index.js via Node.js over stdio).
Who it's for
Teams using itemit for physical asset tracking who want to search, create, and browse assets and locations conversationally through an MCP-enabled AI assistant instead of the itemit web or mobile app.
Source README
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
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_KEYITEMIT_USER_IDITEMIT_USER_TOKENITEMIT_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:
npm install
Build the project:
npm run build
MCP Client Configuration
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.
Environment Variables
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.
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 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" }
2. search-item-by-name
- 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" }
3. create-item
- 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" }
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:
{
"tool": "search-item-by-name",
"arguments": {
"name": "Laptop"
}
}
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:
{
"content": [
{
"type": "text",
"text": "Search results for \"Laptop\" (size=15):\n1. Dell XPS 13 (ID: 1234)\n2. MacBook Pro (ID: 5678)\n..."
}
]
}
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.