Polar MCP Server
Connect Polar to your AI agents with the Polar MCP server.
Updated
What is Polar MCP?
The Polar MCP server is a Model Context Protocol server that connects Polar to AI agents and assistants as a set of tools. With it connected, an agent can work with Polar (merchant-of-record billing — products, subscriptions, checkout, customer payments) directly — instead of you copying data in and out by hand.
It is a remote MCP server that uses a bearer token, so you point your client at the server URL, authorize once, and the Polar tools become available to the model.
Connect the Polar MCP server
Connect Polar MCP to Claude Code
- 1
Add the server
Use `claude mcp add` with the Polar MCP server URL (or its `npx` command), following the official docs.
- 2
Authorize
Complete authentication (a bearer token) so Claude Code can call the server.
- 3
Verify
Ask Claude to use a Polar tool to confirm the connection is live.
Connect Polar MCP to Cursor
- 1
Open MCP settings
In Cursor, go to Settings → MCP → Add new server.
- 2
Add Polar
Provide the Polar MCP server URL or command and complete authentication.
- 3
Test
Reference Polar from chat to confirm Cursor can reach the tools.
Sample use cases
An agent monitors new subscriptions and sends a personalized onboarding email to each customer
Faster subscriber activation without manual intervention.
A scheduled agent pulls daily revenue and MRR metrics from Polar and posts a summary to Slack
Real-time revenue visibility for the team without logging into a dashboard.
An agent creates checkout links for new products and adds them to a landing page automatically
Instant monetization of new offerings without developer involvement.
An agent detects failed subscription payments and triggers a dunning email sequence
Reduced involuntary churn through automated payment recovery.
A support agent looks up a customer's subscription status and recent payments during a help conversation
Faster support resolution with billing context available in real time.
An agent syncs Polar customer data with a CRM, creating or updating contact records on each purchase
Unified customer records across billing and sales systems.
An agent generates a monthly financial report from Polar transaction data and emails it to stakeholders
Consistent, automated financial reporting without spreadsheet work.
Using Polar MCP with Gamut
On Gamut, the Polar MCP server becomes a tool your agents use inside an automated, event-driven workflow — triggered by an event or a schedule, acting through Polar and your other connected MCP servers, with the connection managed by Gamut rather than a local config file.
Frequently asked questions
What billing operations can the Polar MCP server handle?
The server exposes tools for managing products, subscriptions, checkout sessions, customers, and payment data. Agents can create products, generate checkout links, look up subscription status, and pull revenue metrics.
Does the Polar MCP server support recurring billing workflows?
Yes. Agents can monitor subscription lifecycle events (new signups, renewals, cancellations, failed payments) and trigger automated responses like dunning emails or status updates.
Can I use the Polar MCP server to track revenue metrics?
Yes. The server provides access to transaction and subscription data that agents can aggregate into MRR, ARR, churn rate, and other revenue metrics for reporting.
Is the Polar MCP server suitable for production billing?
Polar is a merchant-of-record platform, so the MCP server operates on your live billing infrastructure. Use appropriate scoping and test environments when automating write operations like creating products or modifying subscriptions.