MerchandAise agent platform

Bring product creation into the conversation.

Use the Model Context Protocol (MCP) to connect an AI assistant to supported MerchandAise tools. Help people explore products, refine a design and prepare a quote request while keeping decisions and approvals with the user.

Review an agent workflow Explore API contracts

Understand what the assistant can do

In supported sessions, a user can describe an idea, see the product in interactive 3D and ask for changes. The assistant uses the same product information and design state as the MerchandAise workflow; current tools determine what it can read or change.

The server card and external tool metadata are public for discovery. Each tool call still follows its declared security and workspace boundary, while buyer, proof, and production approvals stay visible and attributable.

01 — Contracts

Discover the server. Then request the right access.

AI agents & MCP

Connect an AI assistant through the Model Context Protocol. Discover supported tools and preserve the user’s design choices, permissions and required confirmations.

Access: Public

Implementation guide

Read MCP implementation guide

Machine contract

Public MCP server-card JSON

/.well-known/mcp/server-card

Public discovery document for machine clients. The external tools list at /api/v1/mcp/tools exposes current tool metadata; each tool call still follows its declared security, workspace, and confirmation boundaries.

API docs & OpenAPI

Find the API reference for assistant tooling and design sessions, then choose the community, supplier or enterprise contract for your workflow.

Access: Public

Implementation guide

Explore API docs

Machine contract

Assistant tooling OpenAPI JSON

/api/docs/openapi.json

Public reference for assistant and tooling APIs. Production access and order-affecting operations still require the applicable authorization.

02 — Implementation guide

From server discovery to your first workflow

01
Discover safely
Use the public MCP server card and tools list to identify MerchandAise and the current external tool inventory. Discovery alone grants no broad authority to quote, change state, or order.
02
Grant the least privilege
Authorize only the tools, workspace, and environment the assistant needs. Separate read-only exploration from actions that change a design, quote, approval, or order state.
03
Confirm before consequence
Keep explicit human confirmation for sensitive actions, test stale-state and refusal behavior, and prove recovery paths before production traffic is enabled.

What the agent must preserve

One versioned product state

The assistant works against the same design, commerce intent, supplier-backed quote, approval, and order state as every other MerchandAise surface.

Commercial and supplier privacy

Where MerchandAise processes the buyer transaction, Hutter Products GmbH is the contracting seller and Merchant of Record under the MerchandAise brand. Private supplier identity, contacts, and internal data are not exposed to an agent.

Proof gates stay human

A 3D view is not physical evidence. The confirmed quote explains any available customer-sample choices, costs, limitations, and timing. Approve the exact digital proof and complete mandatory technical checks and any required or selected sample approval before mass production. Existing accepted-order requirements remain binding.

Before an agent reaches production

A discoverable MCP server is only the beginning. Production readiness means the assistant has a bounded role, every consequential action has an owner, and failures return users to a safe state.

Map access by consequence

Classify every tool as read-only, advisory, state-changing, supplier-sensitive, or order-affecting before granting it to an assistant.

Name every confirmation owner

Define who confirms product changes, quotes, digital proofs, production samples, and orders—and what the assistant does when that person is unavailable.

Observe, refuse, and recover

Test invalid inputs, stale state, missing permissions, refusals, retries, telemetry, and rollback paths before live traffic reaches the workflow.

FAQ

What is MCP, and is this a public ChatGPT app?

MCP stands for Model Context Protocol: a way for an assistant to discover and use tools. These documents describe MerchandAise integration capabilities. A public server card does not confirm ChatGPT app-store availability. ChatGPT workspace access depends on your account, app setup and the supported environment.

What can an AI agent do with MerchandAise?

An authorized assistant can use the tools approved for its workspace and environment, such as product discovery, design or quote guidance, and other explicitly enabled operations. The available tools and their permissions are determined during integration review.

Can an AI agent place orders automatically?

Not by discovering the server or listing tools. Any order-affecting workflow must preserve authentication, buyer and workspace confirmation, version-current pricing, digital-proof approval, and supplier-confirmed producibility, mandatory technical checks, and the exact customer-sample choice and approval requirements agreed for the order. Existing accepted-order requirements cannot be silently waived.

Is the MerchandAise MCP integration public?

The MCP server card and current external tool metadata are public for machine discovery. Individual tool calls follow their declared security model, and protected workspace, supplier, enterprise, quote, and order operations retain their required authorization and confirmations.

Have an agent workflow in mind?

Tell us who the assistant serves, what it should be allowed to do, and where a person needs to stay in control. We will map the right MCP, API, and approval boundary.