← Back to all MCPs

Unleashed MCP

An Unleashed MCP connector for stock, products, sales orders and purchasing. Explore the coverage and join the access waitlist.

Inventory and orders

What is Unleashed MCP?

MCP XYZ is building an independent Unleashed MCP connector so an AI assistant can work with authorised inventory and order records through the Model Context Protocol. The connector covers documented Unleashed API operations; new access is by invitation from the waitlist, and live business workflows still need validation.

Use the catalogue to check the operations and fields your work needs. If an existing connector is missing a useful action, tell us about it when joining the waitlist. Your software’s permissions and API limits still apply.

Unleashed workflows to explore

Check stock and warehouse records

Explore documented product, stock-on-hand and warehouse operations for questions about inventory across your business.

Inspect documented operations

Find sales orders and line items

Inspect sales-order and customer operations, including the products, quantities and prices retained in their documented fields.

Inspect documented operations

Work with purchasing and supplier records

Review the purchase-order, receipt and supplier coverage before planning an authorised purchasing workflow.

Inspect documented operations
Example request to try after setup and validation

“Show stock on hand by warehouse for this product.”

Getting access to Unleashed MCP

New access starts with the Unleashed waitlist. Tell us which assistant you use and the work you want to do. We’ll contact you about relevant access updates; joining does not create an account or guarantee an invitation date.

Once invited, sign in to MCP XYZ, choose your workspace and add the API ID and key for your authorised Unleashed account. Run the connection check, then add its MCP URL to your assistant. Saved credentials alone do not verify a connection.

Unleashed API documentation

Start with read-only access while you explore. Jiffi can handle setup with you. Live business workflows still need validation against an authorised account.

In Claude Desktop or web, open Settings → Connectors → Add custom connector, enter your connection’s MCP URL, then connect and choose access in MCP XYZ.

Unleashed MCP questions

What is the Unleashed MCP from MCP XYZ?
It is an independent connector being built by Jiffi to expose documented Unleashed API operations through the Model Context Protocol. It is intended to let an authorised AI assistant request inventory, customer, supplier and order information from your Unleashed account.
Can I use Unleashed MCP with Claude or ChatGPT?
MCP XYZ connection and tool-discovery flows have been tested with Claude Desktop and web, Codex and Claude Code. Those checks did not verify live Unleashed business requests. ChatGPT acceptance has not yet been verified. Tell us which assistant you use when joining the waitlist.
What Unleashed access will I need?
After an access invitation, setup requires an authorised Unleashed account with API access, its API ID and API key, and an MCP XYZ workspace. Your account permissions and the provider’s API limits still apply. Never put API keys into the waitlist form.
Can this connector update orders or inventory?
The documented catalogue includes reads and writes. A documented write does not establish a tested business workflow. Changes require the relevant permissions and validation in an authorised scope; ambiguous mutating requests are not automatically retried.
How do I get access, and what does it cost?
Join the Unleashed waitlist and describe the job you want to do. We will contact you about access; joining does not create an account or guarantee a launch date. MCP access is included for clients under contract with Jiffi. Standalone access and any applicable terms are discussed before activation.

Read the AI client guide How access and permissions work

Documented coverage

Operations and fields

145 documented operation variants. Open a contract to inspect its parameters, fields, sources and unresolved behaviour. No provider request is made here.

145 operations match. Showing 121–140.

Documented contract, live behaviour unverified

List all purchase order statuses

unleashed_list_purchase_order_statuses

GET/PurchaseOrderStatuses

Read the provider documentation

Unresolved behaviour

  • No authenticated sandbox or production request has verified this operation.

Query parameters and filters

ParameterRequiredProvider description
includeObsoleteNoSet to true to also return obsolete custom statuses. Obsolete custom statuses are excluded by default.
modifiedSinceNoOnly return custom statuses created or edited after a specified date, must be UTC format. The fixed statuses have no modification date, so they are not returned when this filter is used.
pageSizeNoNumber of records per page.

Retained Purchase Order Statuses field and filter tables

These source tables cover the resource’s documented methods. Read each table’s heading for its request or response context.

Available Fields for GET Purchase Order Statuses

GET Purchase Order Statuses

PropertyTypeLengthNotes
NameString15The status name.
IsCustomStatusBooleanfalse for the fixed statuses, true for custom statuses configured in your account.
ObsoleteBooleanAlways false for fixed statuses.
LastModifiedOnNullable DateTimeOnly returned for custom statuses.
Available Filters for GET Purchase Order Statuses

GET Purchase Order Statuses

FilterDescription
includeObsoleteSet to true to also return obsolete custom statuses. Obsolete custom statuses are excluded by default.
modifiedSinceOnly return custom statuses created or edited after a specified date, must be UTC format. The fixed statuses have no modification date, so they are not returned when this filter is used.
Inspect the complete operation contract

The exact retained JSON includes schemas, nested fields, notes, source evidence and unresolved questions. It is a documented contract, not a live response.

