Pine Labs CLI – MCP Command Line Tool for Developers

Prerequisites

Make sure the following are in place before you begin:

MCP-compatible

Node.js 18+ — Download

Pine Labs merchant account

A Pine Labs Online Merchant account with API access enabled

API credentials

Your X-Client-Id and X-Client-Secret from the Pine Labs Dashboard

Get Your API Credentials

Pine Labs authenticates MCP requests using a Client ID and Client Secret pair. To obtain yours:

1 Log in to the Pine Labs Dashboard .
2 Navigate to your merchant account settings.
3 Locate your X-Client-Id and X-Client-Secret values.
4 Copy both — you’ll need them in the next step.

Connect Pine Labs MCP Using the CLI

npm i pinelabs-mcp

Configure your credentials

Save your Pine Labs MCP credentials locally using the Client ID and Client Secret from Step 1.

pinelabs-mcp configure --client-id=X --client-secret=Y [--env=uat | prod]

Environment Variables

Variable	Required	Default	Description
`PINELABS_CLIENT_ID`	Yes	—	Your Pine Labs client ID
`PINELABS_CLIENT_SECRET`	Yes	—	Your Pine Labs client secret
`PINELABS_ENV`	No	`uat`	Environment: `uat` or `prod`
`PINELABS_MCP_ENDPOINT`	No	—	Custom endpoint URL (overrides `PINELABS_ENV`)
`DEBUG`	No	`false`	Enable debug logging (`true` or `1`)

Test your Connection

After saving the configuration, restart your AI client. Then try this quick test prompt in your assistant:

“npx pinelabs-mcp test”

Note: If everything is configured correctly, the assistant will respond and confirms your MCP connection is live.

Manual Configuration

If you prefer to configure manually, 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.

Production environment: Add "PINELABS_ENV": "prod" to the env block.

References

Available Tools

The MCP server exposes 20+ tools across these categories:

Payment Links — Create, retrieve, cancel, and resend payment links
Orders — Create, track, and cancel checkout orders
Payments — QR Code Generation for UPI payments
Refunds — Create and retrieve refund details
Settlements — Settlements APIs

See the complete tools reference for details.

CLI Commands

CLI command	Descriptions
`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]`	Configure MCP CLI with client and secret
`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

Troubleshooting

Issue	Fix
Missing credentials	Run `npx pinelabs-mcp configure` or set `PINELABS_CLIENT_ID` / `PINELABS_CLIENT_SECRET` in your MCP client's `env` block
Tools not appearing	Restart your AI assistant; verify Node.js 18+ (`node --version`); set `"DEBUG": "true"` in `env`
Connection issues	Verify credentials; check network access to `mcp.pluralpay.in`; allow HTTPS if behind a proxy

Supported AI Clients

Client	Command	Config Path
Claude Desktop	setup claude-desktop	`Platform-specific Claude config`
Cursor	setup cursor	`~/.cursor/mcp.json`
VS Code	setup vscode	`..vscode/mcp.json (project)`
Windsurf	setup windsurf	`~/.codeium/windsurf/mcp_config.json`
OpenCode	setup opencode	`.opencode/config.json (project)`
GitHub Copilot	setup copilot	`~/.copilot/mcp-config.json`
OpenAI Codex	setup codex	`.codex/config.toml`