MarketPrint MCP¶

Merchandising has two halves and the AI assistant only ever touches one of them. Design an image and the chat can help. Turn that image into a shippable product with a price, a stock rule and a live listing, and the conversation stops.

MarketPrint publishes a remote MCP endpoint at https://mcp.marketprint.de/mcp over Streamable HTTP with OAuth. A keyless tools/list answers HTTP 401 with a refusal that names both supported credential paths in one sentence:

{"error":"unauthorized",
 "error_description":"Missing bearer token. Connect via OAuth, or use a static mcpacct_ token from your account settings."}

That is a better 401 than most. It tells the agent what to do next instead of reporting a bare failure, and it confirms the OAuth flow and a static account token are both first-class.

Server type: Remote (Streamable HTTP)
Endpoint:    https://mcp.marketprint.de/mcp
Auth:        OAuth, or a static mcpacct_ token
Vendor:      MarketConsultive GmbH
Production:  Germany for Europe, Houston, Texas for the USA
Channels:    Shopify, Etsy, WooCommerce, TikTok Shop
Licence:     closed (no public repository)
Docs:        help.marketprint.de

What it does¶

The connector covers the gap between a finished design and a product on a shelf nobody has to pack. MarketPrint prints and ships the things you sell in your own store, and the MCP surface is the layer that lets an assistant do everything in between: take a saved design, apply it to a product, set the commercial terms and publish the listing to the storefront.

The configuration is one entry, which is the right shape for a hosted service:

{
  "mcpServers": {
    "marketprint-print-on-demand": {
      "type": "http",
      "url": "https://mcp.marketprint.de/mcp"
    }
  }
}

The split production model is the operational detail¶

Two production sites, chosen by destination rather than by the seller: Germany for European orders and Houston for American ones. For a print-on-demand business that is not a footnote, it is the difference between a shipping estimate that survives a customs form and one that does not. A European buyer receiving a US-produced mug pays duty, waits longer and sometimes refuses delivery.

An assistant that publishes to four channels should therefore carry the destination as a real field in the conversation, not infer it. The catalogue has no other print-on-demand entry, so this is also the first place a multi-channel POD question can be answered at all.

Four storefronts, one connector¶

Etsy, Shopify, WooCommerce and TikTok Shop are four different commercial models wearing the same word "listing". Etsy is marketplace discovery with its own fee stack; Shopify is your own store with your own checkout; WooCommerce is the self-hosted counterpart; TikTok Shop is a live-commerce surface with its own creator rules. A connector that publishes to all four is useful precisely because the operator does not have to hold four mental models of how a product goes live.

The correct expectation to test is that product attributes translate rather than flatten. A variant set that works on Etsy should not arrive on Shopify as a single SKU with a note.

Why it belongs in this catalogue¶

The catalogue carries the storefront side heavily: speed checks, store health checks, e-commerce operations for agents. What it did not carry is the supply side, where a physical object begins to exist. That is a new slice rather than a fifth opinion on storefront health.

The nearest neighbours are operational tools that read a store. This one writes inventory into existence and publishes it across channels, which means the failure mode is worse: a bad read costs a wrong answer, a bad publish costs a live listing with a wrong price attached to a product that will actually be manufactured.

What this pass did not establish¶

The credential is real, the endpoint is real, and the tool names are not in this entry because tools/list needs a token. Three things a buyer should confirm in a trial: whether a listing can be created as a draft rather than published live, whether price and margin can be set per channel, and whether existing listings can be read back for reconciliation. Until those are driven, treat the publish path as capable but unverified.

FAQ¶

Does it need an account with MarketPrint?¶

Yes. The connector is the front end of a MarketPrint account, which is what the OAuth consent and the static mcpacct_ token both authorise.

Which storefronts can it publish to?¶

Shopify, Etsy, WooCommerce and TikTok Shop, per the vendor listing.

Where are the products made?¶

Germany for European orders, Houston, Texas for orders in the United States.

Is there a public repository?¶

No. The service is closed and the card carries no repository link, so this entry rests on the live endpoint probe and the vendor documentation rather than on source.

Integration with CorpusIQ¶

CorpusIQ is the connector layer that lets AI assistants read the systems a business already runs on - accounting, payments, CRM, email, files and analytics - and answer with the source named. It is read-only by design: it retrieves data and never writes to, or acts in, a connected system, which is what makes it safe to point at live accounts.

This page is part of the CorpusIQ directory, the reference we maintain for the MCP server and agent-skill ecosystem. Run alongside CorpusIQ, a third-party server like this one can be combined with a company's own business data in a single answer.

See what CorpusIQ connects