Stripe integration

What it gives Plexward

Revenue and subscription numbers for the entity, on the dashboard and in the weekly digest.
Payment and payout context when a question about a customer comes in.
A real number next to the spend number, which is the comparison that matters.

Layer

account. One Stripe connector per Claude account, scoped to the account you authorize. Per-entity scoping is the routing doc, or separate Stripe accounts.

{ "name": "Stripe", "layer": "claude.ai", "svc": "Revenue", "account": "Acme Stripe account" }

Prerequisites

A Stripe account for the entity, with a user who can grant access.
The connector attached on claude.ai.
A clear decision that this is read access. Nothing in a briefing needs to create a charge.

Setup steps

Attach the connector on claude.ai and complete the authorization.
Confirm from the brain: claude mcp list | grep -i stripe.
Declare it in catalog/declarations.json with the account in the account field.
Record in the brain which figures the entity cares about: monthly recurring revenue, net volume, active subscriptions. Different entities care about different ones and the agent should not have to guess.

Per-entity routing

## Owned Integrations
| MCP Tool | Service | Account | Notes |
|---|---|---|---|
| Stripe | Revenue | Acme Stripe | Account layer. Read only. Figures: MRR, net volume. |

## NOT This Company
- Stripe, in any entity that does not own this Stripe account.

If two entities each have a Stripe account, the account layer can only hold one of them at a time. That is a real limitation: the second entity needs either a separate Claude account or a scripted read with a restricted API key declared as a service layer entry.

Verify

cd ~/brains/acme-brain && claude mcp list | grep -i stripe

Expected ✔ Connected. Then read this month's volume and compare it with the Stripe dashboard.

Common failures

Silent expiry. This is one of the connectors most likely to be sitting in Needs authentication for weeks before anyone looks. The probe exists precisely for this.
Test mode versus live mode. Numbers that look plausible but tiny usually mean test mode.
Timezone and period boundaries. Stripe reports in the account's timezone. A "this month" that disagrees with the dashboard is usually this.
Multiple accounts under one login. Confirm which one you authorized.

What Plexward does with it once connected

The portfolio roll-up puts revenue next to agent spend per entity. The weekly digest carries the change since last week. Nothing writes.

Stripe