概览
What is Finland Payments MCP?
A remote MCP server that lets any AI agent (Claude, ChatGPT, Cursor…) accept payments in Finland via Stripe’s hosted checkout. It is a stateless translation layer – funds flow directly from buyer to Stripe to merchant, and the server never holds funds, stores credentials, or uses a database.
How to use Finland Payments MCP?
Configure the MCP endpoint https://mcp-fi.wishpool.app/mcp and set the x-stripe-secret-key header to your Stripe secret key. Then call the create_payment_link tool to generate a EUR checkout link, or query_payment_status to check if a payment has been marked as paid.
Key features of Finland Payments MCP
- Remote MCP server, no local installation needed
- Stateless – no database or credential storage
- Accepts cards, Klarna, Apple Pay, Google Pay via Stripe
- Two tools:
create_payment_linkandquery_payment_status - Uses Streamable HTTP transport (JSON-RPC)
- Zero runtime dependencies; Node ≥ 18, MIT license
Use cases of Finland Payments MCP
- AI chatbot accepting one‑time payments in Finland
- Automated checkout generation for e‑commerce assistants
- Pull‑based payment status verification for order fulfilment
- Integrating Stripe payments into MCP‑compatible agents (Claude, ChatGPT, Cursor)
FAQ from Finland Payments MCP
What does Finland Payments MCP do versus alternatives?
It is a stateless translation layer – funds always flow buyer → Stripe → merchant directly. It never holds funds or stores credentials, and has no database.
What runtime dependencies are required?
Node.js ≥ 18. The server has zero runtime dependencies.
Where does payment data live?
Data is not stored by the server. Funds and transaction records reside entirely in Stripe and the merchant’s Stripe account.
What transport does the server use?
It uses Streamable HTTP with stateless JSON‑RPC.
How is authentication handled?
Authentication is via the x-stripe-secret-key header, which must contain a valid Stripe secret key (sk_test_ for test mode, sk_live_ for production).
