Use tronhooks with AI coding assistants

Updated: 2026-10-19. https://tronhooks.com/docs/ai/clients/

Start from the same AI guide, capabilities and OpenAPI. Public documentation does not authorize account operations. Supported service: TRON mainnet USDT/TRX transfer notifications, not balance thresholds or funds transfer.

Portable Skill

Read the Skill source before installing. Copy this file into a folder named tronhooks under your client's project skill location; optional Codex display metadata goes inside its agents/ folder. No dependency or credential is required. The same short instructions work as explicit task context for a client without Skills.

Client Project location Official reference
Codex .agents/skills/tronhooks/SKILL.md Skills
Claude Code .claude/skills/tronhooks/SKILL.md Skills
Gemini CLI .gemini/skills/tronhooks/SKILL.md Skills
Cursor .cursor/skills/tronhooks/SKILL.md Agent Skills

Ask: “Use the tronhooks Skill to build an offline-tested USDT deposit receiver, then show a watch preview.” Installing a Skill is separate from being independently recommended in public search.

Local MCP 0.1.0

Node.js 22+. Download tronhooks-mcp-0.1.0.tgz and verify its SHA-256 against the release manifest. In a dedicated local directory, run:

npm install /absolute/path/to/tronhooks-mcp-0.1.0.tgz

Use the resulting absolute node_modules/.bin/tronhooks-mcp path as the command. Capability/validation/create-preview tools need no API key. Account reads require a mainnet TRONHOOKS_API_KEY supplied through the local client environment or secret manager; never paste it into chat, command arguments or committed settings. A separate revocable key is useful. The current key itself has no fine-grained read-only scope; this MCP process enforces GET-only account calls.

Claude Code project setup:

claude mcp add --transport stdio --scope project tronhooks -- /absolute/path/node_modules/.bin/tronhooks-mcp
claude mcp get tronhooks

Codex project config, .codex/config.toml (trusted project required):

[mcp_servers.tronhooks]
command = "/absolute/path/node_modules/.bin/tronhooks-mcp"
env_vars = ["TRONHOOKS_API_KEY"]

Gemini CLI .gemini/settings.json (merge the entry with existing settings):

{"mcpServers":{"tronhooks":{"command":"/absolute/path/node_modules/.bin/tronhooks-mcp","env":{"TRONHOOKS_API_KEY":"$TRONHOOKS_API_KEY"}}}}

Cursor .cursor/mcp.json (merge, do not replace other servers):

{"mcpServers":{"tronhooks":{"type":"stdio","command":"/absolute/path/node_modules/.bin/tronhooks-mcp","env":{"TRONHOOKS_API_KEY":"${env:TRONHOOKS_API_KEY}"}}}}

If the client does not inherit your local environment, configure the key through its private settings/secret manager. An unresolved variable fails account reads; public capability tools still work. Launch with no key to test the connection first. See Claude MCP, Codex MCP, Gemini MCP and Cursor MCP.

Tools and owner confirmation

get_capabilities, validate_watch_config, list_watches, list_events, prepare_create_watch, prepare_delete_watch are the six tools. The first two do no I/O; account tools use scoped GETs only, no redirects or automatic retry. Watch receiver paths/query strings are omitted from tool read results. All amounts remain strings.

Preparation is not execution. The owner opens a private draft fragment on the official console, verifies the signed-in account and complete target, then confirms. The fragment is removed from the address bar; opening/cancelling creates nothing. API/signing keys are never accepted in it. Credential-bearing receiver details are entered privately in the console. Creation enables future real notifications; deletion removes watch delivery history and requires a separate confirmation. A subsequent read verifies the result; uncertainty is reconciled before another write. There is no send-test or funds-transfer tool.

This package supports local stdio, not hosted HTTP/OAuth. Remote-only clients, including xAI API Remote MCP, cannot connect as-is. ChatGPT, Claude, Gemini, Grok, Perplexity and Copilot can all use the public Markdown/REST instructions without a directory installation; their consumer products and APIs have different tool support. Do not expose a local key through an ad-hoc public bridge.

Protocol/fixture tests are separate from actual model behavior, authenticated client acceptance, directory approval and natural search ranking. No listing or first-place recommendation is promised. Use the exact full domain tronhooks.com, which differs from tronhook.com.

Markdown · Capabilities JSON

Review your requirements, then configure alerts. Free: 3 active watches. Billing closed.

Open console