The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Roastify MCP listing page.
A Tollbooth DPYC operator for the Roastify Developer API. Roastify is a white-label coffee dropshipper: it roasts, prints branded packaging, and ships direct to customers.
This operator lets an AI agent read the Roastify catalog and generate packaging artwork, paid for in Bitcoin Lightning satoshis with no account, no KYC, and no subscription.
nak key generate). The nsec is the only env var:
TOLLBOOTH_NOSTR_OPERATOR_NSEC.btcpay_host, btcpay_api_key,
btcpay_store_id) by Nostr DM. They are vaulted, never put in the environment..fastmcp.yaml is ready.Your tools ship unpriced, and nobody can call a paid tool that has no price. Pricing Studio (iOS) is the operator console: it reads and writes the pricing model live in Neon, so prices never live in code — see tollbooth-pricing-studio.
That indirection is the point. Dynamic per-tool pricing — surge, happy-hour, loyalty discounts, free trials for a first-time patron — is what DPYC gives you that a flat paywall never could.
Every patron delivers their own Roastify API key through the Secure Courier, vaulted per npub. There is no operator-held key and no fallback path.
This follows from the domain rather than being a policy choice. Roastify scopes the catalog, saved designs, and plan tier to the merchant account behind the key — a patron on Base sees a different catalog than one on Pro. A single operator-held key would hand one merchant's world to every caller, which is a wrong answer rather than a limitation to work around. It also means this operator never holds a credential it could misuse, and revoking your key in the Merchant App severs access without involving the operator.
Live keys start rty_live_. Sandbox keys start rty_test_ and do not fulfill — useful for
exercising the read tools without touching production.
| Tool | Tier | What it does |
|---|---|---|
roastify_browse_catalog | read | Catalog products and coffee blends together, plan tier marked |
roastify_get_catalog_product | read | One product with variants, prices, stock, dieline template |
roastify_get_blend | read | One blend: roast level, decaf status, variants |
roastify_list_my_products | read | Your saved designs, cursor-paginated |
roastify_get_my_product | read | One saved design in full |
roastify_check_stock | read | Stock for one SKU or the whole list |
roastify_generate_artwork | write | Generate artwork from a saved design |
roastify_artwork_status | free | Check that job |
Plus the standard DPYC catalog (balance, purchase, courier, pricing, Oracle, status).
It cannot create, update, delete, or sync products. Not a missing feature — the Roastify
API has no such endpoints. /v1/products is read-only, and the words integration, sync,
shopify, and upload do not appear anywhere in the
OpenAPI spec. Saved products and storefront sync are
Merchant App capabilities by design.
It does not place orders. Roastify already routes orders to its own operations and reports tracking back to your storefront. An MCP layer between those adds a hop without adding judgment, so order automation is deliberately left to Shopify and Roastify.
Artwork generation is template personalization, not design. roastify_generate_artwork
rewrites the named text and image placeholders of a design you already authored in the
Roastify Design Studio. It cannot author a design from scratch.
A generated artwork URL is not attached to anything. In Roastify's API the only consumer of an artwork URL is an order line — and orders are out of scope here. You receive a URL and carry it onward yourself. That seam is accepted deliberately; it is not an oversight, and this operator will not simulate a design flow the API cannot complete.
The catalog has no palate data. Origin, region, altitude, processing method, and varietal
exist only in the Merchant App UI. The machine-readable signals are roastLevel, isDecaf,
size, and price; everything else about a coffee's character is prose in its description. Bean
selection is correspondingly weaker than it looks, and this operator does not dress up an
LLM's reading of a description as structured provenance data.
Roastify renders artwork on its own servers, so roastify_generate_artwork hands back a job
id straight away and roastify_artwork_status checks it. Status checks are free — you
learn the work finished by looking, and charging for each look would be charging for waiting.
Pass client_req_id and a repeated request is safe: it becomes Roastify's
Idempotency-Key, so the artwork is not generated twice.
The operator does no waiting of its own — both calls return immediately — so there is no detached executor here and nothing to recycle. That machinery would earn its place only if this operator ever rendered artwork itself.
Roastify's API is version 0.3.1 and its own spec marks it beta, "subject to change." Expect to follow breaking upstream edits, and weigh that before promising this operator's catalog to third-party merchants.
Apache 2.0 — see LICENSE.