get-location-by-nameLABSCO SUMMARY
Location lookup that answers with the contents.
Asking where something is only half-solves an inventory problem; the other half is what else is there. get-location-by-name returns the location together with the items on it, which is the query you actually run when you are standing in a store cupboard. Creating items from chat is the natural counterpart — new equipment gets recorded while you are holding it rather than later.
What it is
A bridge to itemit, an asset-management platform for tracking physical things: equipment, tools, stock. It searches items by name, lists what you have, creates new records, and finds a location along with the items sitting in it — so an inventory question can be asked rather than clicked through.
What you get
get-itemslists the items in your workspacesearch-item-by-namefinds an item by namecreate-itemadds a new asset recordget-location-by-namefinds a location and the items on it, withlimitdefaulting to 25 and capped at 100, andskipfor pagingget-remindersreturns the reminders set against your assets
Requirements
An itemit account and four credentials from it: ITEMIT_API_KEY, ITEMIT_USER_ID, ITEMIT_USER_TOKEN and ITEMIT_WORKSPACE_ID. Node.js v16+ recommended; clone the repository, npm install, npm run build, then point your client at build/index.js over stdio with those four in the env block (package itemit-mcp, version 1.0.0).
Setup effort
Build from source — git clone https://github.com/umin-ai/itemit-mcp.git
USE CASES
Finding where a specific piece of equipment is
Search by name and read back the record.
Seeing what is in a room or a store
Look the location up by name and get the items on it, paged.
Recording new stock as it arrives
Create the asset record without opening the app.
Checking what is due for attention
Read the reminders set against your assets.
5 tools
Listed in project docs. Your client may show a different list.
search-item-by-namecreate-itemget-remindersget-itemsBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
- Node.js
- ITEMIT_API_KEY in your environment
- ITEMIT_USER_ID in your environment
- ITEMIT_USER_TOKEN in your environment
- ITEMIT_WORKSPACE_ID in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
git clone https://github.com/umin-ai/itemit-mcp.git
cd itemit-mcp
npm install
npm run buildMCP Clients
Cline
{
"mcpServers": {
"itemit-mcp": {
"disabled": false,
"timeout": 60,
"type": "stdio",
"command": "node",
"args": [
"/Users/<YOUR_USERNAME>/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>"
}
}
}
}