Pocketsflow MCP Setup for VS Code and GitHub Copilot

To set up Pocketsflow MCP in VS Code, run MCP: Add Server from the Command Palette, choose HTTP, paste https://www.pocketsflow.com/mcp and name it pocketsflow. Then sign in to Pocketsflow and click Allow access, with no API key to copy.

One detail matters in VS Code: Pocketsflow has 303 tools, and a Copilot chat request can have at most 128 enabled. This guide shows the setup, then which Pocketsflow tools to keep on.

How to connect Pocketsflow to VS Code

1. Create a free Pocketsflow account, or sign in to the one you sell with. Switch the dashboard to test mode first if you want Copilot on sandbox data.
2. In VS Code, open the Command Palette (Ctrl+Shift+P, or Shift+Cmd+P on a Mac) and run MCP: Add Server.
3. Choose HTTP (HTTP or Server-Sent Events) and paste https://www.pocketsflow.com/mcp.
4. Enter pocketsflow as the server ID.
5. For a personal setup, choose Global, then Copilot Global. This keeps the server out of your project files.
6. When VS Code connects, your browser opens Pocketsflow. Sign in, check which app is asking, and click Allow access.

Pocketsflow creates an API key named “MCP: <app>” for VS Code, in the mode your dashboard was in when you clicked Allow. VS Code only receives sign-in tokens: they last one hour and renew on their own. To disconnect, delete that key under Developers > API keys.

The two VS Code config files for Pocketsflow

VS Code now has two config formats, and the Pocketsflow entry differs between them. The guided flow above writes the first one for you.

• Copilot format, in ~/.copilot/mcp-config.json for you or .mcp.json at the workspace root for a team: { "mcpServers": { "pocketsflow": { "type": "http", "url": "https://www.pocketsflow.com/mcp" } } }
• VS Code format, in .vscode/mcp.json or your profile's mcp.json: { "servers": { "pocketsflow": { "type": "http", "url": "https://www.pocketsflow.com/mcp" } } }

The only difference is the top key: mcpServers or servers. VS Code labels the second format deprecated in its guided flow, but it still works. Leave out any oauth or headers field. Pocketsflow supports dynamic client registration and vscode:// redirects, so VS Code needs no client ID.

Check that Pocketsflow answers in VS Code

VS Code's own docs say a saved config isn't proof that the agent can use a server. Run one harmless request and look at the tool call. In Copilot Chat, in agent mode, paste:

“Use the pocketsflow MCP server to show my account and what I sell. Do not change files.”

Expand the tool call in the chat. It should be get_account from the pocketsflow server, it should return your store without a connection error, and Copilot's answer should match that output. If all three hold, Pocketsflow is connected.

Pocketsflow and the VS Code 128 tool limit

VS Code allows 128 tools per chat request, and Pocketsflow brings 303 across 48 groups. Turning all of them on at once gives a “Cannot have more than 128 tools per request” error. The fix is to keep on the Pocketsflow groups you use. For most sellers, these 6 groups come first, 36 tools in all:

That set leaves 92 slots for your other tools. To pick tools, use Configure Tools in the chat input for a Local session, or Chat: Open Customizations > Tools for a Copilot session. You can also turn on the github.copilot.chat.virtualTools.threshold setting and let VS Code manage a large tool set.

Prompts to paste into VS Code Copilot

Each Pocketsflow prompt below lists the tools Copilot calls, so you can check them in the chat.

1. “Create a $29 product called Starter Kit and give me the checkout link.” Calls create_product and create_checkout_session.
2. “Make LAUNCH20, 20% off everything until Sunday.” Calls create_discount.
3. “How did sales go this week, and who are my top customers?” Calls list_orders and list_customers.
4. “How much can I withdraw, and did my last payout land?” Calls get_payout_balance and list_payouts.
5. “Draft a newsletter about the launch, but don't send it until I approve.” Calls create_post, and send_post only after you say yes.

Sending campaigns to your list needs a Pocketsflow email plan. Selling, discount codes and MCP itself are free on every plan.

Pocketsflow with an API key, for headless VS Code setups

Pocketsflow also accepts an API key for machines with no browser to sign in from, such as a remote dev box. Create a key under Developers > API keys, set it as the POCKETSFLOW_API_KEY environment variable, and reference it from the Copilot config: { "mcpServers": { "pocketsflow": { "type": "http", "url": "https://www.pocketsflow.com/mcp", "headers": { "Authorization": "Bearer ${POCKETSFLOW_API_KEY}" } } } }

The Copilot format reads ${NAME} references in header values, so the key itself never sits in the file. Use a pk_test_ key while you build. For clients that only run local servers, Pocketsflow also ships a stdio bridge, npx -y @pocketsflow/mcp.

What stays in the Pocketsflow dashboard

Pocketsflow keeps money movement out of Copilot. Payouts are read only, so withdrawing and bank details stay in the dashboard. Payment refunds stay there too: create_refund sets a refund policy and never returns money. Plans can't be bought through MCP; a tool that needs a higher plan returns FEATURE_LOCKED and Copilot points you to billing.

For other editors, read the Cursor setup guide or the Windsurf setup guide. For every tool group, read what Pocketsflow MCP can do, or start at the Pocketsflow MCP page.