Skip to content

Payment Gateway

NMI MCP connector

Connect NMI to Claude, ChatGPT, Cursor or any MCP client through Elaichi, and your team can look up payments, issue refunds, send invoices and manage subscriptions and plans by asking in plain language, with every action logged.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect NMI to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect NMI once

  1. Open Connections, choose Add connection, and pick NMI.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a NMI API key. One person generates a token in NMI and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

nmi
NMI
Chimoney
Circle
Dwolla
Finexio
Flutterwave
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect NMI to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect NMI to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect NMI to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect NMI to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with NMI through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Finance

    Look up a payment before answering a query

    Pull up a single NMI transaction by its ID to check the amount, card details and status before replying to a customer or the bank.

  • Support

    Refund or void a charge on the spot

    When a customer calls about a duplicate charge, void it if it has not settled or refund it if it has, without leaving the conversation.

  • Accounts receivable

    Draft, send and close invoices

    Create an invoice in NMI from the details in an email, send it to the customer, then close it once payment arrives.

  • Billing

    Pause or change a customer's subscription

    Find a customer's recurring subscription in NMI and update the amount, schedule or plan when their contract changes, or cancel it when they leave.

  • Operations

    Set up and tidy recurring plans

    Create new pricing plans, list the ones already in NMI, and retire plans nobody is on anymore.

  • Sales

    Authorize a card, capture later

    Run an authorization on a new customer's card to confirm it is good, then capture the payment once the order ships.

Try asking

  • “List all NMI invoices still open past due date.”
  • “Refund the NMI payment on invoice 4821.”
  • “Show yesterday's declined NMI sales by amount.”

See all 68 NMI tools below

AI tools

NMI tools for your AI agents

68 tools are ready to call through Elaichi's MCP endpoint the moment you connect NMI, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting NMI gets you

6 screens from the product, each doing one job for your NMI account.

The agent

Ask in plain language, answer from NMI.

Starter prompts pull live NMI payments, invoices and refunds into a straight answer.

  • payments
  • invoices
  • refunds
  • authorizations

Ask Elaichi to work across your apps.

List all NMI invoices still open past due date.

Refund the NMI payment on invoice 4821.

Show yesterday's declined NMI sales by amount.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach NMI.

One org-wide MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

68 NMI tools, no custom code.

Sales, auths, captures, voids, refunds and invoices are cataloged and ready to call.

  • NMI payments sale
  • NMI payments auth
  • NMI payments credit
  • NMI payments validate
ElaichiTools
Tool Action Description
NMI payments sale Action Process a sale transaction in NMI — an authorization and capture in a single step. Pay with raw card details, an ACH bank account, a Collect.js payment_token, or a stored customer via customer_vault_id. Amounts are decimal strings (e.g. 10.00). Returns the transaction result including id, status, response (1 approved / 2 declined / 3 error), auth_code and response_text. Required: amount and a payment_details variant.
NMI payments auth Action Process an authorization for a payment in NMI, to be used in conjunction with the capture endpoint to prepare the payment for settlement. Returns: transaction_id, condition, transaction_type, requested_amount, currency, authorization_code.
NMI payments credit Action Process a credit in NMI without a prior payment, crediting funds directly to the customer's payment method. Returns: merchant, features, transaction_id, transaction_type, condition, processor_id, ponumber, order_description, order_id, customerid, customertaxid, website, shipping, currency, tax, surcharge, convenience_fee, misc_fee, misc_fee_name, cash_discount, tip, requested_amount,…
NMI payments validate Validate Validate a payment method in NMI without processing a payment. Returns the validation result including transaction_id, transaction_type, condition, response_code, and response_text.
NMI payments capture Action Capture a previously authorized payment in NMI. Returns the transaction object including transaction_id, condition, currency, requested_amount, and an action block with amount, action_type, success, response_code, and response_text. Required: payment_id.

Toolboxes

Every team gets its own NMI toolbox.

