Stripe MCP Client

Created By
MattMorgisa year ago
A lightweight JavaScript client for interacting with Stripe's Model Context Protocol (MCP) server to create payment links.
Overview

What is Stripe MCP Client?

Stripe MCP Client is a lightweight JavaScript client designed for interacting with Stripe's Model Context Protocol (MCP) server, enabling users to create payment links easily.

How to use Stripe MCP Client?

To use the Stripe MCP Client, install it via npm and initialize it with your Stripe API key. You can then create payment links by calling the appropriate methods provided by the client.

Key features of Stripe MCP Client?

  • Simple API for creating Stripe payment links
  • Lightweight wrapper around the MCP client
  • Supports custom options and connected accounts
  • Automatic management of the MCP connection

Use cases of Stripe MCP Client?

  1. Creating payment links for e-commerce transactions.
  2. Integrating payment solutions within custom applications.
  3. Managing multiple payment links for different products or services.

FAQ from Stripe MCP Client?

  • Is the Stripe MCP Client free to use?

Yes! The Stripe MCP Client is open-source and free to use.

  • What are the prerequisites for using this client?

You need to have Node.js 16+ installed and a valid Stripe API key.

  • Can I use this client with my own MCP server?

Yes! The client is designed to be used within your own MCP server for seamless integration.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MattMorgis
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago