PineLabs Plural PG — Payment Gateway MCP Server

Name: PineLabs Plural PG — Payment Gateway MCP Server
Author: plural-pinelabs

Server Details

Create payment orders, checkout, subscriptions & UPI via PineLabs Plural PG gateway

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Unhealthy
OAuth: Works in Glama
Last Tested: 2026-09-09 13:50
Transport: Streamable HTTP
URL
Repository: plural-pinelabs/pinelabs-online-mcp
GitHub Stars: 1
Server Listing: pinelabs-mcp

TDQS

A4.1/5.0

Scored 2026-07-08 07:40 across 57 tools

Disambiguation5/5

Each tool targets a specific resource and action, with distinct purposes. Even though there are many retrieval tools (e.g., by ID vs. merchant reference), they are clearly differentiated by parameters and descriptions. No two tools appear to do the same thing.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_order, get_order_by_order_id, cancel_subscription). No mixing of conventions, making the set predictable and easy to navigate.

Tool Count2/5

With 57 tools, the server is over-scoped. It covers multiple domains (orders, payment links, payouts, subscriptions, plans, presentations, settlements, integration helpers) that could be split into smaller, focused servers. The count exceeds the typical well-scoped range and introduces unnecessary complexity.

Completeness4/5

The tool set covers the core payment gateway lifecycle comprehensively: order management, refunds, payouts, subscription management, payment links, OTP flows, and settlements. Minor gaps like webhook management or more detailed analytics exist, but the essential operations are well covered.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

56 tool updatesMay 7, 2026
- Changedcancel_order1 field changed
  - addedInput schema / properties / order_id / description
```
Added value: +"Unique identifier of the order in the Pine Labs database.\n      Example: v1-5757575757-aa-hU1rUd"
```
- Changedcancel_payment_link1 field changed
  - addedInput schema / properties / payment_link_id / description
```
Added value: +"Unique identifier of the payment link\n             (e.g., pl-v1-5757575757-aa-hU1rUd). Max 50 characters."
```
- Addedcancel_payout
- Addedcancel_subscription
- Addedcapture_order
- Addedcreate_card_payment
- Addedcreate_debit
- Addedcreate_merchant_retry
- Changedcreate_order34 fields changed
  - addedInput schema / properties / allowed_payment_methods / description
```
Added value: +"Payment methods to offer: CARD, UPI, POINTS, NETBANKING, WALLET, CREDIT_EMI, DEBIT_EMI, BNPL"
```
  - addedInput schema / properties / amount_value / description
```
Added value: +"Transaction amount in paisa (e.g., 1100 = Rs.11). Min: 100, Max: 100000000"
```
  - addedInput schema / properties / billing_address1 / description
```
Added value: +"Billing address line 1"
```
  - addedInput schema / properties / billing_address2 / description
```
Added value: +"Billing address line 2"
```
  - addedInput schema / properties / billing_address3 / description
```
Added value: +"Billing address line 3"
```
  - addedInput schema / properties / billing_city / description
```
Added value: +"Billing city"
```
  - addedInput schema / properties / billing_country / description
```
Added value: +"Billing country"
```
  - addedInput schema / properties / billing_full_name / description
```
Added value: +"Billing full name"
```
  - addedInput schema / properties / billing_pincode / description
```
Added value: +"Billing pincode"
```
  - addedInput schema / properties / billing_state / description
```
Added value: +"Billing state"
```
  - addedInput schema / properties / callback_url / description
```
Added value: +"URL to redirect customers on success"
```
  - addedInput schema / properties / currency / description
```
Added value: +"Three-letter ISO currency code (default: INR)"
```
  - addedInput schema / properties / customer_country_code / description
```
Added value: +"Country code for mobile (e.g., 91). Defaults to 91"
```
  - addedInput schema / properties / customer_email / description
```
Added value: +"Customer email address"
```
  - addedInput schema / properties / customer_first_name / description
```
Added value: +"Customer first name"
```
  - addedInput schema / properties / customer_id / description
```
Added value: +"Customer ID in Pine Labs database"
```
  - addedInput schema / properties / customer_last_name / description
```
Added value: +"Customer last name"
```
  - addedInput schema / properties / customer_mobile / description
```
Added value: +"Customer mobile number (10-20 digits)"
```
  - addedInput schema / properties / failure_callback_url / description
```
Added value: +"URL to redirect customers on failure"
```
  - addedInput schema / properties / integration_mode / description
```
Added value: +"Integration mode: REDIRECT (default), IFRAME, or SDK"
```
  - addedInput schema / properties / merchant_metadata / description
