Polar.sh MCP for AI. Manage your entire monetization lifecycle from chat.

Listen up. Polar.sh handles your whole open-source monetization stack—the billing, the subscriptions, the product catalog—and it runs it all straight through your AI agent. You don't gotta switch apps or leave your terminal; you just tell your agent what to do in natural language and it executes the API calls for you.

Managing Your Product Catalog:
When you need to sell something, you start by creating it. You use create_product to register any new digital good. If an existing product needs a name change or a price tweak, you run update_product. To define what the customer actually gets, you create specific benefits using create_benefit, and if that benefit is scrapped, running delete_benefit removes it and revokes every associated user grant.

You can see all the perks customers buy into by checking list_benefits, or get the deep details on one perk using get_benefit. When you link a benefit to a product, you adjust those ties with update_product_benefits.

Handling Customers and Accounts:
Setting up users is simple. You use create_customer to add a new account to the billing system. Before a customer can do anything secure, your agent first generates a unique token using create_customer_session. To check on any user's current standing—what they’re subscribed to and what benefits they’ve got—you run get_customer_state.

For a full rundown of all registered accounts, you can pull a filterable list with list_customers. If you need to see every single benefit granted to one specific customer, list_portal_benefit_grants shows it. To check which license keys are out there for an account, run list_portal_license_keys. You can also view all historical orders tied to a single ID using list_portal_orders, or see every subscription record for that user with list_portal_subscriptions.

Subscriptions and Access Control:
If you want to give someone access, you use create_subscription, which initially restricts free product setups. To track what’s going on with a specific paid service, run get_subscription. If the customer loses their right to access, calling revoke_subscription instantly terminates their account privileges. You can also update an existing subscription record using update_subscription.

When you need to check if a license key is legit before giving access, use validate_portal_license_key. For general oversight of all paid services, list_subscriptions pulls the records, and checking recent user activity comes through list_checkouts, which gives you a summary list of attempted purchases.

Billing, Orders, and Funnel Analysis:
When it's time to get paid, your agent can initiate a purchase by running create_checkout, or modify details on an existing cart using update_checkout. Once the process is done, you check the status of that checkout with confirm_checkout_client or pull all data related to it using get_checkout.

To see a customer's past purchases, use get_order, and for a summary list of historical orders across the board, run list_orders, which lets you filter by date or status. When an order is finalized, running generate_invoice creates a professional invoice file for that specific order ID. You can also retrieve the raw data for any past billing with get_invoice.

If an order needs its details tweaked—say, the shipping address changed—you use update_order. For tracking how people drop off during checkout, you monitor list_checkouts. Finally, if your system sends automated updates to a custom endpoint, you first register that URL using create_webhook_endpoint, and then track the status of those messages with list_webhook_deliveries.