Pine Labs Payment Gateway MCP Server (Official)
MCP client for Pine Labs payment gateway -- connect Claude Desktop, Cursor, VS Code, and other AI assistants to Pine Labs payment APIs using your client credentials.
Power your agent
URL ของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
https://mcp.pinelabs.com/mcpปุ่ม Claude ด้านบนจะเปิด Claude พร้อมกรอกชื่อและ URL ให้แล้ว คุณยังต้องยืนยันที่นั่นเอง
claude mcp add --transport http io.github.plural-pinelabs-pinelabs-online-mcp https://mcp.pinelabs.com/mcpRun in a terminal.
{ "mcpServers": { "io.github.plural-pinelabs-pinelabs-online-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.pinelabs.com/mcp" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
MCP client for Pine Labs payment gateway -- connect Claude Desktop, Cursor, VS Code, and other AI assistants to Pine Labs payment APIs using your client credentials.
Create payment orders, checkout, subscriptions & UPI via PineLabs Plural PG gateway
# 1. Configure your credentials
npx pinelabs-mcp configure --client-id=YOUR_ID --client-secret=YOUR_SECRET
# 2. Test your connection
npx pinelabs-mcp test
# 3. Auto-configure your AI client
npx pinelabs-mcp setup cursor # or: claude-desktop, vscode, windsurf, opencode, copilot, codex
Then restart your AI client and start using Pine Labs tools.
pinelabs-mcp start Start MCP server (stdio mode)
pinelabs-mcp configure Interactive credential setup
pinelabs-mcp configure --client-id=X --client-secret=Y [--env=uat|prod]
pinelabs-mcp test Test connectivity and credentials
pinelabs-mcp setup <client> Auto-configure an AI client
pinelabs-mcp setup <client> --local Use local path (dev mode)
pinelabs-mcp setup <client> --print Preview config without writing
pinelabs-mcp status Show current configuration
pinelabs-mcp help Show help message
pinelabs-mcp --version Show version
If you prefer to configure manually instead of using npx pinelabs-mcp setup, add the following to your AI client's MCP config:
{
"mcpServers": {
"pinelabs": {
"command": "npx",
"args": ["-y", "pinelabs-mcp"],
"env": {
"PINELABS_CLIENT_ID": "your_client_id",
"PINELABS_CLIENT_SECRET": "your_client_secret"
}
}
}
}
Note: VS Code uses
"servers"instead of"mcpServers"as the top-level key. For production environment, add"PINELABS_ENV": "prod"to theenvblock.
The Pine Labs MCP Server exposes 50+ tools across multiple categories. Each tool maps to a specific Pine Labs payment API endpoint.
Each tool below is tagged with a Type indicating its access pattern and operational risk. This helps you reason about which tools are safe in read-only deployments and which require explicit user confirmation in autonomous (agentic) flows.
Read-only mode: Run the server with
--read-only(or set the equivalent config) to register onlyReadtools and skip allWrite/Destructivetoolsets. Useful for analytics, monitoring, or untrusted agent contexts.
The Remote MCP Server is hosted and maintained by Pine Labs. Use this approach if you prefer to configure your AI client manually with the remote endpoint instead of using the npm CLI.
If you are connecting to a self-hosted remote deployment instead of the
Pine Labs hosted service, replace the remote URL below with
<your-mcp-server-url>.
npx is required to proxy the remote MCP connection.
Install Node.js (which includes npm and npx):
brew install node
choco install nodejs
Alternatively, download from https://nodejs.org/.
npx --version
Add the following to your Cursor MCP settings:
{
"mcpServers": {
"pinelabs": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.pinelabs.com/mcp",
"--header",
"X-Client-Id:<your-client-id>",
"--header",
"X-Client-Secret:<your-client-secret>"
]
}
}
}
Replace <your-client-id> and <your-client-secret> with your Pine Labs credentials. See Authentication for details.
Add the following to your claude_desktop_config.json:
{
"mcpServers": {
"pinelabs": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.pinelabs.com/mcp",
"--header",
"X-Client-Id:<your-client-id>",
"--header",
"X-Client-Secret:<your-client-secret>"
]
}
}
}
Replace <your-client-id> and <your-client-secret> with your Pine Labs credentials.
Add the following to your VS Code settings (JSON):
{
"mcp": {
"inputs": [
{
"type": "promptString",
"id": "pinelabs_client_id",
"description": "Pine Labs Client ID"
},
{
"type": "promptString",
"id": "pinelabs_client_secret",
"description": "Pine Labs Client Secret",
"password": true
}
],
"servers": {
"pinelabs": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.pinelabs.com/mcp",
"--header",
"X-Client-Id:${input:pinelabs_client_id}",
"--header",
"X-Client-Secret:${input:pinelabs_client_secret}"
]
}
}
}
}
Learn more about MCP servers in VS Code's agent mode documentation.
The MCP server authenticates using Client ID and Client Secret credentials issued by Pine Labs.
Note: For local deployments, credentials can be passed via CLI arguments or environment variables. For the remote server, credentials are passed as HTTP headers.
Deploy the MCP server on your own infrastructure for full control over the runtime environment.
The fastest way to get the MCP server on a Windows machine is via Chocolatey. The package is a thin wrapper that installs Python 3.10+ as a dependency and then installs pinelabs-mcp-server from PyPI, registering a pinelabs-mcp shim on PATH.
choco install pinelabs-mcp
Verify the install:
pinelabs-mcp --help
Run the server over stdio:
pinelabs-mcp stdio --client-id <your-client-id> --client-secret <your-client-secret> --env uat
After choco install, point your MCP client at the pinelabs-mcp shim:
{
"mcpServers": {
"pinelabs": {
"command": "pinelabs-mcp",
"args": ["stdio", "--env", "uat"],
"env": {
"PINELABS_CLIENT_ID": "<your-client-id>",
"PINELABS_CLIENT_SECRET": "<your-client-secret>"
}
}
}
}
To uninstall:
choco uninstall pinelabs-mcp
Use the official Pine Labs Docker image directly. No build step required.
Note: To pin a specific version, replace
pinelabs/mcp:latestwithpinelabs/mcp:<version-tag>(e.g.,pinelabs/mcp:v1.0.0) in the configurations below.
Add the following to your claude_desktop_config.json:
{
"mcpServers": {
"pinelabs": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"PINELABS_CLIENT_ID",
"-e",
"PINELABS_CLIENT_SECRET",
"-e",
"PINELABS_ENV",
"pinelabs/mcp:latest"
],
"env": {
"PINELABS_CLIENT_ID": "<your-client-id>",
"PINELABS_CLIENT_SECRET": "<your-client-secret>",
"PINELABS_ENV": "prod"
}
}
}
}
Replace <your-client-id> and <your-client-secret> with your Pine Labs credentials.
Add the following to your VS Code settings (JSON):
{
"mcp": {
"inputs": [
{
"type": "promptString",
"id": "pinelabs_client_id",
"description": "Pine Labs Client ID"
},
{
"type": "promptString",
"id": "pinelabs_client_secret",
"description": "Pine Labs Client Secret",
"password": true
}
],
"servers": {
"pinelabs": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"PINELABS_CLIENT_ID",
"-e",
"PINELABS_CLIENT_SECRET",
"-e",
"PINELABS_ENV=prod",
"pinelabs/mcp:latest"
],
"env": {
"PINELABS_CLIENT_ID": "${input:pinelabs_client_id}",
"PINELABS_CLIENT_SECRET": "${input:pinelabs_client_secret}"
}
}
}
}
}
Learn more about MCP servers in VS Code's agent mode documentation.
{
"mcpServers": {
"pinelabs": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"PINELABS_CLIENT_ID",
"-e",
"PINELABS_CLIENT_SECRET",
"-e",
"PINELABS_ENV=prod",
"pinelabs/mcp:latest"
],
"env": {
"PINELABS_CLIENT_ID": "<your-client-id>",
"PINELABS_CLIENT_SECRET": "<your-client-secret>"
}
}
}
}
Replace <your-client-id> and <your-client-secret> with your Pine Labs credentials.
Clone the repository and build the Docker image locally:
git clone https://github.com/plural-pinelabs/pinelabs-online-mcp.git
cd pinelabs-online-mcp
docker build -t pinelabs-mcp-server:latest .
Once built, replace pinelabs/mcp:latest with pinelabs-mcp-server:latest in the configurations above.
Run the server directly from source without Docker:
# Clone the repository
git clone https://github.com/plural-pinelabs/pinelabs-online-mcp.git
cd pinelabs-online-mcp
# Create and activate a virtual environment
python -m venv .venv
source .venv/bin/activate # macOS/Linux
# .venv\Scripts\activate # Windows
# Install dependencies
pip install -r requirements.txt
# Run the server (stdio mode)
python -m cli.pinelabs_mcp_server.main stdio \
--client-id <your-client-id> \
--client-secret <your-client-secret> \
--env prod
Once running, configure your MCP client to connect to the local process. Example for VS Code:
{
"mcp": {
"servers": {
"pinelabs": {
"command": "python",
"args": [
"-m",
"cli.pinelabs_mcp_server.main",
"stdio"
],
"env": {
"PINELABS_CLIENT_ID": "<your-client-id>",
"PINELABS_CLIENT_SECRET": "<your-client-secret>",
"PINELABS_ENV": "prod"
}
}
}
}
}
python -m cli.pinelabs_mcp_server.main <transport> [options]
Transports:
stdio Standard I/O transport (for MCP clients)
http HTTP transport (for web-based access)
Options:
--client-id Pine Labs client ID
--client-secret Pine Labs client secret
--env Environment: uat, prod (default: uat)
--log-file Path to log file
--log-level Log level: DEBUG, INFO, WARNING, ERROR
--read-only Only register read-only tools
--toolsets Comma-separated list of toolsets to enable
HTTP-only options:
--host Host to bind to (default: 0.0.0.0)
--port Port to listen on (default: 8000)
Use the --log-level DEBUG flag and optionally --log-file to write detailed logs for troubleshooting:
python -m cli.pinelabs_mcp_server.main stdio \
--client-id <ID> --client-secret <SECRET> \
--log-level DEBUG --log-file ./debug.log
Q: Do I need to provide amounts in paisa?
A: No. Amounts are specified in rupees (e.g., 500 for INR 500). No conversion to paisa is required.
Q: What environments are supported?
A: The server supports uat (default) and prod environments. Set via PINELABS_ENV or --env.
Q: Can I restrict which tools are available?
A: Yes. Use the --read-only flag to disable write operations, or use --toolsets to enable specific toolsets (e.g., --toolsets payment_links,orders).
Q: Where can I find the full API reference? A: Visit the Pine Labs Developer Documentation for the complete API reference.
Pine Labs, Pine Labs Online, Plural, Plural Online, payment gateway, online payment gateway, checkout gateway, payment checkout, online checkout, hosted checkout, payment page, payments, online payments, digital payments, payment processing, accept payments, collect payments, payment integration, gateway integration, payments API, payment API, checkout API, gateway API, UPI, cards, credit card, debit card, netbanking, wallet, EMI, cardless EMI, subscriptions, recurring payments, orders, order payments, create payment, initiate payment, process payment, payment links, MCP server, Model Context Protocol, AI payment automation, agentic payments, QR code payments, payment orchestration, merchant API, transaction reporting, fintech, SDK
This project is licensed under the Apache 2.0 license. See LICENSE for the full terms.
Create payment orders, checkout, subscriptions & UPI via PineLabs Plural PG gateway
{ "mcpServers": { "io.github.plural-pinelabs-pinelabs-online-mcp": { "url": "https://mcp.pinelabs.com/mcp", "headers": {} } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก http สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ผู้เผยแพร่ระบุตัวแปรสภาพแวดล้อมเหล่านี้: PINELABS_CLIENT_ID, PINELABS_CLIENT_SECRET, PINELABS_ENV
PineLabs Plural PG — Payment Gateway MCP Server เข้าถึงได้ผ่าน HTTP
ตรวจสอบล่าสุดเมื่อ 2026-11-10 Create payment orders, checkout, subscriptions & UPI via PineLabs Plural PG gateway