generate_payment_linkLABSCO SUMMARY
Money can come in; it cannot go out.
The blocked operations are enforced at the server rather than hidden from the model — a hand-crafted refund call is rejected with an explanation and a Dashboard link. That is what makes it reasonable to connect an assistant to a live payment account.
What it is
A Node MCP server for a MONEI payment account. It creates payment links, looks up payments by id, searches payment history, reads subscriptions and account configuration, and authenticates merchants over OAuth with scoped permissions.
What you get
- Payment links created and shared with customers
- A payment's details and status fetched by id
- Payment history searched and filtered
- Subscription details and status read
- Merchant account configuration read
- Refunds, card and Bizum charges, payouts, subscription cancellation and account changes rejected at the server, with a pointer to the Dashboard
Requirements
Node.js 18+ and a MONEI account with API credentials — an OAuth client id and secret, plus a plain API key for development work. Connect over streamable HTTP at /mcp; legacy SSE is at /sse.
Setup effort
Build from source — git clone https://github.com/MONEI/MONEI-MCP-Server.git
USE CASES
01
Getting a customer a way to pay, mid-conversation
Create the payment link and send it, without opening the dashboard.
02
Answering whether a payment went through
Fetch it by id, or find it in the history when the id is not to hand.
03
Reviewing what came in this week
Search and filter the payment history over the range you care about.
04
Checking a subscriber's status
Read the subscription detail, or list them when you are looking for the one that lapsed.
05
Confirming which account you are working against
Read the merchant account configuration before acting on anything.
6 tools
Listed in project docs. Your client may show a different list.
get_paymentlist_paymentsget_subscriptionlist_subscriptionsget_account_infoBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
- A client that can reach a remote MCP server over HTTP
- Node.js 18+
- MONEI_CLIENT_ID in your environment
- MONEI_CLIENT_SECRET in your environment
- MONEI_API_KEY in your environment
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/MONEI/MONEI-MCP-Server.git
cd MONEI-MCP-Server
npm install
cp .env.example .envEdit .env with your MONEI credentials: MONEI_CLIENT_ID, MONEI_CLIENT_SECRET, and MONEI_API_KEY for development and testing.
TERMINAL
npm run build
npm startThe server starts at http://localhost:3000 and its MCP endpoint is /mcp. MONEI does not host it for you: run it on a host you control and use that address wherever the client setup says <YOUR_SERVER_URL>/mcp (http://localhost:3000/mcp when the client is on the same machine).
MCP Clients
Claude.ai
server URL: https://your-domain.com/mcp
The configuration on this page does not set MONEI_CLIENT_ID, MONEI_CLIENT_SECRET and MONEI_API_KEY; the project's instructions put them in a .env file. Check which folder the server reads that file from before you rely on it.
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"monei": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"<YOUR_SERVER_URL>/mcp"
]
}
}
}The configuration on this page does not set MONEI_CLIENT_ID, MONEI_CLIENT_SECRET and MONEI_API_KEY; the project's instructions put them in a .env file. Check which folder the server reads that file from before you rely on it.
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add monei --transport http <YOUR_SERVER_URL>/mcpThe configuration on this page does not set MONEI_CLIENT_ID, MONEI_CLIENT_SECRET and MONEI_API_KEY; the project's instructions put them in a .env file. Check which folder the server reads that file from before you rely on it.
