Skip to directory

About Polar MCP

Polar's hosted MCP lets an AI client search, inspect, and execute operations across a connected Polar billing organization through three discovery/execution meta-tools.

What you can use it for

  • Inspect Polar products, customers, subscriptions, orders, benefits, refunds, and billing metrics
  • Find relevant operations on demand without loading a large fixed tool catalog
  • Execute validated billing operations after reviewing their schema
Connection and setup
Hosting
Remote, vendor-hosted
Transport
Streamable HTTP
Endpoint
https://mcp.polar.sh/mcp/polar-mcp
Authentication
OAuth sign-in to a Polar organization; no API key is pasted into the client setup. Access is governed by the authenticated organization/account.

Requirements

  • Polar account and organization
  • MCP client supporting remote Streamable HTTP and OAuth
  • Organization permissions for the billing operations requested

Setup steps

  1. Add https://mcp.polar.sh/mcp/polar-mcp to an OAuth-capable MCP client.
  2. Complete Polar sign-in and select/authorize the intended organization when prompted.
  3. Verify with a read-only operation: call search_tools for a query, describe the returned operation, and inspect its arguments before execution.
  4. For writes such as refunds, subscription changes, or customer actions, summarize exact target and consequences and obtain the user's explicit confirmation before execute_tool.
Tools 3

Three MCP meta-tools are documented: search_tools, describe_tools and execute_tool. They dynamically discover/execute an underlying catalog of about 100 operations; underlying operation availability is dynamic.

  • search_tools

    Search the operation catalog by describing the task; returns matching operations.

    01
  • describe_tools

    Load detailed definitions and input requirements for selected operations.

    02
  • execute_tool

    Execute an operation with validated arguments; can perform changes to billing/customer data.

    03
Limitations and notes
  • Underlying operations can modify billing/customer state; execution must be reviewed carefully.
  • Available operations and access depend on the authorized Polar organization.
  • The service is remote OAuth; local package or static API key setup is not the documented ordinary user setup.
  • The listing calls this entry ?Polar.sh Sandbox,? but the official integration page describes the general hosted Polar MCP endpoint and does not identify a separate sandbox MCP service.
Source discrepancies
  • Discovery name includes ?Sandbox,? but the vendor page documents a single Polar MCP endpoint and does not establish a separate sandbox server. Treat it as the standard Polar hosted MCP; sandbox environment behavior remains unknown.
Original sources
  • official tool reference

    Polar exposes three meta-tools: search_tools, describe_tools, execute_tool. They dynamically discover and execute roughly 100 underlying operations; this count describes the MCP meta-tool surface, not all operations.

  • official documentation or source

    Polar exposes three meta-tools: search_tools, describe_tools, execute_tool. They dynamically discover and execute roughly 100 underlying operations; this count describes the MCP meta-tool surface, not all operations.

Documentation checked 2026-10-28T12:53:18.000Z. Connection has not been runtime tested.

Similar tools