{
  "id": "list_purchase_order_statuses",
  "name": "unleashed_list_purchase_order_statuses",
  "resourceId": "PurchaseOrderStatuses",
  "description": "List all purchase order statuses",
  "method": "GET",
  "path": "/PurchaseOrderStatuses",
  "documentationUrl": "https://apidocs.unleashedsoftware.com/PurchaseOrderStatuses",
  "readOnly": true,
  "destructive": false,
  "idempotent": true,
  "pathParameters": [],
  "queryParameters": [
    {
      "name": "includeObsolete",
      "required": false,
      "description": "Set to true to also return obsolete custom statuses. Obsolete custom statuses are excluded by default.",
      "schema": {
        "type": [
          "string",
          "number",
          "boolean"
        ],
        "description": "Set to true to also return obsolete custom statuses. Obsolete custom statuses are excluded by default."
      },
      "sourceSection": "Available Filters for GET Purchase Order Statuses"
    },
    {
      "name": "modifiedSince",
      "required": false,
      "description": "Only return custom statuses created or edited after a specified date, must be UTC format. The fixed statuses have no modification date, so they are not returned when this filter is used.",
      "schema": {
        "type": [
          "string",
          "number",
          "boolean"
        ],
        "description": "Only return custom statuses created or edited after a specified date, must be UTC format. The fixed statuses have no modification date, so they are not returned when this filter is used."
      },
      "sourceSection": "Available Filters for GET Purchase Order Statuses"
    },
    {
      "name": "pageSize",
      "required": false,
      "description": "Number of records per page.",
      "schema": {
        "type": "integer",
        "minimum": 1,
        "maximum": 1000
      },
      "sourceSection": "Global Pagination reference"
    }
  ],
  "requestBodySchema": null,
  "responseSchema": null,
  "pagination": {
    "strategy": "path-page",
    "pathTemplate": "/PurchaseOrderStatuses/{page}",
    "pageParameter": "page",
    "pageSizeParameter": "pageSize",
    "firstPage": 1,
    "defaultPageSize": 200,
    "maximumPageSize": 1000,
    "minimumPageSize": 1,
    "responseItemsPath": "Items",
    "responsePaginationPath": "Pagination",
    "documentationUrl": "https://apidocs.unleashedsoftware.com/Pagination",
    "notes": [
      "Prefer Pagination.NumberOfPages when supplied. Older responses without metadata require stopping on a short page."
    ]
  },
  "notes": [],
  "provenance": [
    {
      "sourceUrl": "https://apidocs.unleashedsoftware.com/PurchaseOrderStatuses",
      "sourceSha256": "0db2d8911bb74500039b6cace2b2239d88f7004bb714747bcf50c0173975d457",
      "section": "The full range of URIs and HTTP Verbs supported are",
      "evidence": "GET /PurchaseOrderStatuses",
      "operationDescriptions": [
        "List all purchase order statuses"
      ]
    }
  ],
  "confidence": "documented-route",
  "unresolved": [
    "No authenticated sandbox or production request has verified this operation."
  ],
  "requestFieldTable": null,
  "responseFieldTable": "Available Fields for GET Purchase Order Statuses"
}
Inspect the complete resource record
{
  "id": "PurchaseOrderStatuses",
  "name": "Purchase Order Statuses",
  "group": "Read only data",
  "documentationUrl": "https://apidocs.unleashedsoftware.com/PurchaseOrderStatuses",
  "snapshot": "snapshots/PurchaseOrderStatuses.html",
  "sourceSha256": "0db2d8911bb74500039b6cace2b2239d88f7004bb714747bcf50c0173975d457",
  "fetchedAt": "2026-10-23T14:00:32.801658+00:00",
  "operationIds": [
    "list_purchase_order_statuses"
  ],
  "fieldTables": [
    {
      "heading": "GET Purchase Order Statuses",
      "anchor": "get-purchase-order-statuses",
      "summary": "Available Fields for GET Purchase Order Statuses",
      "rows": [
        [
          "Property",
          "Type",
          "Length",
          "Notes"
        ],
        [
          "Name",
          "String",
          "15",
          "The status name."
        ],
        [
          "IsCustomStatus",
          "Boolean",
          "",
          "false for the fixed statuses, true for custom statuses configured in your account."
        ],
        [
          "Obsolete",
          "Boolean",
          "",
          "Always false for fixed statuses."
        ],
        [
          "LastModifiedOn",
          "Nullable DateTime",
          "",
          "Only returned for custom statuses."
        ]
      ]
    }
  ],
  "filterTables": [
    {
      "heading": "GET Purchase Order Statuses",
      "anchor": "get-purchase-order-statuses",
      "summary": "Available Filters for GET Purchase Order Statuses",
      "rows": [
        [
          "Filter",
          "Description"
        ],
        [
          "includeObsolete",
          "Set to true to also return obsolete custom statuses. Obsolete custom statuses are excluded by default."
        ],
        [
          "modifiedSince",
          "Only return custom statuses created or edited after a specified date, must be UTC format. The fixed statuses have no modification date, so they are not returned when this filter is used."
        ]
      ]
    }
  ],
  "documentationNotes": [
    "The Purchase Order Statuses resource allows you to view the purchase order statuses available to your account. The response contains the fixed statuses that Unleashed provides, followed by the custom purchase order statuses that your account has configured.",
    "An account can configure a maximum of 10 custom purchase order statuses.",
    "Note: Date filters should be provided in the ISO format YYYY-MM-DD. The time zone is UTC."
  ]
}

What has been verified

Documented coverage
145 operation variants retained from official provider documentation, with 43 resource records and their field and filter tables. These counts describe documentation, not proven live workflows.
Agent connection
Actual Claude Desktop and web connection, model-selected platform utility calls, renewal after natural token expiry and revoked-access rejection passed. Codex and Claude Code authentication and discovery were also checked. These tests made no provider business requests.
Live business workflows
Awaiting an authorised Unleashed account. Provider reads, writes and business workflows are not yet verified.
More software, the same workspace

Explore Procore MCP

Inspect the Procore catalogue and the approval and account requirements while live acceptance is still pending.

Explore Procore