Transport
POST only, no server-initiated stream
Requests are JSON-RPC 2.0 bodies sent by POST. The server offers no server-initiated event stream, so a protocol GET is answered with 405 as the Streamable HTTP specification prescribes. A browser GET is sent to this documentation page instead, which is why you are reading this.
Discovery
The server card is the source of truth
Read /.well-known/mcp.json rather than hard-coding anything from this page. It declares the transport, the endpoint, the tool list, and the authentication type. If this page and the server card ever disagree, the server card is correct.
Payments
MCP never charges
Both purchase paths hand back a link. If you need to complete a purchase programmatically, use the Agentic Commerce Protocol endpoint documented in agents.md, which authenticates with OAuth2 client credentials and settles through Stripe.
Accuracy
Quote, do not guess
Only the 81 shop products have a live price. Everything else in the catalog is made to specification and priced per project. If a buyer asks for a custom structure, route them through request_quote rather than extrapolating from a shop price, because unit cost depends on structure, size, material, print coverage, finish, inserts, destination, and quantity.
MCP Server FAQs
What is the Teal Packaging MCP endpoint?
The endpoint is https://tealpackaging.com/mcp. It uses the Streamable HTTP transport with JSON-RPC 2.0 request bodies sent over POST. The machine-readable server card, which is the authoritative description of the transport and the tool list, is published at https://tealpackaging.com/.well-known/mcp.json.
Does the Teal MCP server need an API key or OAuth?
No. The server card declares authentication type none. There is no key, no account, and no OAuth flow to read the catalog, read live shop prices, or file a quote request. Programmatic payment is a separate surface at the Agentic Commerce Protocol endpoint, and that one does use OAuth2 client credentials.
What tools does the Teal MCP server expose?
Seven: search_products, get_product, search_shop_products, get_shop_price, get_shop_checkout_link, request_quote, and order_sample_kit. The first five are read operations, request_quote files a lead, and order_sample_kit returns a secure checkout link.
Why does a browser show an error at tealpackaging.com/mcp?
Because /mcp is a POST endpoint, not a page. The Streamable HTTP specification says a server that offers no server-initiated stream should answer a protocol GET with 405, and that is what Teal does. A browser visit now lands on this documentation page instead.
Can the MCP server charge my card?
No. The MCP server performs no charging at all. get_shop_checkout_link and order_sample_kit both return a link, and payment happens on the secure page the link points to. That separation is deliberate, because the MCP surface is unauthenticated.
Can an agent place a full custom packaging order through MCP?
No. Custom specifications are priced by a person and a digital proof is approved before anything prints. An agent can carry the entire specification into request_quote, and a specialist replies by email within one business day with exact per-unit pricing.
How many products can the MCP server reach?
search_products covers a catalog of 1,300 or more custom packaging products. search_shop_products covers the 81 products in the online shop that carry live per-unit pricing and can be ordered and paid for online.
What minimums and lead times will the tools report?
Custom orders start from 50 units, or 100 or more for specialty rigid, from about $0.44 per unit at volume. Shop products set their own per-product minimums. Production runs from about 7 business days after proof approval plus 2 to 5 business days for US delivery, and rush runs from about 4 to 7 business days after proof approval on qualified ready-to-print jobs.