Skip to main content

Polar

Manage Polar products, customers, orders and subscriptions through Polar's MCP server.

Connect it with: MCP. Polar's own documentation: https://polar.sh/docs/integrate/mcp.

What agents can do​

Connect Polar so the agents working your tasks can reach it. With it connected, they can:

  • List products and prices, and create a product or checkout link for a launch.
  • Look up a customer's orders, subscriptions and license keys to answer a support question.
  • Report revenue metrics for a period.

Before you start​

  • A Polar organization (polar.sh) and a user who is a member of it.
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Polar​

Polar's MCP server signs you in itself, so connecting needs no key and no app of your own.

  1. In Jaah, open Secrets and select New.
  2. Search for Polar and select its card.
  3. Name the secret and choose who can use it (see Who can use it).
  4. Select Connect Polar, sign in to Polar in the window that opens, and approve the access it lists.
  5. You land back in Jaah on the new secret. Then link it to the projects whose agents should use it (see Use it in an agent session).

Connect with an API key​

Polar has no API key option in Jaah: connect with the sign-in above.

Use your own OAuth app​

Not needed: Polar's MCP server registers Jaah itself when you connect, so there is no app of your own to create.

Test the connection​

Select Test on the secret. Jaah makes one read-only call to Polar with the stored values and shows the result on the secret's page. Jaah also tests automatically when you save or reconnect.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A signed-in connection hands the agent a live access_token, with access_token_expires_at. Jaah refreshes it before it expires, so an agent never handles a refresh token.

Tell the agent in your task description which secret to use, for example “use the Polar secret org/polar”.

Polar also runs an MCP server, which gives agents ready-made Polar tools instead of raw API calls. A project's agents get those tools only once you link the secret to the project:

  1. Open the project and its MCP tab.
  2. Select Link, pick the Polar secret, and confirm.
  3. New tasks on the project start with the Polar tools. Tasks already running keep the tools they started with.

Jaah connects agents to the server through a local bridge, so the token never appears in the agent's configuration or its transcript. A Google Antigravity session in the terminal runtime runs without these tools; on ACP it gets them.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Reconnect: when Polar ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Polar's side too, revoke Jaah in Polar's settings.

Limitations​

  • At consent you choose the Polar organization and the scopes; agents reach only those.
  • This is Polar's production server: agents act on real customers and money. Polar's sandbox is not reachable from this card.
  • Agents can do only what the connected Polar account and its granted scopes allow.

Troubleshooting​

Test says Polar rejected the token (401)

The grant expired or was revoked under Polar's Settings > Developers. Select Reconnect.

An agent gets a permission error on writes

The consent was granted with read scopes only. Reconnect and approve the write scopes the work needs.

The secret shows Needs reconnect

Polar ended the grant (a password change, a revoked connection or a long idle period). Select Reconnect on the secret and sign in to Polar again.

New tasks on the project have no Polar tools

Link the secret on the project's MCP tab, then start a new task. Tasks already running keep the tools they started with, and an agent marked Not supported on that tab cannot load MCP servers.

Still stuck? Select Test and read the result: it names the value Polar refused and the status it answered.

FAQ​

Does Jaah need an app registered at Polar?

No. Jaah registers itself with Polar's sign-in server the first time anyone connects, and every later connection reuses that registration.

What does Test do?

It opens an MCP session with Polar's server and lists its tools, then closes the session. It reads and changes nothing in your Polar account.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one Polar account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.