Pocketsflow
HumanAgent

Add Pocketsflow to Zed's agent.

Zed calls MCP servers context servers. Add Pocketsflow with only its address, leave out any header, and Zed starts the standard MCP sign-in for you. The agent panel can then read a product or add a webhook without leaving your file.

See the setup
Connects via
Remote context server
Works in
Zed editor (agent panel)
Plan
Zed is free to download; the agent needs a model you have access to.

From an ask in Zed to your store and back.

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

Zed

Get the Starter Kit product and print its id and price.

Pocketsflow MCP
  1. get_product
Your store

Reads one product so the agent uses real values.

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

Connect Zed in 3 steps.

  1. Add a remote server

    Open Settings → AI → MCP Servers, click Add Server, then Add Remote Server. Or add the entry below with zed: open settings file.

  2. Allow access

    With no Authorization header set, Zed asks you to sign in. 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).

  3. Ask the agent

    Open the agent panel and ask. The Pocketsflow tools are listed under the server.

settings.jsonJSON
"context_servers": {
  "pocketsflow": {
    "url": "https://www.pocketsflow.com/mcp"
  }
}

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

What to ask Zed.

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 the agent 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

Why no API key?

Zed runs the standard MCP sign-in when a remote server has no Authorization header. Add the address only.

Which model does it use?

Whichever model Zed's agent is set to. Pocketsflow works the same with any of them.

Can Zed's agent refund a buyer?

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

How do I disconnect Zed?

Delete the MCP: Zed key (the name the app gives itself) under Developers → API keys in your dashboard. Access stops on the next request.

Connect Zed, 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