InkFE MCP connector

The connector is available to approved assistants and integrators. To request an API key, email orders@inkfe.com with the name of your product and how it will use the connector. Keys can be rotated or revoked on request.

Add the server to any MCP client that supports Streamable HTTP:

{
  "mcpServers": {
    "inkfe": {
      "type": "http",
      "url": "https://www.inkfe.com/api/mcp",
      "headers": { "Authorization": "Bearer <api key>" }
    }
  }
}

Or, from the Claude Code CLI:

claude mcp add --transport http inkfe https://www.inkfe.com/api/mcp --header "Authorization: Bearer <api key>"

• URL: https://www.inkfe.com/api/mcp
• Protocol: MCP over Streamable HTTP (stateless)
• Server name: inkfe-print, version 0.1.0

Send each JSON-RPC 2.0 request as a POST with Content-Type: application/json and Accept: application/json, text/event-stream. Responses are delivered as a single server-sent message event containing the JSON-RPC response. No session id is required.

POST https://www.inkfe.com/api/mcp
Authorization: Bearer <api key>
Content-Type: application/json
Accept: application/json, text/event-stream

{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"your-client","version":"1.0"}}}

Tool names and required arguments are stable within a major version. Optional fields and new tools may be added at any time; breaking changes are released under a new version number and announced to key holders in advance.

Every request must include your API key in the Authorization header:

Authorization: Bearer <api key>

Requests without a valid key receive 401 Unauthorized. Treat the key like a password: store it in your client's secret configuration, never in prompts, logs or client-side code, and contact support to rotate it if it may have been exposed.

1. Discover. Call list_business_card_templates. Show the buyer the preview images and the fields each template needs; use search_products and get_product for any other print product.
2. Collect. Help the buyer pick a template and gather a value for every required field. Logo fields take a public https PNG or JPEG URL; QR fields take the https URL the code should open.
3. Design. create_business_card_design applies the values (and logo) to the template, fits the text, renders front and back previews, and returns a design token. Show the buyer both previews before moving on.
4. Checkout. Once the buyer approves the previews and chooses a value for every option get_product lists (for example Corners and Quantity), create_checkout attaches the print-ready artwork to a Shopify cart and returns the checkout URL. Shipping and payment are collected on that page.

Every tool returns JSON in a single text content block. Arguments are validated against the schema advertised by tools/list; invalid arguments return an isError result describing the problem.

{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"list_business_card_templates","arguments":{}}}

HTTP/1.1 200 OK
Content-Type: text/event-stream

event: message
data: {"jsonrpc":"2.0","id":2,"result":{"content":[{"type":"text","text":"{ \"templates\": [ ... ] }"}]}}

{ products: [{ handle, title, productType, priceRange: { min, max, currency }, options: [{ name, values }], url }] }

{ handle, title, productType, hasBack, dimensions: { widthInches, heightInches } | null, options: [{ name, role, values }], variants: [{ variantId, title, selectedOptions, packPrice, currency, availableForSale }], url }

{ templates: [{ templateId, name, orientation, widthInches, heightInches, previewUrls: { front, back }, hasBack, fields: [{ attribute, label, side, inputType, required, sampleValue, maxLines? }], productHandle }] }

{ designToken, designId, templateId, revisionId, expiresAt, previews: [{ side, url, expiresInSeconds: 300, width, height }], warnings: [{ attribute, layerId, code: "text_shrunk", fromFontSize, toFontSize }], nextStep }, plus the same two preview images attached as PNG image content blocks.

{ checkoutUrl, cartId, designAssetId, lineItem: { productTitle, variantTitle, packPrice, currency, selectedOptions }, instructions }

A failed tool call is still HTTP 200 and a JSON-RPC result: the result has isError: true and its single text block is a JSON envelope with a stable code, a human-readable message and optional details.

{
  "content": [
    {
      "type": "text",
      "text": "{\"error\":{\"code\":\"product_unavailable\",\"message\":\"This product is not available for purchase.\",\"details\":{\"handle\":\"unknown-handle\"}}}"
    }
  ],
  "isError": true
}

• create_business_card_design: 20 calls per minute per API key.
• create_checkout: 3 calls per hour per design and 8 per hour per buyer email. Each call creates a new cart; reuse the returned checkoutUrl rather than calling again.
• Exceeding a limit returns rate_limited with details.retryAfterSeconds.
• Requests time out after 300 seconds.
• search_products queries are limited to 160 characters and 20 results.
• Logo images must be publicly reachable over https, PNG or JPEG, at most 10 MiB, and between 32 and 8000 pixels on each side.

• A design token is valid for 7 days. The field values and preview images behind it are retained for that period so the token can be redeemed; preview URLs themselves expire after 5 minutes, and the same images are returned inline with the response.
• When a checkout is created, the print-ready artwork is attached to the cart and retained with the resulting order for production and reorders, exactly as for designs made on inkfe.com.
• The buyer's email is used to start the checkout; shipping and payment details are collected on the checkout page and never pass through the connector.
• Logo images are fetched once from the URL you provide and stored only as part of the design.

Questions about keys, the template list or an order placed through the connector: orders@inkfe.com. Include the tool name and error code from the response; never include your API key.

To report a security issue, email the same address with "Security" in the subject line.