Pinelabs Mcp Server

SSE

by plural-pinelabs

329 downloads Not rated yet

GitHub Website SSE

About

The Pine Labs Online MCP Server implements the Model Context Protocol (MCP) to enable seamless integration between Pine Labs’ online payment APIs and AI tools. It allows AI assistants to perform Pine Labs Online API operations, empowering developers to build intelligent, AI-driven payment applications with ease.

Details

Transport: SSE

Explore

- Exposes 50+ payment gateway tools as MCP tools
- Supports payment links, orders, subscriptions, and UPI payments
- Includes transaction search, refund reports, and merchant analytics
- Provides API documentation retrieval tools
- Offers remote (hosted) and local deployment options
- Requires only client ID/secret for authentication

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name Pinelabs Mcp Server

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "pinelabs mcp server": {
            "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"
                    }
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "pinelabs mcp server": {
            "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"
                    }
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "pinelabs mcp server": {
            "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"
                    }
                }
            }
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "pinelabs mcp server": {
            "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"
                    }
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "pinelabs mcp server": {
            "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"
                    }
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "pinelabs mcp server": {
            "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"
                    }
                }
            }
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "pinelabs mcp server": {
            "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"
                    }
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "pinelabs mcp server": {
            "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"
                    }
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "pinelabs mcp server": {
            "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"
                    }
                }
            }
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "pinelabs mcp server": {
            "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"
                    }
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "pinelabs mcp server": {
            "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"
                    }
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "pinelabs mcp server": {
            "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"
                    }
                }
            }
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "pinelabs mcp server": {
            "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"
                    }
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "pinelabs mcp server": {
            "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"
                    }
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "pinelabs mcp server": {
            "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"
                    }
                }
            }
        }
    }
}

From the repository

Choose your preferred deployment method:

- Remote MCP Server -- Hosted by Pine Labs. No local setup required.
- Local MCP Server -- Self-hosted via Docker or source. Full control over your infrastructure.

---

``bash npx --version



Add the following to your Cursor MCP settings:

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. See Authentication for details.

Add the following to your claude_desktop_config.json:`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. - Configure MCP servers in Claude Desktop: MCP Quickstart Guide - Install Claude Desktop: Download

Add the following to your VS Code settings (JSON):`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.
1. Sign up or log in to the Pine Labs merchant dashboard provided with your account.

2. Navigate to your account settings to locate your Client ID and Client Secret.

3. Use these credentials in the MCP server configuration as shown in the setup instructions above.



> Note: For local deployments, credentials can be passed via CLI arguments or environment variables. For the remote server, credentials are passed as HTTP headers.



---
python -m venv .venv

source .venv/bin/activate      # macOS/Linux
pip install -r requirements.txt

