Connect via MCP

hodlflow runs a remote Model Context Protocol server. Add it to your AI client and ask questions in plain language; the assistant calls hodlflow for you.

Server URL	https://mcp.hodlflow.app
Transport	Streamable HTTP
Sign-in	OAuth with your Google account. No API key needed.

Only accounts with access can sign in: get access first. MCP calls draw on the same daily budget as the HTTP API.

Claude

claude.ai and Claude Desktop

1. Open Settings → Connectors and choose Add custom connector.
2. Enter the name hodlflow and the URL https://mcp.hodlflow.app, then add it.
3. Choose Connect. A browser window opens: sign in with your enrolled e-mail.
4. In a chat, make sure hodlflow is turned on in the tools menu.

Custom connectors need a paid Claude plan. On Team and Enterprise plans an owner may need to allow custom connectors first.

Claude Code

claude mcp add --transport http hodlflow https://mcp.hodlflow.app

Then run /mcp inside Claude Code, pick hodlflow and choose Authenticate. Your browser opens for the e-mail sign-in.

ChatGPT

1. Open Settings → Apps & Connectors → Advanced settings and turn on Developer mode.
2. Back in Apps & Connectors, choose Create.
3. Enter the name hodlflow, the MCP server URL https://mcp.hodlflow.app, and OAuth as the authentication.
4. Save, then sign in with your enrolled e-mail when the browser asks.
5. In a chat, add hodlflow from the tools menu.

ChatGPT’s menu names and the plans that offer developer mode change from time to time. If a step does not match what you see, look for the option to add a custom MCP connector.

Local clients

Clients that run on your computer complete the sign-in by redirecting your browser to a localhost address on the same machine. Keep the client running until the browser says you are signed in.

Cursor

Add to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "hodlflow": { "url": "https://mcp.hodlflow.app" }
  }
}

Cursor shows a Needs login prompt for hodlflow under MCP settings; choose it to sign in.

VS Code

Add to .vscode/mcp.json in your workspace, or run MCP: Add Server from the command palette:

{
  "servers": {
    "hodlflow": { "type": "http", "url": "https://mcp.hodlflow.app" }
  }
}

VS Code asks you to allow the sign-in, then opens the browser.

Other clients (mcp-remote)

A client that only starts local (stdio) servers can reach hodlflow through mcp-remote, a small proxy that runs on your machine and handles the sign-in. It needs Node.js 18 or later.

{
  "mcpServers": {
    "hodlflow": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.hodlflow.app"]
    }
  }
}

The first start opens the browser for sign-in. mcp-remote keeps the session in ~/.mcp-auth; delete that folder to sign in again from scratch.

To test the connection without an assistant, run the MCP Inspector, choose Streamable HTTP, enter https://mcp.hodlflow.app and connect:

npx @modelcontextprotocol/inspector

Tools

Tool	What it does
meta	Coverage, your limits and the budget left. Ask the assistant to call it first.
guide	The full usage rules, written for AI assistants.
get_result	Reads parts of a large answer by result_id and a JSON Pointer such as /rows.
bitcoin_resolve, bitcoin_addr, bitcoin_utxo, bitcoin_tx, bitcoin_cluster, bitcoin_neighbors, bitcoin_topk, bitcoin_trace, bitcoin_info	Bitcoin commands
ethereum_resolve, ethereum_neighbors, ethereum_topk, ethereum_trace, ethereum_reach, ethereum_annotate, ethereum_info	Ethereum commands
tron_resolve, tron_neighbors, tron_topk, tron_trace, tron_reach, tron_annotate, tron_info	Tron commands
zcash_resolve, zcash_addr, zcash_utxo, zcash_tx, zcash_cluster, zcash_neighbors, zcash_topk, zcash_trace, zcash_info	Zcash commands

Tool arguments are the options in the API Reference, written in snake_case (time-start becomes time_start). An answer over about 20,000 characters comes back as a digest with a result_id; the assistant reads the rest with get_result. Stored answers last 24 hours and only you can read yours.

Example prompts

• “Call hodlflow meta, then show the top 20 USDT senders to TQtaugi3vfFuqxp8KCQUTyXDc6Smk1pYDJ with full addresses.”
• “Trace the USDT that left <address> after block <block> for 4 hops and tell me which exchanges it reached. Say whether the totals are complete.”
• “Show the Bitcoin cluster of <address> and its 10 largest counterparties.”
• “List the ten largest ETH senders to <0x address> last week, with amounts in ETH, not wei.”

Troubleshooting

What you see	What to do
The tools answer that the e-mail is not enrolled	This Google account has no access yet. Get access with the same account.
The browser never returns to the client after sign-in	Local clients listen on localhost for the redirect. Keep the client open, allow local connections in your firewall, and retry.
Tools stop working with an authorization error	The session expired. Reconnect or authenticate again from the client’s MCP settings.
quota_exhausted	Your daily budget or input limit is used up. It resets at 00:00 UTC.
pool_exhausted	Your tier’s shared time for today is used up. It resets at 00:00 UTC; ask for the advanced tier on the API keys page if you need more.
deadline or guard	The query was too wide. Ask for a time window, fewer hops or a smaller k.

Agents that run without a browser cannot complete the Google sign-in. Use the HTTP API with an API key instead.