Skip to content
Nappai Documentation

Stripe MCP

Stripe MCP is a quick way to talk to Stripe from your Nappai dashboard.
You only need to give it your Stripe API key and pick the action you want to perform. The component then talks to Stripe’s servers and returns the result, which you can feed into other parts of your workflow.

How it Works

Stripe MCP uses your Stripe API key to authenticate with Stripe’s public API.
When you choose a tool (for example, “Create Charge” or “Retrieve Customer”), the component sends a request to Stripe’s servers with the data you provide.
Stripe processes the request and sends back a response (usually in JSON).
Stripe MCP simply passes that response along to the next component in your workflow.

Inputs

  • API Key: Your secret Stripe API key. This key lets Stripe know who you are and gives you permission to perform actions.
  • Tool: A dropdown list of available Stripe actions. Pick the one you want to run, such as “Create Charge” or “Retrieve Customer”.

Outputs

The component outputs the raw response from Stripe.
This is usually a JSON object that contains details about the action you performed (e.g., the charge ID, status, or customer information).
You can use this output to feed into other components, log the result, or display it to users.

Usage Example

  1. Add the Stripe MCP component to your workflow.
  2. Enter your Stripe API Key in the “API Key” field.
  3. Select a Tool from the dropdown, e.g., “Create Charge”.
  4. Connect the output of Stripe MCP to the next component (e.g., a “Log” component or a “Send Email” component).
  5. Run the workflow. The component will create the charge in Stripe and pass the response forward.
  • Stripe Payment Intent – Create a payment intent for a checkout flow.
  • Stripe Customer – Manage customer records in Stripe.
  • Stripe Invoice – Generate and send invoices.
  • Stripe Webhook Listener – Receive real‑time events from Stripe.

Tips and Best Practices

  • Keep your API key hidden: store it in Nappai’s secure secrets storage instead of typing it directly.
  • Test in Stripe’s sandbox (test mode) before going live.
  • Use the “Tool” dropdown to explore all available actions; the documentation for each tool will show required fields.
  • If you need to pass dynamic data (like an amount or customer ID), connect those values from previous components instead of hard‑coding them.

Security Considerations

  • Treat the API Key as a password. Never expose it in logs or public dashboards.
  • Use environment variables or Nappai’s secret management to store the key.
  • Restrict the key’s permissions in Stripe to only the actions you need (e.g., read‑only or limited write).
  • Regularly rotate the key and update it in Nappai to reduce the risk of compromise.