# Mangoinventory Mango Inventory MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.mangoinventory%2Fmango-inventory
Registry id: `mcp-registry/com.mangoinventory/mango-inventory`
Status: live (checked 2026-11-22T17:00:10.403Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 953
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "mangoinventory-mango-inventory-mcp-serve": {
      "type": "http",
      "url": "https://mcp.mangoinventory.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http mangoinventory-mango-inventory-mcp-serve https://mcp.mangoinventory.com/mcp
```

## Tools (60)

- `add_comment`: Leave a comment on exactly ONE of an item, a ticket or an order: exactly one of itemId / ticketId / orderId plus the text ("note on the beamer: lamp flickers").
- `add_team_member`: Add an organization member to a team. userId is the member's userId from list_members, NOT a person-resource id from search_resources; teamId comes from list_te
- `adjust_stock`: Correct a quantity-tracked item's stock at ONE location: "we used up 12 batteries", "50 arrived", "recounted: there are 7". Exactly one of delta (relative: nega
- `archive_category`: Archive a category that nothing uses, e.g. a starter category the organization does not need. Refused, with nothing written, while anything still uses it: items
- `assign_item`: Assign or move an item: set its current location, current holder, responsible person or home location. An omitted field stays unchanged; null clears the current
- `cancel_order`: Cancel (withdraw) an order. Only the requester can cancel their OWN order, and only while it is still open; once fulfillment has started the requester cannot ca
- `check_fit`: Whether Mango Inventory fits an organization. Works without an account. Takes what is known: the kind of organization, about how many items and people, the need
- `check_item_availability`: Check whether an item is currently available: status, who holds it, where it is, how many tickets are open on it, how many of its maintenance checks are overdue
- `create_account`: Create a Mango Inventory account in the user's name. Works without an account. Needs the user's name, email address and organization name; language, organizatio
- `create_category`: Create ONE category, optionally under a parent category id (ids from get_item_requirements). scaffold_categories creates a whole tree with a dry run and reuses 
- `create_field_def`: Create ONE custom field definition for items, on a category (categoryId) or org-wide (no categoryId: applies to ALL items). Types: text, number, currency (money
- `create_invite`: Invite someone into the organization by email, with a role: owner (admin), manager, member or viewer. An invite grants access to the organization's data at that
- `create_item`: Create an inventory item. Requires the manager role. A category is required unless isDraft is true: a call without categoryId returns { missingCategory, categor
- `create_location`: Create ONE location, optionally under a parent location id (ids from search_resources). scaffold_locations creates a whole tree with a dry run and reuses existi
- `create_order`: Create an order: a request for items or material (any member can order; order managers fulfill). `lines` holds one entry per thing, each with an optional `quant
- `create_person`: Create a person record: someone items can be assigned to. This is NOT a login account; create_invite invites someone into the app, and an accepted invite links 
- `create_team`: Create an assignment team: a named group of members that tickets and orders can be assigned to ("create a facilities team"). Team members see assigned team work
- `create_ticket`: Create a defect or maintenance ticket on an item. The organization's default assignee rules apply, and the assignee is emailed straight away. setItemStatus also
- `find_docs`: Find the Mango Inventory help pages that answer a question. Works without an account. Takes the question in a few words (in any of the help languages or in Engl
- `fulfill_order`: Mark an order as fulfilled (delivered); order managers only. Fulfilling transfers reserved stock to the order's target. Three checks answer { requiresAcknowledg
- `get_item`: Get one inventory item by id: name, description, status, category and its four relations (home location, current location, current holder, responsible person) w
- `get_item_requirements`: Get what creating an inventory item needs. Without arguments: the organization's category tree plus the required fields that apply to ALL items. With categoryId
- `get_setup_status`: The organization's setup state: name, type, default language, default home location, in-app setup-step progress, whether sample data is active, and counts. Cate
- `get_setup_template`: Starting templates for setting up an organization's inventory: per kind of organization a category tree with custom field definitions, typical locations, quanti
- `inventory_overview`: The shape of the whole inventory in one call: the category tree with an item count on every node (each count covers the node's whole subtree), `statusCounts` pe
- `list_activity`: The organization's audit trail: "what changed on this item?", "what did somebody do last week?", "who moved this and when?". Newest first, one merged feed over 
- `list_comments`: Read the comments on exactly ONE of an item, a ticket or an order (the same one-target shape add_comment takes). Newest first, capped at 50 (`truncated` says th
- `list_members`: List the organization's members: userId, name, email, role (owner = admin, manager, member, viewer) and whether they are responsible for orders/tickets. The use
- `list_orders`: List orders (material and item requests) in the organization, newest first, grouped by active vs closed. Order managers see all orders; other members see only o
- `list_resources`: The organization's PLACES and PEOPLE in one call, the structural twin of inventory_overview: "what rooms do we have?", "who is in the organization?", "what is i
- `list_teams`: The organization's teams with member counts: each team's `name` and its `id`, the teamId add_team_member takes ("which teams do we have?"). Any member may read;
- `list_tickets`: List defect and maintenance tickets, newest first, capped at about 500 (`truncated` when cut; filters narrow it). Filters: itemId, statuses (open, in_progress, 
- `maintenance_status`: Maintenance status: "what maintenance is due?" (overdue / this month / next quarter). Without arguments: the organization overview with counts (overdue, dueSoon
- `my_tasks`: Everything on the connected user's plate right now ("what's on my plate?", "what should I do today?"). One merged list, exactly what the app's My-tasks page sho
- `pack_item`: Pack an item into a container: a case, cart, box or vehicle that is itself an inventory item (e.g. the voltmeter into the experiment case). While packed, the it
- `plan_import`: Dry-run an import of a whole list with the product's own importer (the same one the app's import screen uses); it writes NOTHING. Arguments: the data rows (cell
- `preview_item_create`: Preview an item creation without writing anything (read-only). It takes create_item's arguments, all optional: partial values are valid. Returns the resolved pr
- `quote`: The price of Mango Inventory. Works without an account. Takes how many items will be tracked and, optionally, the needs (the same keys as check_fit) and a curre
- `reject_order`: Reject (decline) an order; order managers only. A non-empty reason is required; the requester is notified with it. Releases any reserved stock. Fails on already
- `run_import`: Run an import: the SAME arguments as plan_import, plus its planHash and a clientRequestId (e.g. a UUID). Everything lands in ONE import batch. If anything chang
- `sample_data`: Load or clear the sample data: a small example inventory (categories, places, people, items and a few tickets, all marked as samples) for a new organization to 
- `scaffold_categories`: Create a whole category tree with custom field definitions in one call. Without confirm: true it is a dry run that writes NOTHING and returns the plan: per node
- `scaffold_locations`: Create a whole location tree (buildings, floors, rooms, storage places) in one call, with the same contract as scaffold_categories: without confirm: true it is 
- `scaffold_models`: Create item models («Modelle») in one call: one model per article type whose pieces share a name and settings, e.g. «Arbeitshose» in sizes XS to 8XL, or 16 iden
- `search_items`: Search inventory items. `search` matches exact item codes and barcode labels first (e.g. "BM-002" printed on an asset tag), then names: word-prefix ("Lap" match
- `search_resources`: Find the resource id of ONE person or ONE location by name. `type` is required ("person" or "location"); returns the 10 best matches; name search only (no code 
- `send_feedback`: Send a report about these tools to the Mango Inventory team, who read the stored reports to fix the tools: a tool that failed unexpectedly, an answer or error t
- `set_item_status`: Set an item's operational status (condition): available, in_repair, defect, lost or retired, e.g. defect or lost, or available again after a repair. The change 
- `set_min_stock`: Set or clear the restock threshold (minimum stock) for a quantity-tracked item at ONE location: "alert us when Room 201 drops below 5". Thresholds are per item 
- `set_org_defaults`: Set organization-wide defaults, any combination in one call: defaultHomeLocationId (where new items live by default; a location resource id), defaultResponsible
- `set_org_type`: Set the organization's type: school, company, publicAdmin, publicWorks, club or other. It tailors the in-app experience. Idempotent. Only the organization's cre
- `show_items`: Show a set of inventory items as a visual picker: a photo list in which each row carries the item's name, the code printed on its asset tag, its condition and w
- `stocktaking_status`: Stocktaking overview: without sessionId, all stocktaking sessions with live progress; with sessionId, the per-location and per-counter breakdown of that session
- `tell_us`: Pass a message to the Mango Inventory team: what a visitor came for, or what is missing. Works without an account; signed-in connections have send_feedback. Tak
- `transfer_stock`: Move an amount of a quantity-tracked item's stock from one place or person to another (e.g. 3 packs of printer paper from the storeroom to room 201, or 5 marker
- `unpack_item`: Take an item out of its container. Its current location and holder are set from the container's effective position at that moment (a snapshot: it stops followin
- `update_category`: Update a category (ids from get_item_requirements), any combination in one call: rename it; holdsItems, the container switch for its items (true = its items can
- `update_field_def`: Update a custom field definition: rename the label, flip required, replace a select's options, or change a currency field's currencyCode. The TYPE is immutable,
- `update_item`: Update an inventory item: rename it, edit the description (null clears it), and set custom field values (keys = fieldDefId from get_item_requirements; null clea
- `update_ticket`: Update a ticket: change its status (open, in_progress, done, wontfix) and/or edit title, description, priority or due date. Closing = status done (resolved) or 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
