Stripe (local) logo

Stripe (local)

Beta

Works with Stripe through the Stripe API. With a live-mode key it acts on real customers, charges and refunds.

  • Local
Runs
On the developer's Mac
Launched with
Docker
Platform
macOS
Publisher
Docker

How it works

Every agent request passes through Ferentin policy before it reaches Stripe (local).

It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with docker run -i --rm mcp/stripe.

Ferentin's endpoint agent finds Stripe (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.

  1. AI agentAsks for something
  2. Ferentin policies
  3. Stripe (local) MCP serverRuns on the developer's Mac
  4. Governed resultChecked, logged, returned

About Stripe (local)

Works with Stripe through the Stripe API. With a live-mode key it acts on real customers, charges and refunds.

Frequently asked about Stripe (local)

How do I connect Stripe (local) to Ferentin?
Enroll your Macs with the Ferentin endpoint agent, then add Stripe (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
Is the Stripe (local) integration generally available?
The Stripe (local) integration is currently beta on Ferentin.