What tools does Lfwin Payment Mcp provide?
It provides four MCP tools: `create_payment_order`, `query_payment_order`, `refund_payment_order`, and `query_refund_status`.
@litsen
LFWin Payment MCP Server 是一个面向 AI Agent 的支付能力服务,通过标准 MCP 协议,将创建支付订单、查询支付状态、发起退款、查询退款状态等能力开放给 Cursor、Cline、Claude Desktop、企业智能助手和自研 Agent 应用。
使用下面的配置,将此服务器添加到你的 MCP 客户端。
{
"mcpServers": {
"lfwin-payment-mcp": {
"command": "npx",
"args": [
"-y",
"@litsen/lfwin-payment-mcp"
]
}
}
}Create a cashier payment order. Amount is in yuan and merchant_order_no is the merchant's own unique order number. After success, display pay_qrcode_markdown, the returned image content block, pay_qrcode_image data URL, or pay_qrcode_base64 with pay_qrcode_mime_type as the QR code. If QR rendering fails, show pay_url/qrcode as the fallback payment link. Save order_no/query_order_no when present. If order_no is null, save merchant_order_no plus order_time and use both for query_payment_order polling.
Query payment order status. Prefer platform order_no/orderid when create_payment_order returned it. If order_no is null, pass merchant_order_no plus order_time returned by create_payment_order. Pass either order_no or the merchant pair.
Create a refund request by platform order_no/orderid. mch_refund_no is the merchant refund number and must be unique per refund. Successful submission means accepted/processing, not final refund success; call query_refund_status to confirm.
Query refund status by platform order_no/orderid. Pass mch_refund_no when available to locate a specific partial refund. Only REFUNDED is final success; REFUNDING/PROCESSING means query again later.
LFWin Payment MCP Server is a payment capability service for AI agents. It exposes payment order creation, status querying, refund initiation, and refund status querying via the standard MCP protocol to tools like Cursor, Cline, Claude Desktop, and custom agent applications.
Install the Node.js version via npx -y @litsen/lfwin-payment-mcp or the Python version via pip install git+https://github.com/litsen/lfwin-payment-mcp.git. Configure environment variables PAYMENT_API_KEY and PAYMENT_SIGN_KEY, then add a stdio MCP server entry in your client (Cursor, Cline, etc.) pointing to the appropriate command.
It provides four MCP tools: `create_payment_order`, `query_payment_order`, `refund_payment_order`, and `query_refund_status`.
Both implementations require `PAYMENT_API_KEY` and `PAYMENT_SIGN_KEY`. Obtain these from the service provider.
The server uses the `stdio` transport for local MCP services. Remote deployment requires adding authentication, tenant isolation, access control, and origin validation.
Yes. A Python version in `payment_mcp/` and a Node.js version in `node-mcp/`. They offer the same MCP tools; choose based on your environment.
Never commit `PAYMENT_API_KEY` or `PAYMENT_SIGN_KEY` to version control. Use environment variables, IDE secrets, or a secret management system.

Search a registry of agent skills and MCP servers, run them for real (sandbox or remote MCP, no install, a trace on every run), and hire proven agents for USDC.

Extract, search and tag any document — invoices, receipts, contracts, forms, or your own templates. 13 tools, one sign-in (OAuth 2.1) or API key, free FileTag tier, data residency in the EU, US, Israel or Asia.
Public docs + tool manifest for the GetIntel MCP connector (app.getintel.ai)
NetFoundry MCP Gateway enables secure, isolated access to Model Context Protocol (MCP) tools across distributed systems without exposing public endpoints. Zero trust gateway for MCP servers. Aggregate, filter, and secure

The AI marketing canvas for Claude and MCP agents. Your agent drafts campaigns as cards on a shared board, briefed by your brand rules, approved by you.
评论