Polar MCP integration for AI agents.
Connect AI agents to Polar through 13 structured actions, including get customer, get customer by external id, and get customer state. Review authentication…
- ACTION CONTRACTS
- 13
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Polar integration exposes
The Polar Agent App exposes 13 provider-backed actions for finance and developer tools work. Its current contract lets an authorized agent get a polar customer by id, get a polar customer by external id, and get a polar customer state by customer id, including subscriptions and benefits. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Polar account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Polar capabilities.
Showing 12 of 13 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_customerREADGet a Polar customer by ID.
INPUTS: id
get_customer_by_external_idREADGet a Polar customer by external ID.
INPUTS: external_id
get_customer_stateREADGet a Polar customer state by customer ID, including subscriptions and benefits.
INPUTS: id
get_customer_state_by_external_idREADGet a Polar customer state by external customer ID, including subscriptions and benefits.
INPUTS: external_id
get_orderREADGet a Polar order by ID.
INPUTS: id
get_organizationREADGet a Polar organization by ID.
INPUTS: id
get_productREADGet a Polar product by ID.
INPUTS: id
get_subscriptionREADGet a Polar subscription by ID.
INPUTS: id
list_customersREADList Polar customers with optional organization, email, search, activity, and metadata filters.
INPUTS: organization_id / email / query / active / page
list_ordersREADList Polar orders with optional organization, product, customer, checkout, subscription, and metadata filters.
INPUTS: organization_id / product_id / product_billing_type / discount_id / customer_id
list_organizationsREADList Polar organizations accessible to the Organization Access Token.
INPUTS: slug / page / limit / sorting
list_productsREADList Polar products with optional organization, name, visibility, and metadata filters.
INPUTS: id / organization_id / query / is_archived / is_recurring
INPUT CONTRACTS
Know what the action needs before it runs.
get_customer
idOPTIONAL- The Polar resource ID.
get_customer_by_external_id
external_idOPTIONAL- The Polar customer external ID.
get_customer_state
idOPTIONAL- The Polar resource ID.
get_customer_state_by_external_id
external_idOPTIONAL- The Polar customer external ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Customer
Get a Polar customer by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_customerVerify with Get Customer By External Id
Get a Polar customer by external ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_customer_by_external_idSAFETY BOUNDARY
Operate Polar with explicit limits
- Authorize Polar with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Polar data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Polar rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Polar task completed successfully.
CONNECTION MODEL
API key
Polar Organization Access Token sent as a Bearer token. Create OATs in your Polar organization settings: https://polar.sh/docs/api-reference/introduction#authentication.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 13
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Polar.