Skip to content

Default

HashKey MCP connector

The HashKey connector brings HashKey market data, futures positions, balances, withdrawals and whitelisted wallets into Claude, ChatGPT, Cursor and the Elaichi Agent, with each person signed in as themselves and 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 HashKey to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect HashKey once

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

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

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

hashkey
HashKey
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.

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

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

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

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

  • Trading

    Check positions and funding before the open

    Ask for your open HashKey futures positions, current leverage and the funding rate on each contract, and get one plain answer instead of switching between screens.

  • Treasury

    Move funds to a whitelisted wallet

    Confirm which HashKey wallets are already whitelisted, then raise an account withdraw or a fiat withdraw to one of them without leaving the conversation.

  • Risk

    Watch leverage and liquidation status

    Pull leverage, risk limits and liquidation assign status across HashKey futures accounts and get a flag when a position drifts toward its limit.

  • Research

    Pull price history for a report

    Request klines, 24 hour tickers, mark price and index price for any HashKey pair and have the agent summarize the move in a paragraph you can paste into a note.

  • Finance

    Reconcile balances and commission rates

    Read HashKey futures balances alongside the commission rate on each account so month-end reconciliation starts from live numbers rather than a screenshot.

  • Compliance

    Review whitelist verifications and withdrawals

    List every HashKey whitelist verification and see who raised each withdraw, with the Elaichi audit log naming the person behind every request.

Try asking

  • “What is the current funding rate on BTC perpetuals?”
  • “Show our open HashKey futures positions and leverage”
  • “Summarize the 24 hour ticker for ETH against its mark price”

See all 103 HashKey tools below

Compare

Elaichi vs Zapier MCP vs Composio for HashKey

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

HashKey tools for your AI agents

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

See it in Elaichi

What connecting HashKey gets you

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

The agent

Ask HashKey questions in plain language.

Positions, funding rates and prices answered from live HashKey records, not a stale export.

  • positions
  • withdrawals
  • trades
  • funding rates

Ask Elaichi to work across your apps.

What is the current funding rate on BTC perpetuals?

Show our open HashKey futures positions and leverage

Summarize the 24 hour ticker for ETH against its mark price

Also runs in Claude, ChatGPT or Cursor

MCP clients

HashKey in every client through one endpoint.

Claude, ChatGPT and Cursor share one governed HashKey endpoint, 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

103 HashKey tools, ready without writing code.

Market data, futures, withdrawals and whitelists covered, with no connector code to build.

  • List all HashKey whitelist verifies
  • Create a HashKey account withdraw
  • Create a HashKey fiat withdraw
  • Create a HashKey whitelist wallet signing
ElaichiTools
Tool Action Description
List all HashKey whitelist verifies List Get a micro-payment depositing address for whitelist verification in HashKey. Returns: site, topic, params, data. Required: coin, chainType, quantity. For the same coin, chainType, and walletId, specifying the same quantity always produces the same deposit random amount (micropayment). The signAddress parameter is only needed for signature verification, not for micropayment verification.
Create a HashKey account withdraw Create Submit a digital asset withdrawal request on Hashkey. Returns: success, id, orderId, site, topic, params, data. Required: coin, quantity, address, chainType, clientOrderId. The withdrawal address must be whitelisted in advance via the Hashkey website or app.
Create a HashKey fiat withdraw Create Create a fiat withdrawal in HashKey. Returns the withdrawal order including orderId, asset, grossAmount, netAmount, fee, status, channel, and clientOrderId. A 2FA token is required when two-factor authentication is enabled for the account; each token is valid for 30 seconds and single-use.
Create a HashKey whitelist wallet signing Create Verify a wallet address for whitelisting in HashKey via signature challenge. Returns: site, topic, params, data. Required: coin, chainType, fromAddress, signPhrase, signResult, walletId, timestamp.
HashKey market data get exchange info Get Get current exchange trading rules and symbol information from HashKey. Returns: data, topic. Each item in data includes symbol, productType, buyMakerFeeCurrency, buyTakerFeeCurrency, sellMakerFeeCurrency, sellTakerFeeCurrency, actualMakerRate, and actualTakerRate.

