Cursor + Pocketsflow - Pocketsflow Docs

Cursor is an AI-native code editor. Connect it to the Pocketsflow MCP server and it can call the API as your account while you build; add a project rule so it writes integration code the right way.

Prerequisites

Cursor installed.
A Pocketsflow account. No API key needed: you approve Cursor with your Pocketsflow login.

Connect the Pocketsflow MCP server

Add the Pocketsflow MCP server to Cursor’s MCP config at ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):

{
  "mcpServers": {
    "pocketsflow": {
      "url": "https://api.pocketsflow.com/mcp"
    }
  }
}

Reload Cursor (or toggle the server in Settings → MCP). When Cursor connects, your browser opens Pocketsflow: sign in and click Allow access. Pocketsflow creates a dedicated MCP: … API key for the connection; delete it under Developers → API keys to disconnect. Connect while your account is in test mode to keep the agent on sandbox data while you build. In Composer/Chat (Agent mode), Cursor lists the Pocketsflow tools and can run them — “list my products”, “create a checkout link for product X”, “show orders from the last 7 days”. Each call runs as your account.

Alternative: API key (headless / CI)

To skip the sign-in (for example in a headless or CI setup), create a key under Developers → API keys and send it as a header:

{
  "mcpServers": {
    "pocketsflow": {
      "url": "https://api.pocketsflow.com/mcp",
      "headers": {
        "Authorization": "Bearer pk_test_xxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

With the header variant, keep mcp.json out of version control — it contains your API key. Prefer a pk_test_… key, and never commit pk_live_… keys.

Add a project rule

Create a Cursor project rule so the editor follows Pocketsflow conventions when generating code. In your integration repo:

mkdir -p .cursor/rules

Create .cursor/rules/pocketsflow.mdc:

---
description: Building against the Pocketsflow API
alwaysApply: true
---

# Pocketsflow integration rules

- Base URL: https://api.pocketsflow.com
- Auth header: `Authorization: Bearer <API key>` (`pk_live_…` / `pk_test_…`).
- Secrets (API keys, webhook signing secrets) live in env vars — never in
  client-side code or the repo.

## Checkout
- Create a session with `POST /checkout/sessions` → `{ id, url }`.
- Redirect the buyer to `url`.
- Put our own order id in `metadata`; it is echoed back on the order and every
  related webhook — use it to reconcile.

## Webhooks
- Confirm payment from `order.completed`. Verify the `X-Pocketsflow-Signature`
  HMAC-SHA256 over the RAW request body before trusting the payload.
- Make handlers idempotent (an event may be re-sent).
- Return 2xx quickly; do heavy work asynchronously.

## References
- Docs: Integrations → Custom platforms, and API & Webhooks → Consuming webhooks.
- Interactive API reference: https://api.pocketsflow.com/docs

Add https://api.pocketsflow.com/docs.json (the OpenAPI spec) to Cursor’s Docs so it can search endpoint definitions while it codes. You can also use the Open in Cursor / Copy as Markdown action in the top-right of any docs page to hand a page in as context.

Typical workflow

Describe the integration

In Agent mode, ask Cursor to build the checkout + webhook flow, referencing the rule and docs.

Let it call the API via MCP

Have it create a test product and a checkout session in test mode to validate the request shape.

Test the webhook

Ask it to send a test event and confirm your handler verifies the signature and settles the order.

​Connect the Pocketsflow MCP server

​Alternative: API key (headless / CI)

​Add a project rule

​Typical workflow

​Related topics

Connect the Pocketsflow MCP server

Alternative: API key (headless / CI)

Add a project rule

Typical workflow

Related topics