Skip to directory

Polar MCP Server (Production)

Polar

Transport not documented3 documented tools1

About Polar MCP Server (Production)

Polar's hosted MCP server lets AI clients inspect and manage a Polar organization's products, customers, subscriptions, orders, benefits, and related billing operations through OAuth.

What you can use it for

  • Inspect products, customers, subscriptions, orders, benefits, refunds, and billing metrics
  • Create or update Polar commerce records and manage subscriptions or benefits
Connection and setup
Hosting
remote
Transport
Not documented
Endpoint
https://mcp.polar.sh/mcp/polar-mcp
Authentication
OAuth browser sign-in and organization consent; the documented connection does not require an API key in the AI client. A separate sandbox endpoint is https://mcp.polar.sh/mcp/polar-sandbox.

Requirements

  • Polar account and access to the target organization
  • MCP client that supports remote Streamable HTTP and OAuth, or documented mcp-remote bridge

Setup steps

  1. Add https://mcp.polar.sh/mcp/polar-mcp as a remote MCP server in the selected client.
  2. Initiate connection and complete Polar OAuth in the browser, selecting/authorizing the intended organization.
  3. For Codex CLI, the documented command is codex mcp add polar --url https://mcp.polar.sh/mcp/polar-mcp.
  4. Use https://mcp.polar.sh/mcp/polar-sandbox for development/testing and give it a distinct server name.
  5. Verify using search_tools and describe_tools for a read-only lookup before executing any write operation.
Tools 3

The fixed MCP surface is three meta-tools; the approximately 100 underlying Polar operations are dynamically discovered and are not independent MCP tools.

  • search_tools

    Search Polar’s available operations for ones relevant to a requested task.

    01
  • describe_tools

    Retrieve descriptions and input schemas for selected Polar operations.

    02
  • execute_tool

    Execute a selected Polar operation with supplied arguments.

    03
Limitations and notes
  • This is a live organization connection. Operations may create, update, refund, delete, or revoke access; review proposed changes before execution.
  • Dynamic operations and schemas are discovered on demand, so the three meta-tool list is not the full underlying operation catalog.
  • An MCP client must support remote HTTP OAuth, or use a documented local bridge.
  • The publisher distinguishes production and sandbox endpoints.
  • No runtime connection test performed.
Original sources
  • official documentation

    Current Polar documentation identifies exactly three exposed meta-tools: search_tools, describe_tools, and execute_tool. About 100 business operations are discovered dynamically behind these tools and are not separate fixed MCP tool names. The hosted production endpoint and OAuth setup are documented.

  • official tool reference

    Current Polar documentation identifies exactly three exposed meta-tools: search_tools, describe_tools, and execute_tool. About 100 business operations are discovered dynamically behind these tools and are not separate fixed MCP tool names. The hosted production endpoint and OAuth setup are documented.

Documentation checked 2026-10-28T13:19:36Z. Connection has not been runtime tested.

Similar tools