Skip to main content
Glama
blmsoft

BLMPay MCP Server

by blmsoft

BLMPay MCP Server

Official BLMPay MCP server, version 0.2.0.

The server exposes BLMPay API v1 as MCP tools so AI coding clients can inspect balances, payments, payouts, webhooks and API capabilities without inventing endpoints. Write/financial tools exist but are disabled by default.

Important security defaults

  • BLMPAY_MCP_ALLOW_WRITES=0 by default.

  • Remote MCP endpoint requires its own BLMPAY_MCP_ACCESS_TOKEN.

  • BLMPay merchant API key stays server-side in BLMPAY_API_KEY.

  • Never expose a live merchant API key in a desktop/mobile app or public repo.

  • For a domain-bound BLMPay API key, set BLMPAY_INTEGRATION_ORIGIN to the same HTTPS integration URL saved on that key. The MCP server automatically sends it as X-BLMPay-Origin on every BLMPay API request.

Example:

BLMPAY_API_KEY=bp_live_xxxxxxxxxxxxxxxxx
BLMPAY_INTEGRATION_ORIGIN=https://mcp.example.com
BLMPAY_MCP_ALLOW_WRITES=0

A mismatched domain can be rejected by BLMPay with 403 integration_domain_not_allowed. Existing legacy API keys that have no saved domain remain backward compatible.

Related MCP server: Alternative Payments MCP Server

Run

npm install
cp .env.example .env
# load .env using your host/process manager, then:
npm start

Remote endpoint defaults to http://127.0.0.1:3000/mcp. Put it behind HTTPS/reverse proxy when exposed publicly.

Shared hosting

MCP itself does not require an AI model API. It only translates MCP tool calls to BLMPay API requests. However, this Node server needs a Node-capable long-running runtime. If your cPanel/shared host does not support Node applications, deploy this small service on a VPS or another Node host while keeping the main BLMPay PHP production server unchanged.

Financial write tools

Read tools work with BLMPAY_MCP_ALLOW_WRITES=0. Payment creation, payouts, webhook changes and USDT write operations require BLMPAY_MCP_ALLOW_WRITES=1. Enable writes only in an explicitly trusted environment and keep idempotency keys enabled for payment/payout creation.

OpenAPI: https://github.com/blmsoft/blmpay-openapi PHP SDK: https://github.com/blmsoft/blmpay-sdk-php Node SDK: https://github.com/blmsoft/blmpay-sdk-node Flutter SDK: https://github.com/blmsoft/blmpay-sdk-flutter

Powered by BLMSoft.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI coding assistants to interact with MonCashConnect payment data read-only, including checking balances, listing transactions, and viewing payment details, without moving money.
    8
    MIT
  • F
    license
    Not graded
    quality
    A
    maintenance
    Provides AI assistants with read and safe-write access to Alternative Payments customers, invoices, payment requests, transactions, payouts, and webhooks without directly moving money.
  • F
    license
    Not graded
    quality
    D
    maintenance
    Enables financial data access from connected bank accounts via MCP tools, allowing natural language queries about balances, transactions, subscriptions, investments, and more, with a focus on privacy and read-only access.
  • F
    license
    Not graded
    quality
    B
    maintenance
    Enables AI assistants to query internal business data for insights into customers, revenue, subscriptions, sales, and churn through controlled, read-only MCP tools.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/blmsoft/blmpay-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server