```
Added value: +"Custom key-value metadata (max 10 pairs, 256 chars each)"
```
  - addedInput schema / properties / merchant_order_reference / description
```
Added value: +"Unique identifier for the order (1-50 chars). Used for idempotency/reconciliation."
```
  - addedInput schema / properties / notes / description
```
Added value: +"Note to show against the order (e.g., Order1)"
```
  - addedInput schema / properties / pre_auth / description
```
Added value: +"Whether pre-authorization is required (default: false)"
```
  - addedInput schema / properties / product_amount / description
```
Added value: +"Product amount in paisa (used with product_code)"
```
  - addedInput schema / properties / product_code / description
```
Added value: +"Product code for EMI orders (e.g., redm_1)"
```
  - addedInput schema / properties / shipping_address1 / description
```
Added value: +"Shipping address line 1"
```
  - addedInput schema / properties / shipping_address2 / description
```
Added value: +"Shipping address line 2"
```
  - addedInput schema / properties / shipping_address3 / description
```
Added value: +"Shipping address line 3"
```
  - addedInput schema / properties / shipping_city / description
```
Added value: +"Shipping city"
```
  - addedInput schema / properties / shipping_country / description
```
Added value: +"Shipping country"
```
  - addedInput schema / properties / shipping_full_name / description
```
Added value: +"Shipping full name"
```
  - addedInput schema / properties / shipping_pincode / description
```
Added value: +"Shipping pincode"
```
  - addedInput schema / properties / shipping_state / description
```
Added value: +"Shipping state"
```
- Changedcreate_payment_link32 fields changed
  - addedInput schema / properties / allowed_payment_methods / description
```
Added value: +"Payment methods to offer: CARD, UPI, POINTS, NETBANKING, WALLET, CREDIT_EMI, DEBIT_EMI"
```
  - addedInput schema / properties / amount_value / description
```
Added value: +"Amount in paisa (e.g., 50000 = Rs.500). Min: 100, Max: 100000000"
```
  - addedInput schema / properties / billing_address1 / description
```
Added value: +"Billing address line 1"
```
  - addedInput schema / properties / billing_address2 / description
```
Added value: +"Billing address line 2"
```
  - addedInput schema / properties / billing_address3 / description
```
Added value: +"Billing address line 3"
```
  - addedInput schema / properties / billing_city / description
```
Added value: +"Billing city"
```
  - addedInput schema / properties / billing_country / description
```
Added value: +"Billing country"
```
  - addedInput schema / properties / billing_full_name / description
```
Added value: +"Billing full name"
```
  - addedInput schema / properties / billing_pincode / description
```
Added value: +"Billing pincode"
```
  - addedInput schema / properties / billing_state / description
```
Added value: +"Billing state"
```
  - addedInput schema / properties / cart_coupon_discount_amount / description
```
Added value: +"Cart-level coupon discount in paisa."
```
  - addedInput schema / properties / currency / description
```
Added value: +"Three-letter ISO currency code (default: INR)"
```
  - addedInput schema / properties / customer_country_code / description
```
Added value: +"Country code for mobile (e.g., +91). Defaults to +91"
```
  - addedInput schema / properties / customer_email / description
```
Added value: +"Customer email address"
```
  - addedInput schema / properties / customer_first_name / description
```
Added value: +"Customer first name"
```
  - addedInput schema / properties / customer_id / description
```
Added value: +"Customer ID in Pine Labs database"
```
  - addedInput schema / properties / customer_last_name / description
```
Added value: +"Customer last name"
```
  - addedInput schema / properties / customer_mobile / description
```
Added value: +"Customer mobile number (10-20 digits)"
```
  - addedInput schema / properties / description / description
```
Added value: +"Payment description (e.g., \"Payment for Order #12345\")"
```
  - addedInput schema / properties / expire_by / description
```
Added value: +"Expiry timestamp in ISO 8601 (e.g., 2025-03-21T08:29Z). Max 180 days"
```
  - addedInput schema / properties / merchant_metadata / description
```
Added value: +"Custom key-value metadata (e.g., {\"order_id\": \"12345\"})"
```
  - addedInput schema / properties / merchant_payment_link_reference / description
```
Added value: +"Your unique reference for this payment link (1-50 chars, for idempotency/reconciliation). Auto-generated if not provided."
```
  - addedInput schema / properties / product_amount / description
```
Added value: +"Product amount in paisa. Used only when product_code is provided."
```
  - addedInput schema / properties / product_code / description
```
Added value: +"Product identifier (e.g., \"redmi_10\"). If provided, creates a product_details entry."
```
  - addedInput schema / properties / shipping_address1 / description
```
Added value: +"Shipping address line 1"
```
  - addedInput schema / properties / shipping_address2 / description
```
Added value: +"Shipping address line 2"
```
  - addedInput schema / properties / shipping_address3 / description
```
Added value: +"Shipping address line 3"
```
  - addedInput schema / properties / shipping_city / description
```
Added value: +"Shipping city"
```
  - addedInput schema / properties / shipping_country / description
```
Added value: +"Shipping country"
```
  - addedInput schema / properties / shipping_full_name / description
```
Added value: +"Shipping full name"
```
  - addedInput schema / properties / shipping_pincode / description
```
Added value: +"Shipping pincode"
```
  - addedInput schema / properties / shipping_state / description
```
Added value: +"Shipping state"
```
- Addedcreate_payout
- Addedcreate_plan
- Addedcreate_presentation
- Addedcreate_refund
- Addedcreate_subscription
- Addeddelete_plan
- Addeddelete_presentation
- Addeddetect_stack
- Addedfetch_order_payments
- Addedgenerate_otp
- Addedget_all_settlements
- Addedget_api_documentation
- Addedget_card_details
- Changedget_merchant_success_rate2 fields changed
  - addedInput schema / properties / end_date / description
```
Added value: +"Natural-language datetime (e.g., 'now', 'yesterday at 23:59:59')\n      or exact 'YYYY-MM-DD HH:MM:SS' string. Defaults to 'now'."
```
  - addedInput schema / properties / start_date / description
```
Added value: +"Natural-language datetime (e.g., '5 hours ago', 'yesterday at 00:00')\n        or exact 'YYYY-MM-DD HH:MM:SS' string. Maximum range is 7 days."
```
- Addedget_order_by_merchant_order_reference
- Changedget_order_by_order_id1 field changed
  - addedInput schema / properties / order_id / description
```
Added value: +"Unique identifier of the order in the Pine Labs database.\n      Example: v1-4405071524-aa-qlAtAf"
```
- Changedget_order_details5 fields changed
  - addedInput schema / properties / end_date / description
```
Added value: +"End date in ISO 8601 format (e.g., 2024-10-09T23:59:59).\n       Maximum date range is 60 days."
```
  - addedInput schema / properties / merchant_id / description
```
Added value: +"Merchant identifier for the request."
```
  - addedInput schema / properties / page / description
```
Added value: +"Page number to retrieve."
```
  - addedInput schema / properties / per_page / description
```
Added value: +"Number of records per page."
```
  - addedInput schema / properties / start_date / description
```
Added value: +"Start date in ISO 8601 format (e.g., 2024-10-01T00:00:00).\n         Maximum date range is 60 days."
```
- Changedget_payment_link_by_id1 field changed
  - addedInput schema / properties / payment_link_id / description
```
Added value: +"Unique identifier of the payment link\n             (e.g., pl-v1-5757575757-aa-hU1rUd). Max 50 characters."
```
- Changedget_payment_link_by_merchant_reference1 field changed
  - addedInput schema / properties / merchant_payment_link_reference / description
```
Added value: +"Unique merchant reference for the payment link.\n                             Max 50 characters."
```
- Changedget_payment_link_details5 fields changed
  - addedInput schema / properties / end_date / description
```
Added value: +"End date in ISO 8601 format (e.g., 2024-10-09T23:59:59).\n       Maximum date range is 60 days."
```
  - addedInput schema / properties / merchant_id / description
```
Added value: +"Merchant identifier for the request."
```
  - addedInput schema / properties / page / description
```
Added value: +"Page number to retrieve."
```
  - addedInput schema / properties / per_page / description
```
Added value: +"Number of records per page."
```
  - addedInput schema / properties / start_date / description
```
Added value: +"Start date in ISO 8601 format (e.g., 2024-10-01T00:00:00).\n         Maximum date range is 60 days."
```
- Addedget_payout_balance
- Addedget_payout_details
- Addedget_payout_payments
- Addedget_plan_by_id
- Addedget_plan_by_merchant_reference
- Addedget_plans
- Addedget_presentation
- Addedget_presentation_by_merchant_reference
- Addedget_presentations_by_subscription_id
- Changedget_refund_order_details5 fields changed
  - addedInput schema / properties / end_date / description
```
Added value: +"End date in ISO 8601 format (e.g., 2024-10-09T23:59:59).\n       Maximum date range is 60 days."
```
  - addedInput schema / properties / merchant_id / description
```
Added value: +"Merchant identifier for the request."
```
  - addedInput schema / properties / page / description
