Agent Quickstart

CONNECT VIA MCP

Preznt hosts one MCP endpoint — https://api.preznt.net/mcp (Streamable HTTP, no API key). Every client below connects with that URL alone; what differs is which file it goes in and what the URL field is called.

🤖 CLAUDE CODE

1. 1

   Add the server:

   COPY

   claude mcp add --scope user --transport http preznt https://api.preznt.net/mcp

2. 2

   Restart Claude Code — MCP servers are read at startup, so a server added mid-session stays disconnected until you quit and reopen.

3. 3

   Ask it to order something:

   COPY

   Using the Preznt MCP tools, send a bouquet in test mode to
   Jane Doe, 123 Main St, New York, NY 10001. Pick the first
   weekday at least three weeks out. My email is <your email>
   — email me the confirmation link.

✓ Check it worked: Run /mcp (or claude mcp list) and check preznt is listed as connected.

⚠ Watch out: Without --scope user the server is registered only for the directory you ran the command in, so Claude Code started anywhere else won't see it. It is also Claude Code only — the desktop app is configured separately, in its own settings.

🖥️ CLAUDE DESKTOP

The app's own connector settings — no config file, and nothing the claude CLI writes.

1. 1

   In Claude Desktop open Settings → Customize → Connectors, then click the "+" next to Connectors and choose "Add custom connector". (Connectors is no longer a top-level entry in the settings sidebar — it lives under Customize.)

2. 2

   Name it Preznt and paste the endpoint as the remote MCP server URL. Leave the OAuth client ID and secret under "Advanced settings" empty — Preznt takes no credentials:

   COPY

   https://api.preznt.net/mcp

3. 3

   Click Add, then Connect, and ask it to order something:

   COPY

   Using the Preznt MCP tools, send a bouquet in production mode to
   Jane Doe, 123 Main St, New York, NY 10001. Pick the first
   weekday at least three weeks out. My email is <your email>
   — email me the payment link.

Only if custom connectors are unavailable — a Team or Enterprise workspace whose owner has not enabled them — bridge the same endpoint through a local stdio process instead. Settings → Developer (under the "Desktop app" heading in the sidebar) → Edit Config, then restart the app. Needs Node installed.

~/Library/Application Support/Claude/claude_desktop_config.json (%APPDATA%\Claude\ on Windows)

COPY

{
  "mcpServers": {
    "preznt": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.preznt.net/mcp"]
    }
  }
}

✓ Check it worked: Preznt is listed under Settings → Customize → Connectors, and its five tools show up in the "Search and tools" menu under the message box.

⚠ Watch out: claude mcp add configures Claude Code and only Claude Code — it never touches the desktop app, so a server added that way will not appear here however often you restart. Custom connectors are available on every plan, with Free capped at one.

💜 LOVABLE

1. COPY

   Use the Preznt MCP server (https://api.preznt.net/mcp, Streamable HTTP,
   no API key) and build me a "Send flowers" page:
   
   1. Call search_products to load the bouquets — there is one per delivery
      country (US, UK, Germany, Switzerland and Italy), each priced in its own
      currency. Show each one's
      name, photo, price and delivery lead time on the page.
   2. A gift form: the sender's email address (required — they get the
      payment link there), recipient name, street address, city, country
      ("US", "GB", "DE", "CH" or "IT"), the state and zip for a US address or
      the postcode/PLZ/CAP elsewhere, delivery date, and an optional gift
      message (max 255 chars).
   3. Validate the delivery date before submitting: weekdays only, no public
      holiday in the delivery country, at least 3 business days and at most 3
      months from today. Street addresses in those five countries only — no PO
      Boxes, and a US zip must match the state. Send the order with the product whose delivery
      country matches the recipient.
   4. On submit, call create_order with the email address as payer_email and
      mode "production" — always pass mode explicitly, it has no default and
      the order is rejected without it. Then show the returned order_id and
      tell the user to check their inbox — the order is NOT placed until they
      open the link they were emailed and pay.
   5. An order lookup box that calls get_order_status and shows the status
      (pending_payment → accepted → confirmed → delivered).
   
   Orders cannot be cancelled once paid. Say so on the page, above the submit
   button. All five delivery countries are in production, so mode "production"
   sends a real Stripe payment link and really charges the sender wherever the
   order is going.

