InkFE MCP connector

Anyone can connect; there is no invitation or waitlist. Add InkFE to your AI app as a custom connector (remote MCP server) using the endpoint below. Guests can design and start checkout without an account. To save a design to your InkFE account, sign in with your InkFE login when your app asks and review the requested permissions. Your app handles the OAuth connection. Questions: orders@inkfe.com.

Your app needs remote MCP over Streamable HTTP; signing in also needs compatible OAuth. InkFE is listed on the official MCP Registry as com.inkfe/print.

You pay on InkFE's secure Shopify checkout. Review both artwork sides in your AI app, then review the final charges and pay in Shopify.

InkFE currently sells to shipping addresses in the United States. Quotes are in US dollars; Shopify confirms shipping, tax and the final total. InkFE is operated by InkFE, LLC.

Claude web · Verified

1. Add a custom remote connector using the endpoint below.
2. Complete InkFE sign-in, review permissions and allow the connection.
3. Start a new chat and enable InkFE. If the tool list is stale, refresh the connector tools, then turn InkFE off and on in that chat.
4. Ask to see business-card templates. Open the labelled front and back proof links if your app does not display the images inline.

Works end to end: design, both proofs, approval and Shopify checkout. Changing the artwork creates a new version that needs your approval again.

Muse web · Verified

Add InkFE as a custom connector using the endpoint below, then ask for business cards. Design, proof review, approval and Shopify checkout all work. Never paste passwords or card details into the chat.

If a request seems stuck, ask your assistant to check its last result before trying again.

Other apps

Any AI app that supports remote MCP connectors can connect with the same endpoint. ChatGPT support is coming soon.

• 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. Handle the negotiated protocol's JSON or server-sent event response. The server is stateless; no persistent session id is required.

Builder example for clients that accept this configuration format; your client handles OAuth discovery and keeps its tokens private:

{
  "mcpServers": {
    "inkfe": {
      "type": "http",
      "url": "https://www.inkfe.com/api/mcp"
    }
  }
}

POST https://www.inkfe.com/api/mcp
Authorization: Bearer <access token managed by your client>
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"}}}

Use the live tools/list schemas and returned instructions as the source of truth. Guest tools and write tools depend on the endpoint's enabled capabilities. Generated client notes can become stale; get_product never substitutes for get_quote.

Customer connections use InkFE-owned OAuth with Shopify-backed sign-in. The AI app gets a revocable grant for the permissions you approve, not your Shopify login credentials. Account-owned designs require that same verified customer on later calls. Manage or revoke connections at AI connections.

When guest access is enabled, compatible clients can browse without signing in. Call start_guest_session and pass its private guestToken with design and checkout calls. Guest credentials expire after seven days; revoke_guest_session ends access sooner. This does not delete artwork.

Signed-in customers create account-owned designs directly; they do not need a guest session. Guests can verify ownership through the returned private save link. Once saved, the design belongs to that account and guest access to it ends.

Invalid supplied credentials receive 401 Unauthorized. Reconnect through your app if the connection has expired or was revoked. Builders must keep tokens in the client's secure credential storage, out of prompts, logs and URLs. Provisioned integration keys are a separate operator-managed capability, not customer identity.

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. Quote and checkout. Once the buyer approves the previews and chooses every product option, call get_quote. Show the pack, subtotal, production estimate and unknown charges. After explicit artwork approval, call approve_design_proof with both side-review confirmations. Pass its approvalId and the separately confirmed quoteToken to create_checkout. Expired or changed terms require a new quote and confirmation. Shopify checkout confirms shipping, tax, discounts, delivery availability and the final payable total.

Use your own business details. These prompts keep product choices, artwork approval and payment as separate decisions.

