mcpField
I
Itemit MCP Server

Itemit MCP Server

Local
github.com/umin-aiDeveloper Tools0Updated 70w ago

About Itemit MCP Server

itemit-mcp connects the itemit asset-management platform to MCP for users who need to query and manage assets and locations programmatically. Its tools cover asset search and creation, location lookup, reminders, and item listings.

Key features

  1. 01Search assets by name
  2. 02Create assets
  3. 03Find locations by name
  4. 04Retrieve reminders
  5. 05List assets

Use cases

  1. 01Looking up asset records in itemit
  2. 02Adding assets with descriptions and serial numbers
  3. 03Finding locations and their associated items

MCP support

The server exposes itemit asset-management API operations as tools for MCP clients, including asset and location queries, asset creation, and reminder retrieval.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project 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

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:

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 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:

{
  "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..."
    }
  ]
}

Credits & Further Resources


Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.