↗ Example: preznt-petal-pleasures.lovable.app — a gift page built in Lovable on the Preznt tools.

✨ OTHER AGENTS

Any other MCP-capable agent — the endpoint is the same, only where you paste it changes.

1. 1

   Register the endpoint as a remote (Streamable HTTP) MCP server, wherever your client keeps its server list. There is no API key and no other field to fill in:

   COPY

   https://api.preznt.net/mcp

2. 2

   Once the server is connected, paste this to have the agent build a working gift page on top of the five Preznt tools:

   COPY

   Use the Preznt MCP server (https://api.preznt.net/mcp, Streamable HTTP,
   no API key) and build me a "Send flowers" page:
   
   1. Call search_products to load the bouquets — there is one per delivery
      country (US, UK, Germany, Switzerland and Italy), each priced in its own
      currency. Show each one's
      name, photo, price and delivery lead time on the page.
   2. A gift form: the sender's email address (required — they get the
      payment link there), recipient name, street address, city, country
      ("US", "GB", "DE", "CH" or "IT"), the state and zip for a US address or
      the postcode/PLZ/CAP elsewhere, delivery date, and an optional gift
      message (max 255 chars).
   3. Validate the delivery date before submitting: weekdays only, no public
      holiday in the delivery country, at least 3 business days and at most 3
      months from today. Street addresses in those five countries only — no PO
      Boxes, and a US zip must match the state. Send the order with the product whose delivery
      country matches the recipient.
   4. On submit, call create_order with the email address as payer_email and
      mode "production" — always pass mode explicitly, it has no default and
      the order is rejected without it. Then show the returned order_id and
      tell the user to check their inbox — the order is NOT placed until they
      open the link they were emailed and pay.
   5. An order lookup box that calls get_order_status and shows the status
      (pending_payment → accepted → confirmed → delivered).
   
   Orders cannot be cancelled once paid. Say so on the page, above the submit
   button. All five delivery countries are in production, so mode "production"
   sends a real Stripe payment link and really charges the sender wherever the
   order is going.

⚠ Watch out: Direct REST access is not a supported interface — MCP is the only public surface, so a client that cannot speak Streamable HTTP MCP cannot use Preznt.

Prefer running it yourself? A stdio variant ships with the Preznt repo: claude mcp add preznt -- npx tsx src/mcp/server.ts (needs a checkout of the repo and tsx; run it from the repo root).

BUILD A GIFT PAGE

This prompt has the agent build a working gift page on top of the five Preznt tools. It works in any of the clients above — Lovable, Claude Code or Claude Desktop — because only the way you point them at the endpoint differs. In an app builder like Lovable the URL in the prompt is enough on its own; the coding clients need the server registered first.

Use the Preznt MCP server (https://api.preznt.net/mcp, Streamable HTTP,
no API key) and build me a "Send flowers" page:

1. Call search_products to load the bouquets — there is one per delivery
   country (US, UK, Germany, Switzerland and Italy), each priced in its own
   currency. Show each one's
   name, photo, price and delivery lead time on the page.
2. A gift form: the sender's email address (required — they get the
   payment link there), recipient name, street address, city, country
   ("US", "GB", "DE", "CH" or "IT"), the state and zip for a US address or
   the postcode/PLZ/CAP elsewhere, delivery date, and an optional gift
   message (max 255 chars).
3. Validate the delivery date before submitting: weekdays only, no public
   holiday in the delivery country, at least 3 business days and at most 3
   months from today. Street addresses in those five countries only — no PO
   Boxes, and a US zip must match the state. Send the order with the product whose delivery
   country matches the recipient.
4. On submit, call create_order with the email address as payer_email and
   mode "production" — always pass mode explicitly, it has no default and
   the order is rejected without it. Then show the returned order_id and
   tell the user to check their inbox — the order is NOT placed until they
   open the link they were emailed and pay.
5. An order lookup box that calls get_order_status and shows the status
   (pending_payment → accepted → confirmed → delivered).

Orders cannot be cancelled once paid. Say so on the page, above the submit
button. All five delivery countries are in production, so mode "production"
sends a real Stripe payment link and really charges the sender wherever the
order is going.

