Pocketsflow
HumanAgent

Connect Pocketsflow to Windsurf's Cascade.

Cascade supports sign-in for remote MCP servers, so the config is one address with no key. Then it can read the order that broke your webhook handler, cancel a test subscription and open a fresh checkout to try again.

See the setup
Connects via
Cascade MCP config
Works in
Windsurf editor (Cascade)
Plan
Any Windsurf plan with Cascade.

From an ask in Windsurf to your store and back.

You type in Windsurf. It calls a Pocketsflow tool, your store changes or answers, and the result comes back to the chat.

Windsurf

Show me the journey of the last order: page view to payment.

Pocketsflow MCP
  1. list_orders
  2. get_order_journey
Your store

Reads every step the buyer took before paying.

Figure 1. An ask in Windsurf, the Pocketsflow tools it calls, and what changes in your store. You approve the app once; every change lands in your dashboard.

Connect Windsurf in 3 steps.

  1. Open the MCP config

    In Cascade's MCP menu, choose Open MCP config file, or go to Settings → Tools → Windsurf Settings → Add Server.

  2. Add the server

    Paste the config below and press refresh in the MCP menu.

  3. Allow access

    Your browser opens Pocketsflow. Sign in to Pocketsflow and click Allow access. Pocketsflow adds a key named MCP: <app> under Developers → API keys, in the mode your dashboard is in (live or test).

mcp_config.jsonJSON
{
  "mcpServers": {
    "pocketsflow": {
      "serverUrl": "https://www.pocketsflow.com/mcp"
    }
  }
}

Server address https://www.pocketsflow.com/mcp

What to ask Windsurf.

Write it the way you would ask a colleague. Under each ask are the Pocketsflow tools it calls.

What it can and can't do.

Connecting an AI is not handing over the keys. You approve it, you see every change, and you can unplug it in one click.

It can

  • Use the same 303 tools as the public API: products, checkout links, discounts, upsells, orders, customers, subscriptions, license keys, usage billing, webhooks, newsletters and analytics.
  • Read your payouts: what is ready to withdraw, what is still clearing, and why a payout is on hold.
  • Set the refund policy buyers see at checkout, and look up any order's payment, fees and tax.
  • Work in test mode with no real money, if your dashboard is in test mode when you click Allow.

It can't

  • Refund a payment or withdraw money. Refunds and withdrawals stay in your dashboard.
  • Connect without you: nothing happens until you sign in to Pocketsflow and click Allow access.
  • See another store. Every call is scoped to the account you approved.
  • Use a paid feature your plan lacks. It gets a clear error and tells you which plan unlocks it.

The setup prompt asks Cascade to check with you before anything goes live, and every change shows in your dashboard. To disconnect any app, delete its MCP: <app> key under Developers → API keys. It stops on the next request. Access tokens last an hour and renew themselves; one left unused for 30 days expires.

For developers.

The server speaks streamable HTTP with OAuth 2.1 (PKCE, dynamic client registration) and exposes 303 tools, the same public API as our REST endpoints and the pocketsflow SDK.

Questions

Is it serverUrl or url?

Cascade takes either for a remote server. The example uses serverUrl, as Windsurf's docs do.

Where is the config file?

Use Open MCP config file from Cascade's MCP menu: it opens the right file for your install.

Do I need an API key?

No. You sign in to Pocketsflow and click Allow access, and the app gets a token for your account. API keys are only for headless servers and CI, where nobody can click Allow.

Can Cascade refund a buyer?

No. Payment refunds are issued from your dashboard. Cascade can find the order, check its payment and set the refund policy buyers see at checkout.

Connect Windsurf, then ask for your first product.

Free to start, no monthly fee. Your AI works in your account with the access you approve.

Start selling free