Skip to content

Banking

Depasify MCP connector

The Depasify connector brings accounts, balances, ledgers, settlements, and identity checks into Claude, ChatGPT, Cursor, and the Elaichi Agent, so each person can look up and act on Depasify records within their own access, with every call 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 Depasify to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Depasify once

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

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

  3. Paste a Depasify API key. One person generates a token in Depasify 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.

depasify
Depasify
1Password
360learning
7shifts
Acquire
Active Ants
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.

Depasify 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.

Depasify 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.

Depasify 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 Depasify 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 Depasify through Elaichi

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

  • Finance

    Check a balance before approving a payout

    Ask for a customer's current Depasify balance and recent ledger entries before a withdrawal goes out, then send the withdrawal from the same conversation once you are satisfied.

  • Compliance

    Review and close an identity check

    Pull up a customer's identification record, see where the check stands, update it with what the documents show, and close it or start a fresh identity process when something does not add up.

  • Onboarding

    Open accounts for a batch of new customers

    Create Depasify accounts from a list of new clients, run a light identity check on each, and update the whole batch at once when a shared detail changes.

  • Treasury

    Move funds between internal accounts

    Create an internal settlement between two Depasify accounts and confirm it appears in the ledger, without opening the Depasify console.

  • Support

    Explain a fee to a customer

    Look up the trading fees and SEPA fees applied to a customer's Depasify account so the reply you send is accurate, and adjust the SEPA fees if a correction has been agreed.

  • Accounting

    Pull month-end ledger reports

    Ask for a PDF or CSV ledger report for a Depasify account and pass it to the bookkeeper, or link a blockchain payment to the right account so the ledger matches.

Try asking

  • “Show the balance on every Depasify account today.”
  • “List SEPA fees across our Depasify accounts.”
  • “Pull the latest Depasify ledger PDF report.”

See all 83 Depasify tools below

Compare

Elaichi vs Zapier MCP vs Composio for Depasify

All three can connect Depasify 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 Depasify, 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 Depasify tools Allow or restrict single Depasify 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 Depasify 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

Depasify tools for your AI agents

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

See it in Elaichi

What connecting Depasify gets you

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

The agent

Ask about accounts, get real balances.

Plain language questions answered from live Depasify accounts, ledgers and balances.

  • accounts
  • ledgers
  • balances
  • withdrawals

Ask Elaichi to work across your apps.

Show the balance on every Depasify account today.

List SEPA fees across our Depasify accounts.

Pull the latest Depasify ledger PDF report.

Also runs in Claude, ChatGPT or Cursor

MCP clients

One Depasify endpoint for every client.

Claude, ChatGPT and Cursor connect over OAuth, with no SDK or shared 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

83 Depasify tools ready to call.

Accounts, ledgers, balances, withdrawals and fees, with no custom code to write.

  • Create a Depasify session
  • List all Depasify accounts
  • Create a Depasify account
  • Get single Depasify account by ID
ElaichiTools
Tool Action Description
Create a Depasify session Create Sign in to the Depasify API to obtain a JWT bearer token for authenticating subsequent API calls. Returns: token, openapi, info, servers, paths, components, x-readme. Required: email, password. For 2FA-enabled accounts, include otp_attempt and otp_secret on re-submission after the initial OTP challenge. Token expires after 1 month.
List all Depasify accounts List List all Depasify accounts accessible to the authenticated user, including main and client-facing accounts. Returns: id, referral, status, alias, created_at, balance, status_verification, complete_name, identification_external_uuid, identification_uuid.
Create a Depasify account Create Create a new Depasify account linked to an existing Identification. Provide either the identification uuid or an external id shared between your services. Returns: id, referral, status, alias, created_at, balance, status_verification, complete_name, identification_external_uuid, identification_uuid, openapi, info, servers, paths, components, x-readme.
Get single Depasify account by ID Get Get detailed information about a specific Depasify account by id. Returns: id, referral, status, alias, created_at, balance, status_verification, complete_name, identification_external_uuid, identification_uuid, openapi, info, servers, paths, components, x-readme. Required: id.
Update a Depasify account by ID Update Update an existing Depasify account's alias, referral code, or linked identification. Returns: id, referral, status, alias, created_at, balance, status_verification, complete_name, identification_external_uuid, identification_uuid, openapi, info, servers, paths, components, x-readme. Required: id.

