itemit MCP for asset tracking
If you already use Itemit MCP, the itemit mcp mcp server is the piece that lets your assistant work with it directly. itemit MCP for asset tracking.
Built and maintained by the uminai MCP team.
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)
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
ITEMIT_API_KEY — ITEMIT_USER_IDITEMIT_USER_TOKEN — ITEMIT_WORKSPACE_IDBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: ITEMIT_API_KEY, ITEMIT_USER_ID, ITEMIT_USER_TOKEN, ITEMIT_WORKSPACE_ID, YOUR_API_KEY, YOUR_USER_ID, YOUR_USER_TOKEN, YOUR_WORKSPACE_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Itemit MCP's toolset — ITEMIT_API_KEY, ITEMIT_USER_TOKEN — is a fair guide to whether it matches your workflow. It is maintained by umin-ai; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| ITEMIT_API_KEY | ITEMIT_USER_ID |
| ITEMIT_USER_TOKEN | ITEMIT_WORKSPACE_ID |
{
"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>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| ITEMIT_API_KEY | Credential the server authenticates with. | Yes |
| ITEMIT_USER_ID | Configuration value read at startup. | Optional |
| ITEMIT_USER_TOKEN | Credential the server authenticates with. | Yes |
| ITEMIT_WORKSPACE_ID | Configuration value read at startup. | Optional |
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_USER_ID | Configuration value read at startup. | Optional |
| YOUR_USER_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_WORKSPACE_ID | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.