Skip to content

Dwolla MCP connector

The Dwolla connector lets Claude, ChatGPT, Cursor, and other MCP clients look up and update Dwolla customers, funding sources, transfers, and beneficial owner records inside each person's own Dwolla access, with every call audited.

  • How it connects. App credentials. 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 Dwolla to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Dwolla once

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

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

  3. Paste your Dwolla app credentials. Dwolla authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

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

Add connection

Choose a connector.

dwolla
Dwolla
Airwallex
Cashfree Payments
ChargeDesk
Chimoney
Circle
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.

Dwolla MCP connector for 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.

Dwolla MCP connector for 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.

Dwolla MCP connector for 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 Dwolla 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 Dwolla through Elaichi

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

  • Finance

    Check where a transfer stands

    Ask for the transfers on a Dwolla account and see which ones are pending, processed, or failed without opening the dashboard.

  • Operations

    Onboard a new customer in Dwolla

    Create the Dwolla customer record from the details in a signup form, then attach the identity document they sent over.

  • Compliance

    Verify beneficial owners for a business

    List the beneficial owners on a Dwolla business customer, add or correct one, upload their document, and certify ownership when the set is complete.

  • Support

    Fix a customer's bank details

    Pull up a Dwolla customer's funding sources, confirm which bank account is linked, and rename or update one after a call.

  • Treasury

    Review mass payments before reconciliation

    List the mass payments run from your Dwolla account and match them against the payout schedule for the month.

  • Onboarding

    Pick the right business classification

    Search Dwolla's business classifications to find the correct category and industry code before creating a business customer.

Try asking

  • “List failed Dwolla transfers from the last seven days.”
  • “Which customers have no verified funding source yet?”
  • “Summarize this week's mass payments by receiving customer.”

See all 82 Dwolla tools below

Compare

Elaichi vs Zapier MCP vs Composio for Dwolla

All three can connect Dwolla to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Dwolla, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Dwolla tools Allow or restrict single Dwolla tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Dwolla call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Dwolla tools for your AI agents

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

See it in Elaichi

What connecting Dwolla gets you

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

The agent

Ask about transfers, get live answers.

Plain language questions run against Dwolla customers, transfers and funding sources.

  • customers
  • transfers
  • funding sources
  • mass payments

Ask Elaichi to work across your apps.

List failed Dwolla transfers from the last seven days.

Which customers have no verified funding source yet?

Summarize this week's mass payments by receiving customer.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Dwolla.

One org 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

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

82 Dwolla tools ready to call.

Customers, transfers, funding sources, mass payments and beneficial owners, no custom code.

  • Create a Dwolla funding source
  • List all Dwolla funding sources
  • Get single Dwolla funding source by ID
  • Update a Dwolla funding source by ID
ElaichiTools
Tool Action Description
Create a Dwolla funding source Create Create a funding source for a Dwolla Main Account by connecting a checking or savings bank account using either manual account details or an exchange resource. Returns the newly created funding source.
List all Dwolla funding sources List List all funding sources associated with a specific Dwolla Main Account, including bank accounts and balance sources. Returns status, type, and available processing channel details for each source. Required: account_id.
Get single Dwolla funding source by ID Get Get detailed information about a specific Dwolla funding source by id. Returns type, status, and verification details; debit card sources additionally include masked brand, last four digits, expiration date, and cardholder name.
Update a Dwolla funding source by ID Update Update or remove a Dwolla funding source by id. Allows renaming at any status; routing number, account number, and account type can only be changed while unverified. Setting removed to true soft-deletes the source.
List all Dwolla account transfers List List and search transfers for a Dwolla Main account. Returns a list of transfer objects filterable by amount range, date range, transfer status, and correlation ID. Required: account_id. Results are capped at 10,000 transfers per query; use date range filters to retrieve historical data beyond this limit.

Toolboxes

Every team gets its own toolbox.

Finance, Treasury and Support each see a curated set of Dwolla tools.

  • Finance
  • Treasury
  • Payments Ops
  • Compliance
ElaichiToolboxes
Name Source template Tools Created