Toolboxes

Every team gets its own toolbox.

Curate Depasify toolboxes per team so treasury and support see different tools.

  • Treasury
  • Finance
  • Operations
  • Compliance
ElaichiToolboxes
Name Source template Tools Created

Treasury toolbox

Depasify · balances and withdrawals

Depasify starter 18 Mar 4, 2026

Finance toolbox

Depasify · ledgers and reports

— 9 Mar 2, 2026

Operations toolbox

Depasify · accounts and sessions

— 24 Feb 27, 2026

Compliance toolbox

Depasify · ledger entries and audit

Depasify starter 6 Feb 19, 2026

Trading toolbox

Depasify · trading fees and payments

— 31 Jan 30, 2026

Support toolbox

Depasify · account lookups and balances

— 12 Jan 22, 2026

Shared connections

Share Depasify accounts, never the credential.

See who connected each account and which teams and members work through it.

  • Treasury EMEA
  • Finance
  • Operations
  • Compliance
ElaichiConnections
Connection Scope Status Access
DE

Depasify (Treasury EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
DE

Depasify (Finance)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
DE

Depasify (Operations)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
DE

Depasify (Compliance)

Connected by Tyler Reed

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

Depasify (Trading Desk)

Connected by Ryan Hayes

Personal • Active Not shared
DE

Depasify (Support)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every withdrawal traces back to a person.

When, who, what happened, type and resource for each Depasify call.

  • 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

Depasify Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Depasify Accounts Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Depasify Accounts 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 ships.

Fetch Depasify ledgers, group them, draft a digest, approve, post it back.

Depasify digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch accounts

    Depasify

    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

    Depasify

    Queued

Collections and dashboards

Depasify balances counted, not asked for.

Four metrics, 14 days of accounts created and a team breakdown, refreshed on schedule.

Depasify health

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

Live

Accounts

1,284 ↓ 12%

Ledgers

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Accounts created

Last 14 days

By team

Share of activity

Treasury EMEA 34%

Finance 27%

Operations 21%

Compliance 18%

FAQ

Frequently asked questions

How do I connect Depasify to Claude?

Connecting Depasify to Claude takes two steps. In Elaichi, choose Depasify and paste in the API key from your Depasify account; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi as yourself, and Depasify is ready.

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

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

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

With Depasify connected, you can ask for an account's balance, its ledger entries, or a PDF or CSV ledger report, and ask which trading and SEPA fees apply to it. You can open new Depasify accounts, update them one at a time or in bulk, send a withdrawal, create an internal settlement, link a blockchain payment, and review, update, or close a customer's identity check. Because Depasify offers a lot of actions, short concrete asks such as "show the balance for account 4471" work better than long paragraphs.

Does connecting Depasify give the AI access to every account and ledger?

No. Every request to Depasify runs inside the access of the person who signed in, so the AI sees only the accounts, ledgers, settlements, and identifications that person could already reach in Depasify. Elaichi can narrow that access further for a team or a role, and it can never widen it beyond what Depasify itself allows.

Can my team share one Depasify connection?

Yes. One person connects Depasify in Elaichi and shares the connection with a team, and nobody else ever handles the Depasify API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every balance check, withdrawal, or identity update.

Can I stop an agent from sending withdrawals or changing accounts in Depasify?

Yes. Restrictions in Elaichi work per action, so you can allow reading Depasify balances and ledgers while blocking withdrawals, account updates, fee changes, or closing an identification. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client at all, so no prompt, however worded, can reach it.

What happens to a Depasify connection when someone leaves?

When you offboard a person in Elaichi, their access to Depasify through every client ends at once. A Depasify connection they shared with a team keeps working for everyone else on that team. If you ever want Depasify gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client in the same step.

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

Yes. Depasify 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 Depasify?

Yes. Both let Claude, ChatGPT or Cursor use Depasify. 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 Depasify call.

How is Elaichi different from Composio for Depasify?

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 Depasify: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Depasify 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.