Itemit

Bridges the itemit asset management API with MCP, enabling item search, creation, and location management via MCP tools.

javascript

GitHub Stars

javascript

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": {
    "umin-ai-itemit-mcp": {
      "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>"
      }
    }
  }
}

You connect itemit’s asset management capabilities to the MCP ecosystem, giving you a programmable bridge to search, create, and manage assets and locations across MCP-enabled systems. This server makes it easier to integrate itemit with other tools and workflows that speak MCP, so you can automate asset tracking end-to-end.

How to use

You run the MCP client and load the itemit-mcp server as a local service. The server exposes a set of tools you can invoke through the MCP client to look up locations, search items by name, and create new items. Use the client to chain operations, for example locating a warehouse, finding a specific item by name, or creating a new asset with a serial number.

Key capabilities include getting a list of locations by name, searching for items by name, creating items with a name, description, and serial, and retrieving reminders or item lists as needed. You can combine these tools to automate inventory workflows across your MCP-enabled infrastructure.

How to install

Prerequisites: Node.js v16 or newer and an itemit account with API credentials. Ensure you have the MCP Client available in your environment.

Install dependencies for the project
Build the project
Run the server locally via the MCP client configuration

Configuration and operation notes

Environment variables you supply to the server are required for authentication with itemit. You will provide these values to the MCP client and to the server process to authorize API calls.

The MCP client can start the local server process using a stdio configuration that runs node and points to the built entry script, with credentials supplied as environment variables.

For a direct view of the configuration, you can use the example snippet shown below to set up the MCP client configuration.

Environment variables

The following environment variables are required to connect to the itemit API from the MCP server.

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

Example usage

Use your MCP client to invoke tools such as search-item-by-name or get-location-by-name with appropriate arguments to perform asset management tasks.

Response format

Responses are returned as structured text or JSON that mirrors the itemit API data model. Successful calls include details about items, locations, or reminders as applicable.

Credits & further resources

This MCP server is built to bridge itemit with the MCP ecosystem, enabling automated asset tracking and location management across systems.

Available tools

get-location-by-name

Retrieve locations from itemit by their name with optional limit and skip to paginate results.

search-item-by-name

Search for items in itemit by name with size and page controls for pagination.

create-item

Create a new item in itemit with a name, description, and serial number.

get-reminders

Fetch reminders from itemit for proactive asset management.

get-items

Retrieve a list of items from itemit with an optional size parameter.

Built by

VeilStrat

AI signals for GTM teams