Finance toolbox

Dwolla · transfers and settlement

Dwolla starter 18 Mar 4, 2026

Treasury toolbox

Dwolla · funding sources and balances

— 9 Mar 2, 2026

Payments Ops toolbox

Dwolla · mass payments and retries

— 24 Feb 27, 2026

Compliance toolbox

Dwolla · beneficial owners and verification

Dwolla starter 6 Feb 19, 2026

Support toolbox

Dwolla · customer records and transfer status

— 31 Jan 30, 2026

Engineering toolbox

Dwolla · webhooks and sandbox accounts

— 12 Jan 22, 2026

Shared connections

Teammates move money without holding keys.

See who connected each Dwolla account and which teams and members use it.

  • Finance US
  • Treasury
  • Payments Ops
  • Compliance
ElaichiConnections
Connection Scope Status Access
DW

Dwolla (Finance US)

Connected by Emily Carter

Personal • Active 1 team · 6 members
DW

Dwolla (Treasury)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
DW

Dwolla (Payments Ops)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
DW

Dwolla (Compliance)

Connected by Tyler Reed

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

Dwolla (Support)

Connected by Ryan Hayes

Personal • Active Not shared
DW

Dwolla (Sandbox)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every Dwolla call is on the record.

When, who, what happened, type and resource, appended and never edited.

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

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Dwolla Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Dwolla Customers Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Dwolla Customers 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 drafts your transfer digest.

Six steps fetch Dwolla transfers, group them, draft, wait for approval, then post back.

Dwolla digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch customers

    Dwolla

    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

    Dwolla

    Queued

Collections and dashboards

Dwolla numbers are waiting when you arrive.

Four metrics, 14 days of transfers created and a team breakdown, computed on schedule.

Dwolla health

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

Live

Customers

1,284 ↓ 12%

Transfers

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Customers created

Last 14 days

By team

Share of activity

Finance US 34%

Treasury 27%

Payments Ops 21%

Compliance 18%

FAQ

Frequently asked questions

How do I connect Dwolla to Claude?

Connect Dwolla in Elaichi first, where you sign in with your Dwolla app credentials. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude signs you in through Elaichi and Dwolla is available in your next conversation.

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

Yes. Once Dwolla 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 Dwolla once and every client picks it up.

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

With Dwolla connected, an agent can look up customers, create or update a customer, list and update funding sources, and review the transfers and mass payments on your Dwolla accounts. It can also manage beneficial owners, upload customer and owner documents, certify beneficial ownership, and search business classifications. Because Dwolla has many actions, short direct asks such as "list funding sources for customer Acme" work better than long paragraphs.

Does connecting Dwolla give the AI access to everything in my account?

No. Every call to Dwolla runs inside the access of the person who signed in, so an agent sees only the Dwolla customers, funding sources, and transfers that person can already see. Elaichi can narrow that further by turning off specific actions, but it can never grant more than the person's own Dwolla access allows.

Can my team share one Dwolla connection?

Yes. One person connects Dwolla in Elaichi and shares the connection with a team, and nobody else ever handles the Dwolla credentials. Each teammate still signs in to Elaichi as themselves, so the audit log records exactly who created a customer or updated a funding source in Dwolla.

Can I stop an agent from deleting or changing things in Dwolla?

Yes. Restrictions in Elaichi apply per action, so you can allow looking up Dwolla customers and transfers while blocking updates, document uploads, or deleting a beneficial owner. A blocked action is never advertised to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.

What happens to a Dwolla connection when someone leaves?

Offboarding a person in Elaichi ends their access to Dwolla and every other connected application at once, in every client they used. A Dwolla connection shared with a team keeps working for everyone else on it. If you want Dwolla gone entirely, disconnecting it once in Elaichi removes it from every client.

Does the Dwolla MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Dwolla is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Dwolla?

Yes. Both let Claude, ChatGPT or Cursor use Dwolla. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Dwolla call.

How is Elaichi different from Composio for Dwolla?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Dwolla: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Dwolla in front of your team

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

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.