| Variable | Required | Default | Description | |:---------|:---------|:--------|:------------| |PINELABS_CLIENT_ID| Yes | -- | Pine Labs client ID for API authentication | |PINELABS_CLIENT_SECRET| Yes | -- | Pine Labs client secret for API authentication | |PINELABS_ENV | No | uat | Target environment: uat or prod| |LOG_LEVEL | No | INFO | Log verbosity: DEBUG, INFO, WARNING, ERROR| |LOG_FILE| No | stderr | Path to log output file | |READ_ONLY | No | false| Restrict to read-only tools (disables write operations) | |TOOLSETS` | No | all | Comma-separated list of toolsets to enable |

The Pine Labs MCP Server exposes 50+ tools across multiple categories. Each tool maps to a specific Pine Labs payment API endpoint.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "pinelabs mcp server": {
            "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"
                    }
                }
            }
        }
    }
}

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"
            }
        }
    }
}

Pine Labs Payment Gateway MCP Server (Official)

Pine Labs MCP Server is a production-grade Model Context Protocol (MCP) server that connects AI assistants and agentic applications to the Pine Labs payment gateway. It exposes Pine Labs' online payment APIs -- payment links, checkout orders, UPI intent payments, subscriptions, and transaction reporting -- as structured MCP tools that any compatible AI client can invoke. Built for fintech developers integrating payment gateway capabilities into AI-driven workflows, this server enables programmatic access to the full Pine Labs payment API surface through natural-language AI interfaces such as VS Code Copilot, Claude Desktop, and Cursor. ---

- Quick Start - Available Tools - Use Cases - Remote MCP Server (Recommended) - Authentication - Local MCP Server - Configuration - Debugging - FAQ - Keywords - License ---

Quick Start

Choose your preferred deployment method: - Remote MCP Server -- Hosted by Pine Labs. No local setup required. - Local MCP Server -- Self-hosted via Docker or source. Full control over your infrastructure. ---

Available Tools

The Pine Labs MCP Server exposes 50+ tools across multiple categories. Each tool maps to a specific Pine Labs payment API endpoint.

Payment Links

| Tool | Description | API Reference | |:-----|:------------|:--------------| | create_payment_link | Create a new payment link for collecting payments | Payment Link - Create | | get_payment_link_by_id | Fetch a payment link by its payment link ID | Payment Link - Get by ID | | get_payment_link_by_merchant_reference | Fetch a payment link by its merchant payment link reference | Payment Link - Get by Reference | | cancel_payment_link | Cancel an active payment link | Payment Link - Cancel | | resend_payment_link_notification | Resend a payment link notification to the customer | Payment Link - Resend |

Orders

| Tool | Description | API Reference | |:-----|:------------|:--------------| | get_order_by_order_id | Retrieve order details by order ID | Order - Get by ID | | cancel_order | Cancel a pre-authorized payment against an order | Order - Cancel |

Checkout Orders

| Tool | Description | API Reference | |:-----|:------------|:--------------| | create_order | Create a new checkout order and generate a checkout link | Order - Create |

Subscriptions

| Tool | Description | API Reference | |:-----|:------------|:--------------| | create_plan | Create a new subscription plan | Plan - Create | | get_plans | Retrieve subscription plans | Plan - Get All | | get_plan_by_id | Retrieve a subscription plan by plan ID | Plan - Get Specific | | get_plan_by_merchant_reference | Retrieve a plan by merchant plan reference | Plan - Get Specific | | update_plan | Update an existing subscription plan | Plan - Update | | delete_plan | Delete a subscription plan | Plan - Delete | | create_subscription | Create a new subscription against a plan | Subscription - Create | | get_subscriptions | Retrieve subscriptions | Subscription - Get All | | get_subscription_by_id | Retrieve a subscription by subscription ID | Subscription - Get Specific | | get_subscription_by_merchant_reference | Retrieve a subscription by merchant reference | Subscription - Get Specific | | pause_subscription | Pause an active subscription | Subscription - Pause | | resume_subscription | Resume a paused subscription | Subscription - Resume | | cancel_subscription | Cancel an active subscription | Subscription - Cancel | | update_subscription | Update an existing subscription | Subscription - Update | | create_presentation | Create a presentation (payment request) for a subscription | Presentation - Create | | get_presentation | Retrieve a presentation by presentation ID | Presentation - Get | | delete_presentation | Delete a presentation | Presentation - Delete | | get_presentations_by_subscription_id | Retrieve all presentations for a subscription | Presentation - Get by Subscription | | get_presentation_by_merchant_reference | Retrieve a presentation by merchant reference | Presentation - Get | | send_subscription_notification | Send a pre-debit notification for a subscription | Presentation - Create | | create_debit | Execute a debit (payment collection) against a subscription | Presentation - Create | | create_merchant_retry | Retry mandate execution for a failed debit (max 3 retries) | Merchant Retry |

UPI Payments

| Tool | Description | API Reference | |:-----|:------------|:--------------| | create_upi_intent_payment_with_qr | Create a UPI intent payment with QR code for instant collection | UPI Intent QR |

Reports and Transaction Search

| Tool | Description | API Reference | |:-----|:------------|:--------------| | get_payment_link_details | Fetch payment link details within a date range | API Docs | | get_order_details | Fetch order details within a date range | API Docs | | get_refund_order_details | Fetch refund order details within a date range | API Docs | | search_transaction | Se

…

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Details

Explore

Setting up with Highlight

From the repository

Claude Desktop / Cursor

Mcp

Pine Labs Payment Gateway MCP Server (Official)

Table of Contents

Quick Start

Available Tools

Payment Links

Orders

Checkout Orders

Subscriptions

UPI Payments

Reports and Transaction Search

More like this

Sequential Thinking

Sentry

Github

Filesystem