Easypaydirect Mcp

io.github.praveendias1180Published by GitHub account praveendias1180v0.1.3Updated Oct 24, 2026

Read-only MCP server for the Easy Pay Direct (EPD) / NMI-family payment gateway Query API.

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Read-only MCP server that lets an assistant query an Easy Pay Direct / NMI-family payment gateway for transactions, subscriptions, plans and vault records.

What you can do
Look up and search transactions by ID, date range, condition, action type, payment type, source, email or order ID. Retrieve and list recurring subscriptions, optionally filtered by created or updated date range. List recurring billing plans, or fetch one by plan ID. Fetch or list stored Customer Vault records, optionally by date range.
When to use it
Useful when you want to ask plain-language questions about your gateway's payment history, such as finding failed transactions for a customer in a given week or checking whether a subscription is still active, without opening the merchant portal.
Requirements
Runs locally over stdio via npx with Node.js 18+, or as a Docker container with stdin kept open. Requires the NMI_SECURITY_KEY environment variable (a read-only security key is recommended) and optionally NMI_API_URL, which defaults to the NMI host and can be set to an EPD or white-label gateway host. Network access to the gateway is needed.
Before you install
The server holds a gateway security key in its environment; use a read-only key and never commit it. It is an unofficial, independent client, not affiliated with Easy Pay Direct or NMI. It is described as read-only and unable to charge, refund, void or modify the vault, but the key itself may carry broader permissions, so scope it carefully.

Installation

In SourceWeft

  1. Open Easypaydirect Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

easypaydirect-mcp

[npm] [CI] [docs] [good first issues] [license: MIT]

📖 Documentation: https://praveendias1180.github.io/easypaydirect-mcp/

Unofficial, read-only Model Context Protocol server for the Easy Pay Direct (EPD) / NMI-family payment gateway.

Give an AI assistant (Claude Desktop, Claude Code, or any MCP client) safe, read-only access to your gateway's transactions, subscriptions, recurring plans, and Customer Vault records — so you can ask questions like "find the failed transactions for this customer last week" or "is this subscription still active?" in plain language.

Easy Pay Direct is built on the NMI / Network Merchants gateway platform, so this server works with any NMI white-label gateway — just point it at your gateway's host. EPD is the headline example, not the limit.

⚠️ Not affiliated with, endorsed by, or sponsored by Easy Pay Direct or NMI. "Easy Pay Direct", "EPD", and "NMI" are trademarks of their respective owners. This is an independent open-source client for their public Query API.

Why read-only?

This server talks only to the gateway's Query API (/api/query.php) — the reporting endpoint. It has no code path to the transaction endpoint (transact.php), so it cannot charge a card, issue a refund, void a transaction, or modify the vault. An LLM connected to this server can look, but it cannot touch money. See docs/security.md.

Write operations may arrive in a future major version — always opt-in, off by default, and loudly gated.

Install & run

Requires Node.js 18+.

bash
# no install needed — run straight from npmnpx easypaydirect-mcp

The server speaks MCP over stdio and expects two environment variables:

VariableRequiredDescription
NMI_SECURITY_KEY✅Your gateway API security key (a read-only key is recommended). Merchant portal → Settings → Security Keys.
NMI_API_URL—Gateway API base URL. Defaults to https://secure.nmi.com. For EPD/white-labels, set this to your gateway's host.

See docs/configuration.md for how to find your key and host.

Run with Docker

No local Node.js needed. Build the image from the repository root, then run it with -i — MCP talks over stdio, so the container needs stdin kept open:

bash
docker build -t easypaydirect-mcp .
docker run --rm -i \  -e NMI_SECURITY_KEY=your_read_only_security_key \  -e NMI_API_URL=https://secure.nmi.com \  easypaydirect-mcp

Or keep the variables in an env file (--env-file .env). .env is already git-ignored — never commit a real key.

Connect it to Claude

Claude Desktop — add to claude_desktop_config.json (see examples/claude-desktop-config.json):

json
{  "mcpServers": {    "easypaydirect": {      "command": "npx",      "args": ["-y", "easypaydirect-mcp"],      "env": {        "NMI_SECURITY_KEY": "your_read_only_security_key",        "NMI_API_URL": "https://secure.nmi.com"      }    }  }}

Claude Code:

bash
claude mcp add easypaydirect \  -e NMI_SECURITY_KEY=your_read_only_security_key \  -e NMI_API_URL=https://secure.nmi.com \  -- npx -y easypaydirect-mcp

To use the Docker image instead, swap the command — a bare -e NAME forwards the variable into the container:

bash
claude mcp add easypaydirect \  -e NMI_SECURITY_KEY=your_read_only_security_key \  -e NMI_API_URL=https://secure.nmi.com \  -- docker run --rm -i -e NMI_SECURITY_KEY -e NMI_API_URL easypaydirect-mcp

Full walkthrough: docs/getting-started.md.

Claude Code plugin (server + skill)

The plugin installs the MCP server and an Agent Skill that teaches Claude how to read gateway data correctly — for example that a successful ACH sale is only submitted, not paid, and that EPD timestamps are UTC.

Set the key in your shell (the plugin reads it from the environment), then install:

bash
export NMI_SECURITY_KEY=your_read_only_security_keyexport NMI_API_URL=https://secure.nmi.com   # optional; your EPD / white-label host
/plugin marketplace add praveendias1180/easypaydirect-mcp/plugin install easypaydirect@easypaydirect-mcp

Using another client? The skill is a plain SKILL.md — add it to any tool that supports Agent Skills.

Tools

All tools are read-only. Full reference in docs/tools.md.

ToolWhat it does
get_transactionFetch one transaction by gateway transaction ID.
search_transactionsSearch transactions by date range + filters (condition, action type, payment type, source, email, order id).
get_subscriptionFetch one recurring subscription by ID.
list_subscriptionsList recurring subscriptions, optionally by created/updated date range.
list_recurring_plansList recurring billing plans (or one by plan_id).
get_customer_vault_recordFetch one stored Customer Vault record by ID.
list_customer_vaultList stored Customer Vault records, optionally by date range.

Develop

bash
git clone https://github.com/praveendias1180/easypaydirect-mcp.gitcd easypaydirect-mcpnpm installnpm run build      # compile TypeScript to dist/npm run typecheck  # type-check only

Local run against the MCP Inspector:

bash
npx @modelcontextprotocol/inspector node dist/index.js

Architecture and how tools map to the Query API: docs/nmi-api-mapping.md.

Roadmap

Planned / under consideration — contributions welcome (see open issues):

  • Tests — unit suite with recorded Query API fixtures (#1)
  • Friendlier dates — accept ISO-8601 in date filters (#2)
  • More filters — merchant-defined fields on search_transactions (#3)
  • Better errors — map NMI response codes to actionable messages (#4)
  • Distribution — publish-on-release automation (#8)
  • Docs — response-field reference (#9)

Read-only stays the default posture — any write support would be a separate, opt-in, gated major version.

See the changelog for released changes.

Contributing

Contributions are welcome — this aims to be a small, dependable, read-only MCP server. See CONTRIBUTING.md for the ground rules and dev setup.

New here? Start with a good first issue — each one has context, a task checklist, file pointers, and acceptance criteria. Have a question? Open a Discussion.

License

MIT © the easypaydirect-mcp contributors.

Source: README.md at commit 0bd2a9d

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.3LatestSep 18, 2026
  2. v0.1.2Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts