Pocketsflow MCP Setup for Gemini CLI and AI Studio

You connect Gemini to Pocketsflow through Gemini CLI: run gemini mcp add --transport http pocketsflow with the server URL https://www.pocketsflow.com/mcp, then type /mcp auth pocketsflow, sign in to Pocketsflow and click Allow access. Gemini CLI is the Google client Pocketsflow supports for MCP, and Google AI Studio is where you get the Gemini API key that Gemini CLI can run on.

Who can use Gemini CLI with Pocketsflow today

Check your Google access before you set up Pocketsflow in Gemini CLI. Google changed who Gemini CLI serves on June 18, 2026. As of November 1, 2026, Google's Gemini CLI page says it works with:

• Gemini Code Assist Standard or Enterprise licenses
• Code Assist for GitHub on Google Cloud
• Paid Gemini API keys and Vertex AI keys

Free individual accounts and Google AI Pro and Ultra subscribers moved to Google's Antigravity CLI. This guide covers Gemini CLI, the client Pocketsflow documents. If you have none of the access above, Claude's free plan is the simpler way in: it allows one custom connector, which is all Pocketsflow needs. See how to connect Pocketsflow to Claude.

Where Google AI Studio fits with Pocketsflow

Google AI Studio is not where you add Pocketsflow. Custom MCP servers, Pocketsflow included, connect through Gemini CLI. AI Studio's part is the key: at aistudio.google.com/apikey you create a Gemini API key, and Gemini CLI runs on it when you set GEMINI_API_KEY. That key pays for Gemini. It has nothing to do with your Pocketsflow account.

The Gemini web app works differently. On the Pocketsflow MCP page, the Gemini button copies the setup prompt and opens gemini.google.com, so Gemini can walk you through the Gemini CLI steps. Google's Gemini API docs also describe remote MCP servers for developers who call the API in code. Pocketsflow has no guide for that route yet, so this post sticks to Gemini CLI.

How to connect Gemini CLI to Pocketsflow

1. Install Gemini CLI with npm install -g @google/gemini-cli and sign in with one of the Google options above.
2. In the Pocketsflow dashboard, switch to test mode if you want to practice first. The connection takes the mode the dashboard is in when you click Allow.
3. Add the server. The -s user flag saves it for every folder; without it, Gemini CLI saves it only for the current project:

   gemini mcp add -s user --transport http pocketsflow https://www.pocketsflow.com/mcp

4. Start gemini and type /mcp auth pocketsflow. Your browser opens Pocketsflow. Sign in and click Allow access.
5. Type /mcp. Pocketsflow should show as connected, with its tools listed.
6. Ask Gemini in plain words.

No Pocketsflow API key changes hands in this flow. Pocketsflow creates a key named "MCP: <app>" for the connection. Delete it under Developers, then API keys, to disconnect Gemini CLI.

Pocketsflow prompts to paste into Gemini

Each prompt below comes from the Pocketsflow MCP page, with the tools Gemini calls to answer it. Gemini CLI asks before each tool call unless you mark the server as trusted. Leave that check on, so you see each change before it lands in your Pocketsflow store.

• "Create a $29 presets pack and give me the checkout link." (create_product, create_checkout_session)
• "How did sales go this week, and who are my top customers?" (list_orders, list_customers)
• "How much can I withdraw, and did my last payout land?" (get_payout_balance, list_payouts)
• "Write a newsletter about my spring sale and send it." (create_post, send_post)
• "Make SPRING20: 20% off everything until Sunday." (create_discount)

Gemini can reach all 303 Pocketsflow tools. The chart shows how many sit behind the jobs a seller asks about most.

Products has 6 tools, Orders has 6 and Memberships has 17. Payouts has 4, and all of them only read.

Gemini CLI and Pocketsflow without a browser

Gemini CLI can also run Pocketsflow jobs in a script. A script has no browser for the sign in, so it sends a Pocketsflow API key as a header instead. Create a pk_test_ key under Developers, then API keys, while in test mode. This command adds the server with the key and limits it to five read tools:

gemini mcp add -s user --transport http \
  -H "Authorization: Bearer pk_test_xxxxxxxx" \
  --include-tools list_orders,get_order,get_payout_balance,list_payouts,get_analytics_summary \
  pocketsflow https://www.pocketsflow.com/mcp

Then run a prompt with gemini -p, for example: gemini -p "Summarize yesterday's Pocketsflow orders". Keep these rules:

• The command writes the key into a Gemini settings file. Use -s user so it lands in your home folder, not in a project you might commit.
• A Pocketsflow API key can call every tool. The --include-tools list is what keeps this script on reads.
• Use one key per script, so you can delete one without breaking the others. To rotate, create a new key, update the command, then delete the old key.

What stays in the Pocketsflow dashboard

Pocketsflow keeps money movement out of Gemini. Refunding a payment, withdrawing a payout and changing bank details happen only in the Pocketsflow dashboard. Gemini can read payouts but not move them, and Pocketsflow's refund tools set your refund policy, not refunds. Selling on Pocketsflow has no monthly fee; see Pocketsflow pricing.

More on Pocketsflow MCP

For every tool group, read what Pocketsflow MCP can do. The setup for every other app is on the Pocketsflow MCP page.