Pinelabs Online MCP Server

MCP client for Pine Labs payment gateway -- connect Claude Desktop, Cursor, VS Code, and other AI assistants to Pine Labs payment APIs using your

Remote serverstreamable-httpPython

What is the Pinelabs Online MCP MCP server?

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. That is what the pinelabs online mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

The tools it exposes

The server publishes 13 tools. What each one is for:

  • get_api_documentation — Read
  • list_plural_apis — Read
  • detect_stack — Read
  • integrate_pinelabs_checkout — Read
  • Orders — The Orders tool exposed by this server
  • Refunds — The Refunds tool exposed by this server
  • Settlements — The Settlements tool exposed by this server
  • Payouts — The Payouts tool exposed by this server
  • Subscriptions — The Subscriptions tool exposed by this server
  • Benefits — If you are connecting to a self-hosted remote deployment instead of the Pine Labs hosted service, replace the remote URL below with
  • Prerequisites — npx is required to proxy the remote MCP connection. Install Node.js (which includes npm and npx):
  • macOS — The macOS tool exposed by this server

What it needs from you

Configuration is passed through the environment: PINELABS_CLIENT_ID, PINELABS_CLIENT_SECRET, PINELABS_ENV, YOUR_ID, YOUR_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 13 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Pinelabs Online MCP.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Pinelabs Online MCP's toolset — get_api_documentation, list_plural_apis, detect_stack and 10 more — is a fair guide to whether it matches your workflow. It is maintained by plural-pinelabs; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
get_api_documentationRead
list_plural_apisRead
detect_stackRead
integrate_pinelabs_checkoutRead
OrdersThe Orders tool exposed by this server.
RefundsThe Refunds tool exposed by this server.
SettlementsThe Settlements tool exposed by this server.
PayoutsThe Payouts tool exposed by this server.
SubscriptionsThe Subscriptions tool exposed by this server.
BenefitsIf 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>.
Prerequisitesnpx is required to proxy the remote MCP connection. Install Node.js (which includes npm and npx):
macOSThe macOS tool exposed by this server.
WindowsAlternatively, download from [https://nodejs.org/](https://nodejs.org/).

How to install the Pinelabs Online MCP MCP server

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

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
PINELABS_CLIENT_IDConfiguration value read at startup.Optional
PINELABS_CLIENT_SECRETCredential the server authenticates with.Yes
PINELABS_ENVConfiguration value read at startup.Optional
YOUR_IDConfiguration value read at startup.Optional
YOUR_SECRETCredential the server authenticates with.Yes

Example prompts to try

  • Use Pinelabs Online MCP to get api documentation.
  • Use Pinelabs Online MCP to list plural apis.
  • Use Pinelabs Online MCP to detect stack.

Frequently asked questions

It connects Pinelabs Online MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 13 tools (get_api_documentation, list_plural_apis, detect_stack, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Pinelabs Online MCP directly.