Finance and revenue

The Stripe connector.

Payments, customers, subscriptions. Connect once with your own key. Every agent your team runs reads the same 18 tools under one permission model.

How access is governed

18

Read tools

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

0

Write tools

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

0

Destructive tools

Stripe 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 Stripe tool

18 tools, named as the agent sees them.

  • list_customersread

    List customers from Stripe with optional filtering.

  • get_customerread

    Get a single customer by Stripe customer ID.

  • search_customersread

    Search customers using Stripe Search syntax. Examples: - By email: query: "email:'john@example.com'" - By name: query: "name~'John'" - By metadata: query: "metadata['plan']:'enterprise'"

  • list_subscriptionsread

    List subscriptions from Stripe with optional filtering.

  • get_subscriptionread

    Get a single subscription by Stripe subscription ID.

  • search_subscriptionsread

    Search subscriptions using Stripe Search syntax. Examples: - Active: query: "status:'active'" - By customer: query: "customer:'cus_xxx'" - Trialing: query: "status:'trialing'"

  • list_trialsread

    List subscriptions currently in trial period.

  • list_invoicesread

    List invoices from Stripe with optional filtering.

  • get_invoiceread

    Get a single invoice by Stripe invoice ID.

  • list_productsread

    List products from Stripe.

  • list_pricesread

    List prices from Stripe.

  • list_chargesread

    List charges (payments) from Stripe.

  • list_payment_intentsread

    List payment intents from Stripe.

  • get_balanceread

    Get the current Stripe account balance.

  • list_balance_transactionsread

    List balance transactions (money movement) from Stripe.

  • get_subscription_summaryread

    Get subscription metrics including MRR, active count, trials, and recent churn.

  • list_couponsread

    List coupons from Stripe.

  • list_eventsread

    List recent Stripe events (webhooks).

Use it from any agent

The same Stripe 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 Stripe Secret Key in your Stripe 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

Connect Stripe once. Use it everywhere.

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