Finance and revenue

The Paddle connector.

Subscriptions, transactions and customers. Connect once with your own key. Every agent your team runs reads the same 6 tools under one permission model.

How access is governed

6

Read tools

Open by default. They run when called, and every call is logged with the endpoint, tool and capability.

0

Write tools

Paddle exposes no write tools. Nothing it does mutates external state.

0

Destructive tools

Paddle defines no destructive tools. Nothing here deletes data.

Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.

Every Paddle tool

6 tools, named as the agent sees them.

  • list_subscriptionsread

    List subscriptions with their status, billing cycle, and next bill date. Filter by status to answer churn/dunning questions (e.g. status=past_due). The returned `id` feeds get_subscription; `customer_id` feeds list_customers and list_transactions.

  • get_subscriptionread

    Get one subscription in full, including its items, discount, scheduled change, and management URLs. Use the id from list_subscriptions. Read-only: this returns the cancel URL, it does not cancel anything.

  • list_transactionsread

    List billing transactions (invoices and charges), newest first. Bound it with billed_at/created_at — this list is long. Date filters take an operator suffix, e.g. billed_at="[GTE]2026-08-01T00:00:00Z". Filter by subscription_id or customer_id to trace one account's billing history.

  • list_customersread

    List or search customers by email, name, or id. Use search to resolve a person the user named in words into the ctm_ id that list_subscriptions and list_transactions filter on.

  • list_productsread

    List the product catalogue with each product's prices attached. Use this to see what a workspace actually sells and what each plan costs before interpreting subscription or transaction amounts.

  • list_pricesread

    List prices across the catalogue, optionally narrowed to one product. Each price carries its unit_price (amount as a string in the currency's smallest unit), billing cycle, and trial period. Get product_id from list_products.

Use it from any agent

The same Paddle tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.

.mcp.json · works for Cursor and Claude Desktop too
{
  "mcpServers": {
    "growth": {
      "type": "http",
      "url": "https://app.notara.ai/mcp/g/acme/growth",
      "headers": {
        "Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

The URL and token are placeholders. Real endpoints are issued per group from the dashboard.

Setup

  1. 01

    Create a Paddle API Key in your Paddle account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.

  2. 02

    Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.

  3. 03

    The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.

More in finance and revenue

StripeChartMogulCartaMercuryRamp

Connect Paddle once. Use it everywhere.

Use Notara directly, or bring us the workflow that needs to be redesigned and built.

Book a callSign in