```
Added value: +"Page number to retrieve."
```
  - addedInput schema / properties / per_page / description
```
Added value: +"Number of records per page."
```
  - addedInput schema / properties / start_date / description
```
Added value: +"Start date in ISO 8601 format (e.g., 2024-10-01T00:00:00).\n         Maximum date range is 60 days."
```
- Addedget_settlement_by_utr
- Addedget_subscription_by_id
- Addedget_subscription_by_merchant_reference
- Addedget_subscriptions
- Addedintegrate_pinelabs_checkout
- Addedlist_plural_apis
- Addedpause_subscription
- Addedresend_otp
- Changedresend_payment_link_notification1 field changed
  - addedInput schema / properties / payment_link_id / description
```
Added value: +"Unique identifier of the payment link\n             (e.g., pl-v1-5757575757-aa-hU1rUd). Max 50 characters."
```
- Addedresume_subscription
- Changedsearch_transaction2 fields changed
  - addedInput schema / properties / merchant_id / description
```
Added value: +"Merchant identifier for the request."
```
  - addedInput schema / properties / transaction_id / description
```
Added value: +"Unique identifier of the transaction."
```
- Addedsend_subscription_notification
- Addedsubmit_otp
- Addedupdate_payout
- Addedupdate_plan
- Addedupdate_subscription
14 tool updatesApr 27, 2026
- First observedcancel_order
- First observedcancel_payment_link
- First observedcreate_order
- First observedcreate_payment_link
- First observedcreate_upi_intent_payment_with_qr
- First observedget_merchant_success_rate
- First observedget_order_by_order_id
- First observedget_order_details
- First observedget_payment_link_by_id
- First observedget_payment_link_by_merchant_reference
- First observedget_payment_link_details
- First observedget_refund_order_details
- First observedresend_payment_link_notification
- First observedsearch_transaction

Frequently Asked Questions

Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.

Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
- GitHub identity – fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
- HTTP challenge – works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
- DNS challenge – works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.

The HTTP ownership file has this structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "claim": "glama_claim_..."
}

Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.

If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.

For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Connectors

Checkout PageOAuth
com.checkoutpage
Create and manage checkout pages, event ticketing, forms, customers, payments and subscriptions.
E-commerce & Retail Payments & Billing
1
PagSeguro C
io.github.mcp-dir
PagSeguro / PagBank payments, orders, charges (get, cancel, refund), checkouts and public key via th
Payments & Billing E-commerce & Retail
172
India Payments (Razorpay Payment Links — UPI / cards / netbanking)A
app.wishpool
India payments for AI agents — UPI, cards, wallets via Razorpay Payment Links. Never holds funds.
Payments & Billing Finance
2
Pagar.me C
io.github.mcp-dir
Stone's payments gateway (api.pagar.me), orders, charges (card, Pix, boleto), customers and cards, p
Payments & Billing E-commerce & Retail
862

Related MCP Servers

Razorpay MCP Server
Payments & Billing Finance
hahahamid
A
license
Not graded
quality
D
maintenance
Enables interaction with Razorpay payment gateway through natural language, allowing users to fetch payments, manage orders, issue refunds, and list settlements.
Updated 6 months ago (2026-03-15 20:55 UTC)
12
MIT
CL Razorpay MCP Server
Payments & Billing Finance
AStheTECH
F
license
Not graded
quality
D
maintenance
Integrates with Razorpay's payment infrastructure to manage orders, process payments, handle refunds, and query settlements via the Model Context Protocol. Features stateless, multi-tenant architecture with secure per-request authentication using API keys.
Updated 3 months ago (2026-06-15 06:47 UTC)
-
Razorpay MCP Agent
PandeyAnukrati
-
license
Not graded
quality
Not graded
maintenance
Enables conversational AI agents to manage Razorpay payments directly, including payment lookups, order creation, refunds, UPI QR generation, and real-time webhook triage via the Model Context Protocol.
Updated 4 days ago (2026-09-05 16:06 UTC)
-
dukaan-agent
E-commerce & Retail Payments & Billing
Blazehue
A
license
Not graded
quality
B
maintenance
Enables AI agents to search a merchant's product catalog and complete UPI checkouts via Razorpay test-mode APIs, with spend mandates and full audit logging.
Updated 4 days ago (2026-09-05 14:09 UTC)
MIT

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Server Details

TDQS

Tool Schema Changelog

Frequently Asked Questions

Discussions

Related MCP Connectors

Related MCP Servers

Razorpay MCP Server

CL Razorpay MCP Server

Razorpay MCP Agent

dukaan-agent

Glama MCP Gateway

Resources