Skip to main content
Windsurf is an AI-native editor whose Cascade agent can call tools and edit code. Connect it to the Pocketsflow MCP server so Cascade can act on your account, and add a workspace rule so it writes integration code correctly.
Prerequisites
  • Windsurf installed.
  • A Pocketsflow API key from Developers → API keys (use pk_test_… while building).

Connect the Pocketsflow MCP server

Add the Pocketsflow MCP server to Windsurf’s MCP config (Cascade → MCP serversConfigure, which edits ~/.codeium/windsurf/mcp_config.json):
Refresh the server list in Cascade. It can now run Pocketsflow tools — “list my last 10 orders”, “create a $29 product and give me the checkout link”, “cancel subscription sub_123”. Each call runs as your account, scoped by the key.
The MCP config holds your API key — keep it out of shared repos. Prefer a pk_test_… key while developing, and never expose pk_live_… keys.

Add a workspace rule

Give Cascade project context and standards. Create .windsurf/rules/pocketsflow.md in your workspace root:
Use the Copy as Markdown / open-in-editor action in the top-right of any docs page to paste an authoritative reference straight into Cascade as context.

Typical workflow

1

Plan with Cascade

Ask Cascade to design the checkout + webhook flow using the workspace rule and docs.
2

Validate via MCP

Have it create a test product and checkout session with your pk_test_… key.
3

Exercise the webhook

Send a test event and confirm the handler verifies the signature and settles the order idempotently.