Pine Labs Payments Assistant

Query a Pine Labs merchant account: orders, transactions, settlements, subscriptions and success rates, plus checkout…

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Pine Labs Payments Assistant connector does

The Pine Labs Payments Assistant MCP server connects an Indian Pine Labs merchant account to Claude, ChatGPT and any MCP-compatible agent. Its 13 listed tools do two unrelated jobs: they retrieve merchant data — orders, transactions, settlements, subscriptions, success rates — and they help a developer write Pine Labs integration code. Sign-in is required; no anonymous mode exists.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Pine Labs Payments Assistant tools (13)

  • detect_stack
  • get_api_documentation
  • get_bin_details
  • get_merchant_success_rate
  • get_order_details
  • get_payment_link
  • get_plans
  • get_presentation
  • get_settlement
  • get_subscriptions
  • integrate_pinelabs_checkout
  • list_plural_apis
  • search_transaction

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The 13 listed tools all read or generate, but the endpoint is not therefore read-only. Pine Labs' own documentation describes a 30-plus tool set on this same URL that creates payment links and orders, cancels them, and executes subscription debits. Anthropic's listing describes one surface of the endpoint, not the endpoint's ceiling. Treat the 13 names as a snapshot.
  • No scope separates reading from writing. The authorization server advertises exactly one scope, pinelabs, and the RFC 9728 descriptor names only that scope and bearer_methods_supported (both fetched 2026-09-08). No consent screen can show a reader a scope naming write access, and no issued token can be audited for one afterwards.
  • The vendor documentation contradicts the server on OAuth. Pine Labs' MCP FAQ states OAuth is not supported. The server publishes OAuth 2.1 metadata with dynamic client registration and offers a bearer token in its own 401. We report the wire; a reader following the docs alone would wrongly conclude the OAuth path does not exist.
  • One tool reads your local project. Pine Labs states the integration tools read your project's dependency files to detect your stack. That is filesystem access arriving alongside payments access on one connection, and it is a different kind of permission from the other twelve tools.
  • Generated integration code is unreviewed by Pine Labs. Pine Labs instructs the integrating party to review LLM-written code for rogue lines caused by hallucination, requires that the APIs be called from a backend and never from frontend files — naming order creation and refunds as needing special care — and states the integrating party is liable for damages from non-adherence. Carried unsoftened; it is Pine Labs' language, not ours.
  • India only, and amounts are in paisa. Pine Labs Online is an Indian gateway operating under an RBI payment-aggregator licence, and Pine Labs documents amounts in paisa with a valid range of 100 to 1,00,00,000. A prompt that says "500" without a unit is ambiguous by a factor of a hundred.
  • What each tool can see depends on your merchant configuration. Which payment methods, settlement type (T+1, early batch or same-day) and products are enabled is an account property. Pine Labs states a payment link with no methods specified shows everything enabled on the account.
  • No per-tool schemas or safety annotations are available. The handshake is gated and we did not authenticate, so no tool here is confirmed annotated read-only. Undocumented is not the same as confirmed safe.
  • A 401 on this host proves nothing about a path. The gateway returns 401 for every path under /mcp, including invented ones. Anyone probing for a read-only sibling will find four false positives.
  • Not financial advice. This page describes what tools return. It takes no view on any settlement, success rate, transaction, subscription or business decision, and the connector interprets nothing either.

Frequently asked questions

Does the Pine Labs MCP server need a merchant account?

Yes. Pine Labs lists an active Pine Labs Online merchant account with API access enabled as the first prerequisite for both setup paths, and a Client ID and Client Secret generated from the Pine Labs dashboard as the second. There is no anonymous or demo mode, and the live endpoint refused an unauthenticated handshake when we checked it.

Can the Pine Labs connector move money or issue a refund?

Not through the 13 tools Anthropic's directory lists for it, which all retrieve or generate. Pine Labs states in that same listing that no tool in the connector can move funds, issue refunds, or modify the account. But Pine Labs documents a larger 30-plus tool set on this identical endpoint that does create payment links, orders and subscription debits, and no OAuth scope separates reading from writing.

Does the Pine Labs MCP server support OAuth?

The server does, though Pine Labs documentation says otherwise. Its MCP FAQ states plainly that OAuth is not supported and that authentication uses the X-Client-Id and X-Client-Secret headers. The live endpoint disagrees: it publishes OAuth 2.1 authorization-server metadata and its authentication challenge offers a bearer token or those headers. We verified this on the wire.

Which environment should you point the Pine Labs connector at?

Use UAT for development and production only for live transactions. Pine Labs documents two MCP endpoints, a sandbox host carrying test data and no real charges, and the production host that Anthropic's directory lists. The two run identical server software and both refuse an unauthenticated request, so the hostname you paste is the only thing separating test data from real money.

How should amounts be specified with the Pine Labs MCP server?

In paisa, the smallest unit of the Indian rupee. Pine Labs documents 100 for one rupee, 50000 for five hundred, and a valid range from 100 up to one crore paisa, which is ten lakh rupees. An assistant that passes a rupee figure where paisa is expected will be off by a factor of a hundred, so state the unit in your prompt.

Are your Pine Labs API credentials stored on the MCP server?

No, according to Pine Labs. Its MCP FAQ states the Client ID and Client Secret travel in request headers, are forwarded directly to the Pine Labs API, and that nothing is persisted on the MCP layer. This is Pine Labs describing its own architecture, not something we observed, and it applies to the header credentials rather than an OAuth token.

Which payment methods can a Pine Labs payment link offer?

Cards, UPI, net banking, wallets, credit EMI, debit EMI and loyalty points, per Pine Labs documentation. Pine Labs also states that if you specify no methods, every method enabled on your merchant account is displayed by default. Which of those are actually enabled depends on your own account configuration rather than on the connector.

Does the Pine Labs connector work outside India?

The account behind it is an Indian one. Pine Labs describes its payment gateway as an India product, prices in Indian rupees, and operates as an RBI-licensed payment aggregator. It documents cross-border import payments as a separate product that settles in rupees. The connector reads whatever your Indian merchant account holds, wherever you happen to be asking from.

Sources

More Finance connectors

  • Affinity

    Search your CRM, prep for meetings and update deal records from your AI assistant.

  • Aiera

    Pull earnings-call transcripts, event calendars, SEC filings and company publications into your AI assistant.

  • Airwallex Developer

    Search Airwallex documentation and exercise a sandbox account from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Pine Labs Payments Assistant to work.

Connect Pine Labs Payments Assistant once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.