tron_mcp_server: Instructions file for Claude Code

CLAUDE.md Template for TRON MCP Server Integration

This document explains how to create an effective CLAUDE.md file for projects that use the TRON MCP Server. The CLAUDE.md file helps AI assistants understand your project context and use the TRON blockchain features effectively.

What is CLAUDE.md?

CLAUDE.md is a special markdown file that Claude reads when working with your codebase. It provides project-specific context, guidelines, and instructions that help Claude understand your project's requirements and conventions.

Basic Template

Here's a template you can customize for your project:

# Project Name

## Overview
Brief description of your project and its relationship to TRON blockchain.

## TRON Integration

### MCP Server Configuration
This project uses the TRON MCP server for blockchain operations. When working with TRON:
- Always use the `tron` MCP server for blockchain queries
- Never make assumptions about gas costs - use `estimate_energy` first
- Check balances before attempting transactions

### Network Configuration
- Network: mainnet/shasta/nile
- Primary operations: [list main blockchain operations your project uses]

### Smart Contracts
List important contracts your project interacts with:
- USDT: TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t (6 decimals)
- Custom Contract: TXxxxxx... - Description

### Common Operations

#### Checking Balances
When asked about balances, use:

get_balance with address parameter

#### Estimating Energy
Before any contract interaction:

estimate_energy with contract address and function details

#### Sending Transactions
For TRX transfers:

send_trx with recipient and amount

## Project-Specific Guidelines

### Error Handling
- Always check if address is valid TRON format (starts with T)
- Handle insufficient balance errors gracefully
- Monitor energy consumption for contract calls

### Security Considerations
- Private keys are managed via environment variables
- Never log or display private keys
- Always validate user input addresses

### Testing
- Use Shasta testnet for development
- Test addresses: [list test addresses if any]

## Code Style
[Your project's coding standards]

## Common Tasks

### Task 1: Check User Balance
1. Get address from user
2. Validate address format
3. Use `get_balance` tool
4. Display in user-friendly format

### Task 2: Send USDT
1. Check USDT balance first
2. Estimate energy required
3. Ensure sufficient TRX for fees
4. Execute transfer
5. Return transaction hash

## Troubleshooting

### Common Issues
1. "Insufficient Energy" - User needs to freeze TRX or rent energy
2. "Invalid Address" - Check if address starts with 'T' and is 34 characters
3. "Transaction Failed" - Check fee limit and contract parameters

## Resources
- TRON Documentation: https://developers.tron.network/
- TronScan Explorer: https://tronscan.org/
- Project Repository: [your repo URL]