Skip to main content
Glama

PineLabs Plural PG — Payment Gateway MCP Server

Server Details

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

Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL
Repository
plural-pinelabs/pinelabs-online-mcp
GitHub Stars
1
Server Listing
pinelabs-mcp

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsA

Average 4.3/5 across 57 of 57 tools scored.

Server CoherenceA
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.

Discussions

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

Related MCP Servers

  • A
    license
    -
    quality
    D
    maintenance
    Enables interaction with Razorpay payment gateway through natural language, allowing users to fetch payments, manage orders, issue refunds, and list settlements.
    Last updated
    1
    MIT
  • F
    license
    -
    quality
    C
    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.
    Last updated
  • F
    license
    -
    quality
    -
    maintenance
    Enables AI agents to interact with multiple payment providers (Stripe, Paystack) through a unified API. Supports payment initialization, verification, refunds, customer management, and invoicing without requiring knowledge of specific provider implementations.
    Last updated
    2
  • A
    license
    -
    quality
    D
    maintenance
    Enables merchant integration with payware payment APIs for creating transactions, managing authentication, and generating code examples across multiple programming languages. Provides comprehensive tools for payment processing, JWT authentication, and sandbox testing.
    Last updated
    30
    MIT

View all MCP Servers

Try in Browser

Your Connectors

Sign in to create a connector for this server.