Default
HashKey MCP connector
The HashKey connector brings HashKey market data, futures positions, balances, withdrawals and whitelisted wallets into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, with each person signed in as themselves and every call logged.
- Connects with an API key
- Free 14-day trial
- No credit card
What is the current funding rate on BTC perpetuals?
Working in HashKey with Elaichi
-
List all HashKey whitelist verifies
-
HashKey market data get exchange info
-
HashKey market data get depth
How to connect HashKey to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
HashKey MCP connector for 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.
HashKey MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
HashKey MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
HashKey MCP connector for 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.
HashKey MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with HashKey through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in HashKey is logged.
-
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”
What connecting HashKey gets you
6 screens from Elaichi, each doing one job for your HashKey account.
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, Cursor or Microsoft Copilot
The agent
Ask HashKey questions in plain language.
Positions, funding rates and prices answered from live HashKey records, not a stale export.
Copy the endpoint
AI apps
HashKey in every client through one endpoint.
Claude, ChatGPT, Cursor and Microsoft Copilot share one governed HashKey endpoint, no SDK and no shared API key.
Tool catalog
103 HashKey tools, ready without writing code.
Market data, futures, withdrawals and whitelists covered, with no connector code to build.
Toolboxes
Each team gets its own HashKey toolbox.
Trading reads positions, treasury raises withdrawals, and research keeps to market data.
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.
Audit log
Every HashKey withdrawal names the person behind it.
When, who, what happened and which resource, logged for every HashKey call.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
HashKey digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
HashKey
Queued
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 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%
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.
For IT and engineering
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.
| 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 | Free for one person; $15 per user per month on Gold. | 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.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting actions like withdrawals for a role, 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 restricting account withdraws, fiat withdraws and wallet signing. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot, 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 of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot