Introducing the Pocketsflow startup program: Win $100K if you are a startupWin $100K if you are a startup
Pocketsflow
All posts
MacBook Pro open on a desk beside a ceramic mug
Photo by Mia Baker on Unsplash
Guides

How to Connect Pocketsflow to Claude via MCP

Pocketsflow Team8 min read

Apply it with your AI

To connect Pocketsflow to Claude via MCP, add the hosted server URL https://api.pocketsflow.com/mcp as a custom connector in Claude, sign in and click Allow (or authenticate with an API key in a desktop client), and Claude instantly gets 53 tools for products, checkout, discounts, orders, refunds, subscriptions, and more. The whole setup takes a few minutes, and your first product can be live before your coffee cools. This guide walks through both connection methods, every tool group, and a worked example with real fee math.

What this connection actually gives you

The Model Context Protocol (MCP) is an open standard that lets AI assistants call real software tools instead of just generating text. Pocketsflow runs a hosted MCP server, so there is nothing to install and no server to maintain on your side. Once connected, you manage your store the way you already talk to Claude: in plain words.

Instead of clicking through dashboards, you type things like “create a $49 one-time product called Pro license” or “refund yesterday's duplicate order and tell me the customer's history,” and Claude executes the calls. Every action runs against your live Pocketsflow account and shows up in your dashboard exactly as if you had done it by hand. If you are still deciding what to sell through it, our roundup of MCP server ideas developers can build and sell is a good source of product inspiration.

What you need before you start

You need exactly three things, and you probably have two already:

  • A Pocketsflow account. Selling has no monthly fee—each sale carries one estimated itemized transaction cost of 4.7% + $0.30 (about $5.00 on a $100 sale), shown line by line on every order.
  • Access to Claude: the Claude.ai web or desktop app with custom connector support, or Claude Desktop / Claude Code for the API-key method.
  • The hosted server address: https://api.pocketsflow.com/mcp. Note that this is a connector address for your AI app, not a web page you visit in a browser.

Full protocol details live in the Pocketsflow MCP server reference. Claude's connector screens change from time to time, so if a button label below doesn't match what you see, look for the nearest equivalent (Connectors, Integrations, or Custom connector).

Method 1: Connect in Claude.ai (no API key)

This is the fastest path and the one most creators should use. Open Claude's settings, find Connectors (or Integrations), and choose to add a custom connector. Paste https://api.pocketsflow.com/mcp as the server URL.

Claude will open Pocketsflow, where you sign in and click Allow access. That's the whole authentication step—no tokens to copy, no config files to edit. The connection is scoped to your account, and you can revoke it at any time from your Pocketsflow dashboard.

Go back to a Claude chat and test it with something harmless and read-only first: “list my Pocketsflow products.” If Claude answers with your catalog (or an empty list on a new account), the connection works and you can move on to selling.

Method 2: Connect with an API key (desktop and code clients)

If you use Claude Desktop, Claude Code, or your own agent, connect over HTTP with a Bearer token instead. In your Pocketsflow dashboard at app.pocketsflow.com, go to Developers and create an API key. Use a pk_live_ key for your real store and a pk_test_ key while experimenting—test mode never touches real money or real customers.

Add the server to your MCP client configuration with the URL https://api.pocketsflow.com/mcp and an Authorization: Bearer <your-key> header over HTTP transport. Every action Claude takes is then scoped to that key's live or test mode. Keep keys out of screenshots, shared docs, and chat transcripts, and rotate a key the moment you suspect it leaked.

The 53 tools Claude gets

The connection exposes 53 tools across 13 groups. You don't need to memorize them—just describe the outcome and Claude picks the right calls. Here is the full map so you know what's possible.

Selling tools

  • Products (6 tools): create, update, list, and archive the digital products in your catalog.
  • Checkout (1 tool): spin up hosted checkout sessions you can link from anywhere. Our guide to the best checkout for digital products explains what makes a checkout page convert once the link exists.
  • Discounts (5 tools): percentage and fixed-amount codes, launch sales, and limited-time offers.
  • Upsells (5 tools): post-purchase offers that raise average order value without extra traffic.
  • Subscriptions (3 tools): recurring plans, billing changes, and cancellations.

After the sale

  • Orders and customers (4 tools): look up any order, inspect customer history, and answer “where's my download?” in seconds.
  • Refunds (3 tools): full and partial refunds with reasons attached.
  • Reviews (1 tool): pull social proof for product pages and launch posts.
  • Webhooks (6 tools): wire Pocketsflow events into your own automations.
  • Newsletters (10 tools): write, schedule, and send email campaigns to your buyers.
  • Link-in-bio (2 tools): keep your social storefront pages current.
  • Partners (6 tools): run affiliate and partner programs, the highest-leverage channel for many creators.
  • Account (1 tool): check account status and settings.

Your first sale from chat: a $49 Pro license

Here is the canonical first transcript. Paste this into Claude once connected: “Create a $49 one-time product called Pro license with a 20% launch discount, and give me the checkout link.” Behind the scenes Claude chains three tools: create_product builds the $49 listing, create_discount adds the 20%-off launch code, and create_checkout_session returns a shareable payment link.

Before you share that link, know your numbers. Pocketsflow has no monthly selling fee; each sale carries an estimated itemized transaction cost of 4.7% + $0.30. For the $49 Pro license that is $49 × 0.047 + $0.30 ≈ $2.60, so you keep about $46.40. A buyer using the 20% launch code pays $39.20, the estimated cost is $39.20 × 0.047 + $0.30 ≈ $2.14, and you keep about $37.06. All figures are illustrative estimates—the exact amount varies by payment method, buyer region, and currency, and is itemized on every order:

Line itemAmount
Pro license, launch price (20% off $49)$39.20
Estimated transaction cost (4.7% + $0.30)−$2.14
You keep (estimate)$37.06

Price with this math in mind from day one. Our guide to pricing digital products shows how to fold fees into prices customers still say yes to.

Five copy-paste prompts to run your store

Once the basics work, these prompts cover a full selling week:

  1. “Draft a launch discount for my bestseller: 25% off for 72 hours, then send me the checkout link.”
  2. “Add a $19 order-bump upsell to my Pro license checkout and estimate my earnings per 100 buyers at a 15% take rate.”
  3. “Summarize this week's orders: total revenue, refunds, and anything that looks unusual.”
  4. “Write and schedule a newsletter to past buyers announcing the Pro license launch discount.”
  5. “Set up a partner program for the Pro license at 30% commission and draft the invite message.”

Read each draft before it goes live, especially anything that charges money or emails customers. Claude proposes; you approve.

Troubleshooting and safety rules

Three quick fixes cover most connection problems:

  • Claude can't reach the server: re-check the URL character by character—https://api.pocketsflow.com/mcp with no trailing page path. Remember it is a connector address, not a web page.
  • Authentication fails: in Claude.ai, remove the connector and re-add it, then sign in and Allow again. With API keys, confirm you are sending the full key as a Bearer token and that you haven't mixed up pk_test_ and pk_live_.
  • Actions don't appear in your dashboard: you are probably in test mode. Switch to the live key or live connection and retry.

And three rules keep agent commerce safe: start every new workflow in test mode, require your explicit approval before refunds, mass emails, or price changes go out, and treat anything Claude quotes from customer data as untrusted input worth verifying in the dashboard. Scoped keys, narrow permissions, and a human in the loop are the whole security model.

You now know both ways to connect, all 53 tools, and the exact transcript for a first $49 sale. The connector takes minutes; the catalog is the real work, and you can build that conversationally too. Start free on Pocketsflow and let Claude handle the busywork while you make the product.

Start accepting payments today.

Sell your first product today, and let the AI you already use run the busywork.

Or start from the AI you already use