Finance keeps invoices, support keeps refunds, each toolbox scoped to one team.

  • Finance
  • Support
  • Billing operations
  • Sales
ElaichiToolboxes
Name Source template Tools Created

Finance toolbox

NMI · invoices and settlements

NMI starter 18 Mar 4, 2026

Support toolbox

NMI · refunds and voids

9 Mar 2, 2026

Billing operations toolbox

NMI · recurring charges and captures

24 Feb 27, 2026

Sales toolbox

NMI · payment links and invoices

NMI starter 6 Feb 19, 2026

Risk toolbox

NMI · declines and chargebacks

31 Jan 30, 2026

Engineering toolbox

NMI · auth and capture testing

12 Jan 22, 2026

Shared connections

Teammates charge cards without seeing credentials.

Each NMI connection shows who connected it and which teams and members share it.

  • Finance
  • Support EMEA
  • Billing ops
  • Risk review
ElaichiConnections
Connection Scope Status Access
NM

NMI (Finance)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
NM

NMI (Support EMEA)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
NM

NMI (Billing ops)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
NM

NMI (Risk review)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
NM

NMI (Sales US)

Connected by Clara Nowak

Personal • Active Not shared
NM

NMI (Sandbox)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every refund has a name against it.

When, who, what happened, type and resource for each NMI call, append-only.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

NMI Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

NMI Payments Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

NMI Payments List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires, a digest posts back.

Six steps fetch NMI transactions, group them, draft a digest, then wait for approval.

NMI digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch payments

    NMI

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    NMI

    Queued

Collections and dashboards

NMI settlement numbers, counted not guessed.

Four metrics, fourteen days of transactions and a team breakdown, refreshed on schedule.

NMI health

Refreshed 4 minutes ago · every 15 minutes · from the payments collection

Live

Payments

1,284 ↓ 12%

Invoices

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Payments created

Last 14 days

By team

Share of activity

Finance 34%

Support EMEA 27%

Billing ops 21%

Risk review 18%

FAQ

Frequently asked questions

How do I connect NMI to Claude?

First connect NMI in Elaichi by pasting in an API key from your NMI merchant account, which takes about a minute. Then in Claude go to Customize, then Connectors, then Add, and paste in https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate, so the NMI side is a single key and nothing else.

Does NMI work with ChatGPT and Cursor as well as Claude?

Yes. Once NMI is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect NMI once and every client your team uses picks it up.

What can an AI agent actually do with my NMI data?

With NMI connected, an agent can look up a payment by its ID, run a sale, authorize and capture a card, void or refund a charge, and create, update, send and close invoices. It can also create and update subscriptions and plans, or list what is already there. Because NMI offers a lot of actions, short concrete asks like "refund transaction 12345" work better than long paragraphs.

Does connecting NMI give the AI access to my whole merchant account?

An agent working through NMI in Elaichi can only do what the API key it was connected with allows, and Elaichi can narrow that further but never widen it. Every call runs under the person who signed in to Elaichi, so a support agent's session cannot do more in NMI than that person is permitted to do.

Can my team share one NMI connection?

Yes. One person connects NMI with the API key, shares the connection with a team in Elaichi, and nobody else ever sees or handles the key. Each teammate still signs in to Elaichi as themselves, so every refund or invoice sent through NMI is logged under the name of the person who asked for it.

Can I stop an agent from refunding, voiding or deleting things in NMI?

Yes. In Elaichi you restrict NMI actions one at a time, so you can allow looking up payments and sending invoices while blocking refunds, voids or deleting subscriptions and plans. A blocked action is never shown to Claude, ChatGPT, Cursor or any other client, so no prompt, accidental or otherwise, can reach it.

What happens to a NMI connection when someone leaves?

When you offboard someone in Elaichi, their access to NMI through every connected client ends at once. If they had been using a shared NMI connection, it keeps working for everyone else on the team. If you want to remove NMI entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

Put NMI in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.