pixl.directory
Stripe logo

Stripe

Interact with the Stripe API to manage payments, subscriptions, customers, and other financial operations through MCP tools.

Installation Instructions →

How to Use Model Context Protocol (MCP) in Cursor

What is MCP?

Model Context Protocol (MCP) is an open protocol that allows you to provide custom tools to agentic LLMs (Large Language Models) in Cursor's Composer feature.

Installation Steps

  1. Open Cursor Settings
    • Navigate to Cursor Settings > Features > MCP
    • Click the "+ Add New MCP Server" button
  2. Configure the Server
    • Name: Give your server a nickname
    • Type: Select the transport type (stdio or sse)
    • Command/URL: Enter either:
      • For SSE servers: The URL of the SSE endpoint
      • For stdio servers: A valid shell command to run the server

Example Configurations

For stdio Server (Stripe Example):

Command: node ~/mcp-quickstart/stripe-server/build/index.js --secret-key $STRIPE_SECRET_KEY --webhook-secret $STRIPE_WEBHOOK_SECRET

For SSE Server:

URL: https://api.stripe.com/v1/sse

Using MCP Tools

Tool Availability

  • • After adding a server, it will appear in your MCP servers list
  • • You may need to click the refresh button to populate the tool list

Using Tools in Composer

  • • The Composer Agent automatically uses MCP tools when relevant
  • • You can explicitly prompt tool usage by:
    • Referring to the tool by name
    • Describing the tool's function

Tool Execution Process

  • • Displays a message in chat requesting approval
  • • Shows tool call arguments (expandable)
  • • Executes the tool upon user approval
  • • Displays the tool's response in the chat

Important Notes

  • • MCP tools may not work with all models
  • • MCP tools are only available to the Agent in Composer
  • • For Stripe integration, you need to set up STRIPE_SECRET_KEY and STRIPE_WEBHOOK_SECRET environment variables
  • • Get your secret key from the Stripe Dashboard (API Keys section)
  • • Set up a webhook endpoint and get the signing secret from Stripe Dashboard
  • • For security, use a wrapper script that sets the environment variables before running the server
  • • Use test API keys for development and testing
  • • Be cautious with live mode API keys and sensitive customer data
  • • Consider implementing proper error handling for payment failures
  • • Monitor webhook events for important payment status updates
← Back to Home