@layers/amba-mcp 4.0.5 → 4.0.6

package/dist/tools/monetization.d.ts

@@ -0,0 +1,20 @@
+/**
+ * Monetization control-plane tools (Phase 1 — read-only against RevenueCat).
+ *
+ * These let an agent reason about a project's subscription monetization as
+ * Infrastructure-as-Code: preview the gap between the declared config and
+ * what's live (plan), see what changed out-of-band (drift), snapshot the live
+ * config into a declarative bundle (export), adopt the live config as the
+ * managed baseline (adopt), and inspect the current declared definitions.
+ *
+ * Phase 1 is READ-ONLY against the upstream subscription provider: plan / drift
+ * / export only read; adopt writes Amba's own state (definitions + statefile),
+ * never the provider. Provisioning ("apply" — pushing declared changes back to
+ * the provider) is a later phase; these tools deliberately don't claim it.
+ *
+ * RevenueCat may be named here — it's a developer-chosen integration the
+ * developer configured themselves, not an Amba implementation detail.
+ */
+import type { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
+import type { ApiClient } from '../api-client.js';
+export declare function registerTools(server: McpServer, apiClient: ApiClient): void;

package/dist/tools/payments.d.ts

@@ -0,0 +1,30 @@
+/**
+ * Amba Payments — Stripe Connect platform tools (tracker #10).
+ *
+ * Amba is the payments rail for the developer's app: the app is the seller,
+ * Amba takes a platform fee, Stripe carries money-transmission. These are
+ * the DEVELOPER-facing onboarding + configuration + reporting tools — the
+ * developer knowingly connects a Stripe account, so "Stripe" is named here
+ * (same posture as the existing developer-billing surface). The end-customer
+ * (app-user) payment surface lives in the SDK and stays neutral.
+ *
+ * Tools:
+ *   - amba_payments_account_create  — create the project's connected account
+ *   - amba_payments_create_onboarding_link — hosted onboarding URL (copy box)
+ *   - amba_payments_account_status  — onboarding + capability flags
+ *   - amba_payments_set_fee         — set the default platform fee (basis points)
+ *   - amba_payments_charge          — destination charge with application fee
+ *   - amba_payments_balance         — connected-account balance
+ *   - amba_payments_payouts         — connected-account payouts
+ *
+ * Backend routes: POST/GET/PUT /v1/admin/projects/:id/payments/*. All live
+ * Stripe calls are gated by the platform's PAYMENTS_CONNECT_LIVE
+ * kill-switch — when off, the tools surface a clear PAYMENTS_NOT_ENABLED
+ * error via the standard AmbaApiError path (the platform owner enables it).
+ *
+ * No vendor leakage on the END-CUSTOMER surface; here, naming Stripe is by
+ * intent in the developer onboarding context.
+ */
+import type { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
+import type { ApiClient } from '../api-client.js';
+export declare function registerTools(server: McpServer, apiClient: ApiClient): void;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@layers/amba-mcp",
-  "version": "4.0.5",
+  "version": "4.0.6",
   "license": "Apache-2.0",
   "engines": {
     "node": ">=22"
@@ -26,7 +26,7 @@
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.12.1",
     "zod": "^3.25.0",
-    "@layers/amba-shared": "4.0.3"
+    "@layers/amba-shared": "4.0.4"
   },
   "devDependencies": {
     "@types/node": "^22.10.2",