TROUBLESHOOTING

/mcp shows preznt ✗ failed to connect? Work through these in order — the first two account for nearly every report. Steps 1, 3 and 4 apply to any client; step 2 is Claude Code's scope rules. On any other MCP client, check the client-specific note in Connect via MCP first — a config in the wrong file, or the URL under a field name the client does not read, looks exactly like a connection failure.

1. Restart the client. MCP servers are loaded at startup, so a server added mid-session shows as not connected until you quit and reopen. (Some clients offer a refresh button in their MCP panel instead.)
2. Check nothing is shadowing the entry. Claude Code resolves a server name by scope — local, then project, then user — and the first match wins. If you ever added a preznt server in the current directory (the stdio variant above, or an older URL), that entry silently overrides the one --scope user just wrote, and it is the one failing.
   COPY

   claude mcp get preznt          # which scope and URL actually won
   claude mcp remove preznt -s local     # drop a shadowing local entry
   claude mcp remove preznt -s project   # ...or a project one

   Then re-add with --scope user and restart.
3. Confirm the endpoint from your own machine. This is the same handshake Claude Code performs. A JSON result naming preznt means the service is up and the problem is local config; a hang or TLS error points at a proxy or firewall between you and api.preznt.net.
   COPY

   curl -sX POST https://api.preznt.net/mcp \
     -H 'Content-Type: application/json' \
     -H 'Accept: application/json, text/event-stream' \
     -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'

4. Check the URL is complete. It must end in /mcp — a URL truncated while copying is a connection failure, not a 404 you would see.

A bare GET of the endpoint answering 405 is correct, not a fault: the endpoint is stateless and takes POST only, so there is no SSE stream to open. Still stuck? Tell us.

THE FLOW

TOOLS

A summary — every parameter, result shape and error is on the MCP tool reference.

EXAMPLE ORDER

// create_order input
{
  "product_id": "prod_ABC123",       // from search_products
  "mode": "test",                    // REQUIRED — "test" or "production", no default
  "delivery_date": "2026-09-21",     // YYYY-MM-DD, weekday, 3 business days–3 months out
  "payer_email": "alex@example-domain.com",  // required (unless payer_phone is given on a UK order)
  "payer_name": "Alex",              // optional, greets them in the email
  "recipient": {
    "name": "Jane Doe",
    "address": "123 Main St",        // street address — no PO Boxes
    "city": "New York",
    "country": "US",                 // "US", "GB" ("UK" too), "DE", "CH" or "IT"; defaults to "US"
    "state": "NY",                   // US only: 2-letter code, 50 states + DC
    "zip": "10001"                   // must be a real zip inside that state
  },
  "gift_message": "Happy Birthday!"  // optional, max 255 chars (the florist's card limit)
}

// result — pending, not accepted: it is waiting on the human
{
  "order_id": "ord_XYZ789abc",
  "mode": "test",
  "status": "pending_confirmation",
  "amount": { "cents": 10000, "currency": "USD", "formatted": "$100.00" },
  "delivery_country": "US",
  "confirmation_email": { "sent": true, "to": "al•••@example-domain.com" },
  "next_step": "al•••@example-domain.com must open the confirmation link in that email to move the order to \"accepted\". Nothing is charged.",
  "message": "Order created and waiting on the human. ... Poll GET /v1/orders/:id for status updates."
}

ORDER RULES

ORDER STATUSES

pending_confirmation → test order: waiting for the human to click Confirm
pending_payment      → production order: waiting for the human to pay
payment_expired      → the 48h payment link lapsed unpaid
accepted    → order received (reached only once the human confirmed or paid)
confirmed   → order placed
delivered   → delivered!
failed      → could not be fulfilled — escalate via create_support_ticket
cancelled   → cancelled by Preznt
unknown     → no order with this ID / status cannot be determined

CONTACT & CONSENT

RATE LIMITS

A rate-limited call carries a Retry-After header in seconds — wait that long before retrying.

There is also a service-wide queue cap, which is not a per-caller limit. Orders are placed by hand, so while 500 paid orders are already waiting to be placed, create_order refuses production orders with a 503 — nothing is charged and no order is created — until the backlog clears. test orders are never refused for this reason.