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.
In Elaichi
Connect HashKey once
-
Open Connections, choose Add connection, and pick HashKey.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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 HashKey to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect HashKey to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect HashKey to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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”
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.
No tools match your search.
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.
Copy the endpoint
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
Toolboxes
Each team gets its own HashKey toolbox.
Trading reads positions, treasury raises withdrawals, and research keeps to market data.
- Trading
- Treasury
- Risk
- Research
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
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
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 Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch positions
HashKey
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
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
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%
Related connectors
More from the catalog
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 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.
Put HashKey in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.