1. “Show me InkFE business-card templates. I want one pack of 100 with Square corners. Show the current price and anything still unknown.”
2. “Use the template I selected. Ask me for each required printed field, then show both sides and any fit warnings. Stop for my review.”
3. “Change the job title to Operations Manager and show both revised proofs. Do not reuse my previous artwork approval.”
4. After actually reviewing the proofs: “I approve both sides and the selected print options. Show me a current quote before checkout.”
5. After confirming that quote: “Prepare Shopify checkout using the checkout email I provide. I will review final charges and pay there.”

For other products: “Find InkFE postcards and explain which design or upload steps are supported. Give me the product page for anything this connector cannot complete.” Catalog discovery is broader than the current business-card design journey.

• Connection unavailable: restart the connection from your AI app. Do not resubmit an old consent page. For Inspector, keep the registered localhost callback exact; localhost and 127.0.0.1 are different callback addresses.
• Tools missing: refresh the connector's tools and start a new chat. Do not invent capabilities the tool list does not show.
• Proof link expired: ask the agent to refresh the same design's proofs. Links last five minutes; refreshing does not change the artwork, renew a design token or grant approval.
• Quote expired or changed: request a new quote and confirm its terms. Changed artwork or print options also needs new proof approval. Never accept changed terms automatically.
• Checkout interrupted: return to its existing link. A tool retry must use the same approval, buyer and purchase details. An uncertain cart outcome needs recovery, not a replacement order.
• Repeated authentication errors: stop and contact support with the tool name and error code. Do not paste credentials, loosen permissions or turn a failed sign-in into guest access.

Tools return JSON in a text content block; design and proof tools also return image blocks. 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\": [ ... ] }"}]}}

{ guestToken, expiresAt, instructions }

{ revoked: true }

Products include handles, titles, price ranges, options, URLs and artwork workflow support. Filters can return fewer matches than the candidate limit; an empty result is not an exhaustive inventory statement.

Product, dimensions, options and variants, plus configuration status, quantity rules, artwork workflow, source freshness and policy links. A resolved variant is catalog information, not a purchase quote; call get_quote.

{ quoteId, quoteToken, productTitle, configuration, variantId, quantity, subtotal: { amount, currency }, shipping, tax, discounts, total, delivery, issuedAt, expiresAt, instructions }. Shipping, tax, discounts and total are unknown until Shopify checkout. Delivery is unconfirmed; productionBusinessDays is an estimate or null.

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

{ designToken, proof (artifact and saved-image hashes), saveUrl (private browser ownership link), 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.

A new designToken/designId, proof hashes, both preview images, signed preview links and warnings. Review and approve the new revision.

Design identity, proof hashes, warnings, original expiry, 300-second links and both saved image blocks. Refresh is not approval.

{ approvalId, proofHash, configurationHash, approvedAt, expiresAt, evidence: agent_reported, designId, printedSides, instructions }. Repeating identical approval preserves its id and expiry.

{ approvalId, quoteId, quotedSubtotal, 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 integration or guest session.
• create_checkout: 3 calls per hour per design, with additional upload limits. One approval maps to one purchase attempt. Reuse the returned checkoutUrl; identical retries recover the same cart and artwork. Changed buyer details conflict, and uncertain outcomes stop for recovery.
• Exceeding a limit returns rate_limited with details.retryAfterSeconds.
• Operations also share a global 60-per-minute limit. Guest startup/revocation and anonymous catalog reads each share a 20-per-minute public budget.
• 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 seven days; that expiry does not delete artwork. Preview URLs expire after five minutes; the saved images can also appear inline when the AI app supports image content.
• The policy for unpaid, unsaved guest drafts is 30 days from the design request. Saved, checkout-linked and unresolved purchase artwork is protected by separate retention rules. Token expiry is not deletion.
• 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 by Shopify. Do not send card details or verification codes to your AI chat. Printed contact details may belong to someone other than the buyer.
• Logo images are fetched once from the URL you provide and stored only as part of the design.

Questions about connecting, 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 access, guest, design or quote tokens, signed preview URLs, or private checkout links.

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

Read our privacy policy, terms of service, returns and refunds policy or contact InkFE. Your AI app also has its own data-handling terms.