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.

Join the Unleashed waitlist Existing user? Log in →

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

Create a new Bill of Materials

/BillOfMaterials/{billOfMaterialsGuid}Inspect fields and contract →

Documented contract, live behaviour unverified

View an Attribute Set with the specified Guid

unleashed_get_attribute_sets

GET/AttributeSets/{attributeSetGuid}

Read the provider documentation ↗

Unresolved behaviour

No authenticated sandbox or production request has verified this operation.

Path parameters

Parameter	Required	Provider description
`attributeSetGuid`	Yes	Provider identifier from the corresponding resource; preserve the documented identifier type.

Retained Attribute Sets 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 Attribute Sets

GET Attribute Sets

Property	Type	Length	Notes
Attributes	Attribute Collection
CreatedBy	Nullable String
CreatedOn	Nullable DateTime
Guid	Guid		Unique identifier. Can only be set when adding a record.
LastModifiedBy	Nullable String	50
LastModifiedOn	Nullable DateTime
SetName	String	50
Type	String		The Type value must be Product .

Available Fields for Attribute

GET Attribute Sets

Property	Type	Length	Notes
Guid	Guid		Unique identifier. Can only be set when adding a record.
IsRequired	Boolean	true , false
Name	String	50
Value	String	50	The default value assigned to the attribute.

Available Fields for POST Attribute Sets

POST AttributeSets

Property	Type	Length	Required	Notes
Attributes	Attribute Collection
Guid	Guid		Yes for updating N/A for creating	Unique identifier. Can only be set when adding a record.
SetName	String	50	Yes
Type	String		Yes	The Type value must be Product .

Available Fields for Attribute

POST AttributeSets

Property	Type	Length	Required	Notes
Guid	Guid		Yes for updating N/A for creating	Unique identifier. Can only be set when adding a record.
IsRequired	Boolean	true , false
Name	String	50	Yes	Must be unique.
Value	String	50		The default value assigned to the attribute.

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": "get_attribute_sets",
  "name": "unleashed_get_attribute_sets",
  "resourceId": "AttributeSets",
  "description": "View an Attribute Set with the specified Guid",
  "method": "GET",
  "path": "/AttributeSets/{attributeSetGuid}",
  "documentationUrl": "https://apidocs.unleashedsoftware.com/AttributeSets",
  "readOnly": true,
  "destructive": false,
  "idempotent": true,
  "pathParameters": [
    {
      "name": "attributeSetGuid",
      "required": true,
      "schema": {
        "type": "string",
        "minLength": 1
      },
      "description": "Provider identifier from the corresponding resource; preserve the documented identifier type."
    }
  ],
  "queryParameters": [],
  "requestBodySchema": null,
  "responseSchema": null,
  "pagination": null,
  "notes": [],
  "provenance": [
    {
      "sourceUrl": "https://apidocs.unleashedsoftware.com/AttributeSets",
      "sourceSha256": "2d059230823e259470e188b6c5dd12c29f22a20d43f88b7ee926fd8e29e2550a",
      "section": "The full range of URIs and HTTP Verbs supported are",
      "evidence": "GET /AttributeSets/{attributeSetGuid}",
      "operationDescriptions": [
        "View an Attribute Set with the specified Guid"
      ]
    }
  ],
  "confidence": "documented-route",
  "unresolved": [
    "No authenticated sandbox or production request has verified this operation."
  ],
  "requestFieldTable": null,
  "responseFieldTable": "Available Fields for GET Attribute Sets"
}

Inspect the complete resource record

{
  "id": "AttributeSets",
  "name": "Attribute Sets",
  "group": "Editable resources",
  "documentationUrl": "https://apidocs.unleashedsoftware.com/AttributeSets",
  "snapshot": "snapshots/AttributeSets.html",
  "sourceSha256": "2d059230823e259470e188b6c5dd12c29f22a20d43f88b7ee926fd8e29e2550a",
  "fetchedAt": "2026-10-23T14:00:30.558458+00:00",
  "operationIds": [
    "list_attribute_sets",
    "get_attribute_sets",
    "create_attribute_sets",
    "create_attribute_sets_with_guid"
  ],
  "fieldTables": [
    {
      "heading": "GET Attribute Sets",
      "anchor": "get-attribute-sets",
      "summary": "Available Fields for GET Attribute Sets",
      "rows": [
        [
          "Property",
          "Type",
          "Length",
          "Notes"
        ],
        [
          "Attributes",
          "Attribute Collection",
          "",
          ""
        ],
        [
          "CreatedBy",
          "Nullable String",
          "",
          ""
        ],
        [
          "CreatedOn",
          "Nullable DateTime",
          "",
          ""
        ],
        [
          "Guid",
          "Guid",
          "",
          "Unique identifier. Can only be set when adding a record."
        ],
        [
          "LastModifiedBy",
          "Nullable String",
          "50",
          ""
        ],
        [
          "LastModifiedOn",
          "Nullable DateTime",
          "",
          ""
        ],
        [
          "SetName",
          "String",
          "50",
          ""
        ],
        [
          "Type",
          "String",
          "",
          "The Type value must be Product ."
        ]
      ]
    },
    {
      "heading": "GET Attribute Sets",
      "anchor": "get-attribute-sets",
      "summary": "Available Fields for Attribute",
      "rows": [
        [
          "Property",
          "Type",
          "Length",
          "Notes"
        ],
        [
          "Guid",
          "Guid",
          "",
          "Unique identifier. Can only be set when adding a record."
        ],
        [
          "IsRequired",
          "Boolean",
          "true , false",
          ""
        ],
        [
          "Name",
          "String",
          "50",
          ""
        ],
        [
          "Value",
          "String",
          "50",
          "The default value assigned to the attribute."
        ]
      ]
    },
    {
      "heading": "POST AttributeSets",
      "anchor": "post-attributesets",
      "summary": "Available Fields for POST Attribute Sets",
      "rows": [
        [
          "Property",
          "Type",
          "Length",
          "Required",
          "Notes"
        ],
        [
          "Attributes",
          "Attribute Collection",
          "",
          "",
          ""
        ],
        [
          "Guid",
          "Guid",
          "",
          "Yes for updating N/A for creating",
          "Unique identifier. Can only be set when adding a record."
        ],
        [
          "SetName",
          "String",
          "50",
          "Yes",
          ""
        ],
        [
          "Type",
          "String",
          "",
          "Yes",
          "The Type value must be Product ."
        ]
      ]
    },
    {
      "heading": "POST AttributeSets",
      "anchor": "post-attributesets",
      "summary": "Available Fields for Attribute",
      "rows": [
        [
          "Property",
          "Type",
          "Length",
          "Required",
          "Notes"
        ],
        [
          "Guid",
          "Guid",
          "",
          "Yes for updating N/A for creating",
          "Unique identifier. Can only be set when adding a record."
        ],
        [
          "IsRequired",
          "Boolean",
          "true , false",
          "",
          ""
        ],
        [
          "Name",
          "String",
          "50",
          "Yes",
          "Must be unique."
        ],
        [
          "Value",
          "String",
          "50",
          "",
          "The default value assigned to the attribute."
        ]
      ]
    }
  ],
  "filterTables": [],
  "documentationNotes": [
    "The AttributeSets resource allows attributes to be listed, created, and updated. An individual attribute set details can be viewed or updated by appending its identifier (a GUID formatted as XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX ) to the URI.",
    "Note: This endpoint can only be used for Products."
  ]
}

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 →