Payment Gateway
Polar MCP connector
The Polar connector brings your Polar checkouts, checkout links, benefits, benefit grants, custom fields, customer meters and downloadables into Claude, ChatGPT, Cursor and any MCP client, so your team can ask about them and act on them under their own access.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Polar to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Polar once
-
Open Connections, choose Add connection, and pick Polar.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Polar API key. One person generates a token in Polar and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Polar to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Polar to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Polar to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Polar to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Polar through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Spin up a checkout link for a prospect
Create a Polar checkout link for a specific product or bundle while you are still on the call, and send it before the prospect has moved on. Pull the link back up later to check whether it has been used.
-
Support
Find out what a customer is entitled to
Look up a customer's benefit grants in Polar to confirm which license keys, downloads or Discord access they should have. Fetch the downloadable they are asking about instead of hunting for it in the dashboard.
-
Finance
Review checkouts from the past week
List recent Polar checkouts, see which ones completed and which stalled, and get a plain summary of what came through. Check a single checkout by its reference when a customer disputes a charge.
-
Product
Keep benefits current as the plan changes
Create a new Polar benefit when you launch a feature, update the description of an existing one, and list every benefit to confirm each tier is offering what the pricing page says.
-
Product
Check how much a customer has used
Read a customer meter in Polar to see how much of a metered allowance a customer has consumed this period, before you decide whether to reach out about an upgrade.
-
Operations
Add a question to the checkout form
Create or update a Polar custom field to collect a VAT number, company name or referral source at checkout, and list the existing fields so you do not add one twice.
Try asking
- “List active Polar subscriptions renewing in the next 14 days.”
- “Create a Polar checkout link for the annual Pro plan.”
- “Which Polar benefit grants were revoked last month?”
AI tools
Polar tools for your AI agents
136 tools are ready to call through Elaichi's MCP endpoint the moment you connect Polar, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Polar gets you
6 screens from the product, each doing one job for your Polar account.
The agent
Ask about Polar subscriptions in plain language.
The agent answers from live Polar checkouts, orders and benefit grants.
- checkouts
- subscriptions
- orders
- benefits
Ask Elaichi to work across your apps.
List active Polar subscriptions renewing in the next 14 days.
Create a Polar checkout link for the annual Pro plan.
Which Polar benefit grants were revoked last month?
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Polar together.
One org-wide MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
136 Polar tools are ready to call.
Benefits, checkout links, orders and subscriptions covered without writing custom code.
- Create a Polar benefit
- Delete a Polar benefit by ID
- Get single Polar benefit by ID
- List all Polar benefits
Toolboxes
Every team gets its own Polar toolbox.
Support sees orders and refunds, finance sees subscriptions, each toolbox scoped separately.
- Finance
- Support
- Growth
- Product
Shared connections
Teammates use Polar without seeing a key.
Each Polar connection shows who connected it and which teams share it.
- Core billing
- Growth experiments
- Support desk
- Finance ops
Audit log
Every Polar call is on the record.
When, who, what happened, type and resource, appended and never edited.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts your Polar revenue digest.
Orders are fetched, grouped, drafted by an agent, approved, then posted back to Polar.
Polar digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch checkouts
Polar
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Polar
Queued
Collections and dashboards
Polar checkout numbers arrive before you ask.
Four metrics, fourteen days of orders and a team breakdown, refreshed on schedule.
Polar health
Refreshed 4 minutes ago · every 15 minutes · from the checkouts collection
Checkouts
1,284 ↓ 12%
Subscriptions
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Checkouts created
Last 14 days
By team
Share of activity
Core billing 34%
Growth experiments 27%
Support desk 21%
Finance ops 18%
FAQ
Frequently asked questions
How do I connect Polar to Claude?
Connect Polar in Elaichi by pasting the API key from your Polar organization settings, then in Claude go to Customize, then Connectors, then Add, and enter https://api.elaichi.ai/mcp. There is no OAuth application to register in Polar and no client ID or secret to generate. Once Claude has the endpoint you sign in to Elaichi as yourself and Polar is available in the conversation.
Does Polar work with ChatGPT and Cursor as well as Claude?
Yes. Polar is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is added to Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. Nothing about the Polar connection changes from one client to the next.
What can an AI agent actually do with my Polar data?
With Polar connected, an agent can list and look up checkouts, create and manage checkout links, create, update and remove benefits, read benefit grants, manage the custom fields on your checkout form, read customer meters and fetch downloadables. In practice that means asking for last week's completed checkouts, creating a checkout link for a product, or confirming which benefits a customer has been granted. Polar has a large catalog of actions, so short concrete asks such as "list checkout links for the Pro plan" work better than long paragraphs.
Does connecting Polar give the AI everything in my Polar organization?
No. Access to Polar follows the API key of the person who connected it, so the agent can only see the Polar organization and records that key can already reach. Elaichi can narrow that further by hiding actions or whole groups of actions from a team, but it can never widen access beyond what Polar itself allows that key.
Can I stop an agent from deleting or changing things in Polar?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Polar checkouts and benefits while blocking the actions that delete a benefit, remove a checkout link or update a custom field. A blocked action is never shown to Claude, ChatGPT or any other client, so no prompt, however worded, can reach it.
What happens to a Polar connection when someone leaves?
When a person is offboarded in Elaichi their access to Polar through every client ends at once. If they had shared a Polar connection with a team, that connection keeps working for everyone else on the team. Disconnecting Polar once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Put Polar in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.