Direct answer: Finta's Aurora catalog includes Stripe's remote MCP server at https://mcp.stripe.com. Stripe documents public-preview tools for supported account, balance, customer, invoice, payment-link, payment, product, price, subscription, refund, dispute, and documentation tasks, separated between sandbox and live mode.
This guide is for teams using Finta as relationship intelligence around a capital, investor, customer, or company-building workflow. Stripe remains the source system for its records. Aurora can use only the context and actions exposed to the connected account.
How the Stripe connection works
| Connection detail | Current Finta guidance |
|---|---|
| Classification | Catalog MCP |
| Configured endpoint | https://mcp.stripe.com |
| Authentication and transport | Provider OAuth through Aurora; Streamable HTTP |
| Source of truth | Stripe remains authoritative for provider records, permissions, and action results. |
| Human control | Review external communication, record changes, financial actions, publishing, deletion, and other consequential work before execution. |
What you can use it for
- Read supported Stripe account, balance, customer, invoice, payment, and subscription context.
- Search Stripe documentation through the provider's documented tool.
- Prepare supported invoices, payment links, products, prices, refunds, or subscription actions for review.
- Use Stripe's sandbox mode to validate a workflow before any live financial action.
- Keep live access limited to the authenticated account and approved Stripe permissions.
These uses summarize the current provider documentation and Finta catalog purpose. The exact tool inventory varies by provider version, plan, workspace, user permissions, region, and authorization scopes.
Relationship intelligence workflows for Stripe
Prepare operating metrics for a board review
Outcome: Have finance approve the source-linked summary before it is shared.
- Define the Stripe account, date range, currency, and metric questions.
- Retrieve the relevant balance, invoice, customer, payment, or subscription records.
- Document exclusions, refunds, disputes, and data gaps.
- Have finance approve the source-linked summary before it is shared.
Human decision: Stripe data may support operating analysis but is not audited financial reporting and should not be used without finance review.
Create a paid-program checkout after approval
Outcome: Verify the resulting Stripe object before sharing it.
- Confirm the approved product, price, customer terms, currency, and tax treatment.
- Test the intended payment-link or invoice workflow in Stripe sandbox.
- Ask the responsible operator to approve the live action.
- Verify the resulting Stripe object before sharing it.
Human decision: Do not use this workflow for investor subscriptions, securities transactions, or any capital-raising payment without qualified legal and financial review.
How to connect Stripe to Aurora
- Ask a Stripe administrator to confirm MCP access is enabled for the intended account.
- In Aurora, open Apps and select Stripe.
- Authorize https://mcp.stripe.com and explicitly confirm sandbox or live mode.
- Review the requested permissions and begin with sandbox and read-oriented tools.
- Run a safe account or documentation lookup before any financial write.
Open the official Finta apps directory to confirm the catalog entry before authorizing a provider account.
Permissions and approval boundary
Use sandbox first and least privilege in live mode. Require explicit human confirmation for invoices, payment links, refunds, disputes, subscriptions, prices, customers, or any other financial mutation. Stripe is not a substitute for accounting, legal, tax, securities, or investment advice.
Limitations to understand
- Stripe MCP is in public preview and tools, scopes, and access controls can change.
- Sandbox and live mode are separate and must be clearly identified in every test.
- The MCP toolset does not cover every Stripe product or accounting requirement.
- Stripe operating data does not by itself establish audited revenue, cash, or financial performance.
Verification checklist
- Confirm account admin enablement, endpoint, OAuth, account ID, and sandbox or live mode.
- Capture the granted permissions and exact tool inventory.
- Run a safe sandbox read and retain the receipt.
- Test one sandbox write after approval, verify the resulting object, and avoid live mutation during page QA.
- Record preview status, unsupported products, financial disclosure, and verification date.
Verification status: On 2026-08-22, Finta confirmed that this connector appears in the enabled production Aurora catalog and reviewed the configured endpoint, authentication type, and first-party sources listed below. This is not a claim that every provider tool or an authenticated end-to-end action has been tested for every account.