Setup Polar

Interactive onboarding wizard to set up Polar payment integration from scratch — authentication, product creation, and framework-specific…

You say
Buy it · $15 Read it before you buy $15 Written by polarsource · unverified publisher
Context cost
1.1k tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 4.5 kBtext throughout, nothing executable
Licence
MITpaid listing
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

Interactive onboarding wizard to set up Polar payment integration from scratch. Use this skill when: (1) User wants to "set up Polar" or "integrate Polar" in their project; (2) User is starting fresh with Polar and needs guided setup; (3) User asks "how do I get started with Polar"; (4) User wants to add payments/subscriptions/checkout to their app using Polar; (5) User needs help creating their first Polar product and checkout. This skill walks through MCP installation, authentication, product creation, and generates framework-specific integration code.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

polaronboardingpaymentssubscriptions

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md4.5 kB · 137 lines
--- name: setup-polar description: | Interactive onboarding wizard to set up Polar payment integration from scratch. Use this skill when: (1) User wants to "set up Polar" or "integrate Polar" in their project; (2) User is starting fresh with Polar and needs guided setup; (3) User asks "how do I get started with Polar"; (4) User wants to add payments/subscriptions/checkout to their app using Polar; (5) User needs help creating their first Polar product and checkout. This skill walks through MCP installation, authentication, product creation, and generates framework-specific integration code. ---
7# Polar Setup Wizard
8
9Interactive setup guide to get Polar payments working in your project.
10
11## Setup Flow
12
13Follow these steps in order:
14
15### Step 1: Check MCP Availability
16
17First, check if the Polar MCP server is available. Try listing products or organizations using MCP tools.
18
19**If MCP tools work:** Skip to Step 3.
20
21**If MCP not available:** Continue to Step 2.
22
23### Step 2: Install Polar MCP
24
25Guide the user to install the Polar MCP server based on their environment:
26
27**Claude Code:**
28```bash
29# Production
30claude mcp add --transport http "Polar" "https://mcp.polar.sh/mcp/polar-mcp"
31
32# Sandbox (recommended for setup)
33claude mcp add --transport http "Polar Sandbox" "https://mcp.polar.sh/mcp/polar-sandbox"
34```
35
36**Cursor** (.cursor/mcp.json):
37```json
38{
39 "mcpServers": {
40 "Polar Sandbox": {
41 "url": "https://mcp.polar.sh/mcp/polar-sandbox"
42 }
43 }
44}
45```
46
47After installation, the user must:
481. Restart their editor/CLI
492. Authenticate when prompted (redirects to polar.sh)
50
51Once authenticated, verify MCP works by listing organizations.
52
53### Step 3: Gather Project Context
54
55Ask the user:
56
571. **Framework**: What framework are you using?
58 - Next.js (App Router)
59 - Next.js (Pages Router)
60 - Express.js
61 - FastAPI (Python)
62 - Other
63
642. **Environment**: Start with sandbox or production?
65 - Sandbox (recommended for new setups)
66 - Production
67
683. **Product type**: What are you selling?
69 - Subscription (recurring)
70 - One-time purchase
71 - Both
72
73### Step 4: Create Organization (if needed)
74
75Use MCP to check if user has an organization. If not, guide them to create one at:
76- Sandbox: https://sandbox.polar.sh/start
77- Production: https://polar.sh/start
78
79### Step 5: Create First Product
80
81Use MCP to create a test product. Example for subscription:
82
83```
84Create a product with:
85- Name: "Pro Plan"
86- Monthly price: $29
87- Organization: [user's org]
88```
89
90Store the returned product ID for checkout integration.
91
92### Step 6: Generate Integration Code
93
94Hand off to the polar-integration skill to generate the Checkout, Customer Portal, and Webhooks endpoints for the framework selected in Step 3. That skill has the canonical, framework-agnostic recipes plus per-framework variations.
95
96Before invoking it, make sure the user has these environment variables ready (use whatever loader their framework provides):
97
98```bash
99POLAR_ACCESS_TOKEN= # from polar.sh/settings (or sandbox)
100POLAR_WEBHOOK_SECRET= # created in Step 7
101POLAR_SERVER=sandbox # omit or set to "production" when going live
102```
103
104Pass along the product ID from Step 5 so checkout links can be tested in Step 8.
105
106### Step 7: Set Up Webhooks
107
1081. Start the local development server.
1092. Start ngrok against the dev server's port:
110 ```bash
111 ngrok http <port>
112 ```
1133. Copy the ngrok URL (e.g., https://abc123.ngrok.io).
114
115Use MCP to create a webhook endpoint, or guide the user to the dashboard:
116- Sandbox: https://sandbox.polar.sh → Settings → Webhooks
117- Add endpoint: https://[ngrok-url]/<webhook-path> (use the path from the route generated in Step 6).
118- Select events: order.paid, subscription.created, subscription.canceled.
119- Copy the webhook secret into the env var loader from Step 6.
120
121### Step 8: Test the Integration
122
1231. Start the dev server.
1242. Visit the checkout URL with the product ID from Step 5 (path and query shape come from the route generated in Step 6).
1253. Complete checkout using test card: 4242 4242 4242 4242.
1264. Verify the webhook was received in terminal logs.
1275. Check the success page displays correctly.
128
129### Step 9: Next Steps
130
131Once basic setup works, suggest:
132
1331. **Add customer portal** - Let users manage subscriptions (Recipe 2 in polar-integration).
1342. **Link to your auth** - Pass externalCustomerId in checkout.
1353. **Add benefits** - License keys, file downloads, Discord roles.
1364. **Go production** - Switch POLAR_SERVER from sandbox to production.
137
In the file
SKILL.md667 words
Files1
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈150
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
975
on trigger
The instruction body, read only when the skill fires.
0.56%
of a 200k window
Ten skills this size would take about 6% of the window before you open a file.
050k100k150k200k context window

1.1k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Small enough to keep loaded permanently without thinking about it.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 4.5 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md4.5 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$15 once
Setup Polar · MIT · polarsource
one-time
Price$15 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery update its author ships, delivered through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
Price$15
Referencepolarsource/setup-polar

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

PO
polarsource

Publishes on mcprush.

0 servers listed2 skills listednot claimed
Profile
Publisher
Servers0