Toolboxes

Each team gets its own HashKey toolbox.

Trading reads positions, treasury raises withdrawals, and research keeps to market data.

  • Trading
  • Treasury
  • Risk
  • Research
ElaichiToolboxes
Name Source template Tools Created

Trading toolbox

HashKey · positions and funding rates

HashKey starter 18 Mar 4, 2026

Treasury toolbox

HashKey · withdrawals and whitelisted wallets

— 9 Mar 2, 2026

Risk toolbox

HashKey · leverage and liquidation status

— 24 Feb 27, 2026

Research toolbox

HashKey · klines and tickers

HashKey starter 6 Feb 19, 2026

Finance toolbox

HashKey · balances and commission rates

— 31 Jan 30, 2026

Compliance toolbox

HashKey · whitelist verifications and withdrawal records

— 12 Jan 22, 2026

Shared connections

Teammates use HashKey without seeing the key.

One person connects HashKey, shares it, and the API key stays out of everyone's hands.

  • Trading desk
  • Treasury
  • Risk
  • Research
ElaichiConnections
Connection Scope Status Access
HA

HashKey (Trading desk)

Connected by Emily Carter

Personal • Active 1 team · 6 members
HA

HashKey (Treasury)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
HA

HashKey (Risk)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
HA

HashKey (Research)

Connected by Tyler Reed

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

HashKey (Finance ops)

Connected by Ryan Hayes

Personal • Active Not shared
HA

HashKey (Compliance)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every HashKey withdrawal names the person behind it.

When, who, what happened and which resource, logged for every HashKey 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

HashKey Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

HashKey Positions Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

HashKey Positions 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 runs the HashKey funding digest.

Positions and funding rates are fetched, grouped, drafted, approved by a person, then posted to HashKey.

HashKey digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch positions

    HashKey

    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

    HashKey

    Queued

Collections and dashboards

HashKey activity reported without asking anyone.

Fourteen days of HashKey trades and withdrawals by team, refreshed on a schedule, no model involved.

HashKey health

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

Live

Positions

1,284 ↓ 12%

Withdrawals

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Positions created

Last 14 days

By team

Share of activity

Trading desk 34%

Treasury 27%

Risk 21%

Research 18%

FAQ

Frequently asked questions

How do I connect HashKey to Claude?

Connect HashKey in Elaichi first: paste the API key from your HashKey account and Elaichi holds it for you. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate, so the whole thing takes a few minutes.

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

Yes. Once HashKey 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 HashKey once and every client sees it.

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

With HashKey connected, an agent can read order book depth, recent trades, klines, tickers, mark and index prices and coin details, and it can report your futures positions, balances, leverage, funding rates and risk limits. It can also list whitelisted wallets and raise account or fiat withdrawals if you allow that. HashKey exposes a lot of tools, so short concrete asks such as "funding rate on BTC perpetuals" work better than long paragraphs.

Does connecting HashKey give the AI access to my whole exchange account?

No. Access follows the HashKey API key of the person who connected, so the agent can only do what that key already permits in HashKey. Elaichi can narrow that further by hiding actions like withdrawals from a team, but it can never widen what HashKey itself allows.

Can my team share one HashKey connection?

Yes. One person connects HashKey in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so every HashKey call in the audit log carries their own name.

Can I stop an agent from making withdrawals or changing things in HashKey?

Yes. Restrictions in Elaichi work per action, so you can allow market data and positions from HashKey while blocking account withdraws, fiat withdraws and wallet signing. A blocked action is never shown to Claude, ChatGPT or Cursor at all, so no prompt can reach it.

What happens to a HashKey connection when someone leaves?

Offboarding that person in Elaichi ends their access to HashKey at once, across every client they used. A HashKey connection they shared keeps working for everyone else on the team. If you want HashKey gone entirely, disconnecting it once in Elaichi removes it from every client.

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

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

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

How is Elaichi different from Composio for HashKey?

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

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