HashPilot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEDERA_NETWORK | Yes | Network to use: testnet, mainnet, or previewnet | |
| OPENAI_API_KEY | No | Required for documentation search and code generation (RAG features) | |
| HEDERA_OPERATOR_ID | Yes | Your Hedera account ID (e.g., 0.0.12345) | |
| HEDERA_OPERATOR_KEY | Yes | Your private key in hex format |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Check HashPilot MCP server health and status. Returns version, tool count, and optimization level. |
| account_createA | Create a new Hedera account with customizable parameters. CREATES: New account with auto-generated ECDSA key pair (or use provided public key) FUNDS: Initial HBAR balance from operator account RETURNS: Account ID, private key, public key, transaction ID USE FOR: Creating new accounts for testing, development, or production workflows. COSTS: Network fee + initial balance (minimum 1 HBAR recommended) |
| account_balanceA | Query HBAR and token balances for any Hedera account. RETURNS: HBAR balance in ℏ format, list of all associated token balances FREE: No transaction fee (Mirror Node query) USE FOR: Checking account balances, monitoring funds, verifying token holdings. |
| account_infoA | Get comprehensive Hedera account information. RETURNS: Balance, EVM address, public key, memo, auto-renew period, expiration FREE: No transaction fee (Mirror Node query) USE FOR: Account inspection, EVM address lookup, key verification, expiration monitoring. |
| transfer_hbarA | Transfer HBAR between Hedera accounts. EXECUTES: CryptoTransfer transaction from source to destination REQUIRES: Operator account must be source OR have signing authority COSTS: Standard network transaction fee USE FOR: Funding accounts, payments, moving HBAR between wallets. |
| network_infoA | Get current Hedera network configuration. RETURNS: Network name, Mirror Node URL, JSON-RPC Relay endpoint USE FOR: Verifying active network, getting endpoint URLs, network status. |
| network_switchA | Switch between Hedera networks seamlessly. NETWORKS: mainnet (production), testnet (testing), previewnet (preview), local (development) UPDATES: All SDK connections, Mirror Node URLs, RPC endpoints automatically USE FOR: Multi-network development, testing across environments, production deployment. |
| token_manageA | Comprehensive Hedera Token Service (HTS) management. Execute ANY token operation through a single unified interface. OPERATIONS:
USE THIS FOR: All token lifecycle management, compliance operations, supply control, and transfer operations. REQUIRES: Operator account with appropriate keys (admin/supply/freeze/kyc/wipe/pause) based on operation. |
| addressbook_manageA | Manage Hedera account address book for multi-account workflows. OPERATIONS:
USE THIS FOR: Managing multiple accounts, organizing workflows, quick account reference. |
| state_manageA | Manage HashPilot MCP server state through backup/restore/export operations. OPERATIONS:
USE THIS FOR: State persistence, migration, disaster recovery, debugging. |
| hcs_topicB | Hedera Consensus Service (HCS) topic management. OPERATIONS:
USE THIS FOR: Creating consensus topics, configuring topic settings, real-time message streams. |
| hcs_messageA | Hedera Consensus Service (HCS) message operations. OPERATIONS:
USE THIS FOR: Publishing messages, retrieving consensus-ordered data, auditable logs. |
| rpc_callA | Execute ANY JSON-RPC method on Hedera's JSON-RPC Relay. SUPPORTS: 55+ methods including eth_*, web3_*, net_*, debug_* EXAMPLES: eth_blockNumber, eth_getBalance, eth_call, eth_getLogs, eth_sendRawTransaction DECODES: Results automatically converted to human-readable format USE FOR: EVM-compatible operations, blockchain state queries, transaction submission. |
| rpc_call_contractA | Call read-only smart contract function via eth_call (FREE - no gas cost). EXECUTES: View/pure function on deployed contract DECODES: Return values using provided ABI FREE: No transaction fee, no state changes USE FOR: Reading contract state, querying balances, checking conditions. |
| rpc_deploy_contractA | Deploy smart contract to Hedera via JSON-RPC. HANDLES: Bytecode deployment, constructor encoding, gas estimation, receipt polling RETURNS: Contract address, transaction hash, deployment details COSTS: Gas fees for contract creation AUTO-KEY: privateKey is OPTIONAL - automatically uses MCP operator account if not provided USE FOR: Deploying Solidity contracts to Hedera EVM. |
| rpc_execute_contractA | Execute state-changing contract function via eth_sendRawTransaction. EXECUTES: Transaction that modifies contract state HANDLES: Function encoding, signing, gas estimation, receipt polling COSTS: Gas fees for execution RETURNS: Transaction hash, receipt, decoded logs AUTO-KEY: privateKey is OPTIONAL - automatically uses MCP operator account if not provided USE FOR: Token transfers, contract interactions, state modifications. |
| docs_searchA | Semantic search across complete Hedera documentation. INDEXED: Official docs, SDK references (JS/Java/Go/Rust/Python), tutorials, HIPs, service specs RETURNS: Ranked results with titles, URLs, excerpts, relevance scores FILTERS: By content type (tutorial/api/concept/example), language, code presence USE FOR: Finding specific documentation, discovering relevant tutorials, locating API references. |
| docs_askA | Answer ANY knowledge question about Hedera using RAG. HANDLES: Conceptual (what is X?), how-to (how do I?), comparison (X vs Y), troubleshooting, best practices, architecture, security RETURNS: Comprehensive answer with code examples and source citations EXPERTISE: Adjustable for beginner/intermediate/advanced levels USE FOR: Learning Hedera concepts, getting implementation guidance, understanding best practices. THIS IS YOUR PRIMARY TOOL FOR HEDERA KNOWLEDGE QUESTIONS. |
| docs_get_exampleA | Find working code examples for Hedera functionality. SEARCHES: SDK examples, tutorials, implementation patterns RETURNS: Annotated code with explanations and source references LANGUAGES: JavaScript, TypeScript, Java, Python, Go, Rust, Solidity USE FOR: Getting implementation code, learning patterns, finding SDK usage. |
| code_generateA | Generate context-aware Hedera SDK code from natural language. CREATES: Complete, runnable code with imports, error handling, best practices LANGUAGES: JavaScript, TypeScript, Java, Python, Go, Solidity STYLES: minimal (core logic), complete (with setup), production (full best practices) USE FOR: Creating new implementations, generating boilerplate, scaffolding projects. |
| deploy_contractA | Deploy smart contract to Hedera with unified interface. AUTO-DETECTS: Hardhat or Foundry project framework SUPPORTS: Constructor arguments, gas limits, auto-verification TRACKS: Deployment history with metadata USE FOR: Production contract deployment, automated workflows, verified deployments. |
| verify_contractA | Verify smart contract on HashScan block explorer. METHODS: Direct source upload, Hardhat build-info, Foundry artifacts RETURNS: Verification status and HashScan URL USE FOR: Contract transparency, code verification, public auditability. |
| deployment_historyB | View deployment history with filtering and export. FILTERS: By network, contract name, status EXPORTS: JSON, CSV, or Markdown format USE FOR: Tracking deployments, auditing, documentation. |
| mirror_query_accountA | Query comprehensive account data from Hedera Mirror Node REST API. RETURNS: Balance, EVM address, creation time, keys, memo, transactions (optional) FREE: No transaction fees (REST API query) USE FOR: Account inspection, transaction history, state verification. |
| hardhat_projectB | Manage Hardhat project lifecycle operations. OPERATIONS:
USE FOR: Project setup, compilation, testing, and configuration management. |
| hardhat_contractA | Manage Hardhat contract deployment and interaction. OPERATIONS:
AUTO-RESOLUTION: Deployment automatically uses MCP operator account credentials. No need to set TESTNET_PRIVATE_KEY manually. USE FOR: Contract deployment, verification, and interaction. |
| foundry_projectA | Manage Foundry project lifecycle operations. OPERATIONS:
USE FOR: Project setup, dependencies, compilation, and gas optimization. |
| foundry_contractA | Manage Foundry contract testing, deployment, and interaction. OPERATIONS:
AUTO-RESOLUTION: privateKey and rpcUrl are OPTIONAL - if not provided, automatically uses MCP operator account configuration. USE FOR: Testing, deployment, gas analysis, and local development. |
| stablecoin_manageA | Enterprise-grade stablecoin management via Hedera Stablecoin Studio. OPERATIONS:
FEATURES:
AUTO-CONFIG: Uses MCP operator account for SDK authentication. USE FOR: Institutional stablecoin issuance, compliance workflows, token lifecycle management. |
| error_explainA | Explain Hedera error codes and provide debugging guidance. USE FOR:
EXAMPLES:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 30 tools
The tool set has clear distinct purposes for most tools, but there is significant overlap in some areas. For example, 'deploy_contract', 'rpc_deploy_contract', 'hardhat_contract', and 'foundry_contract' all handle contract deployment with different frameworks, which could confuse an agent about which to use. Similarly, 'docs_ask', 'docs_get_example', and 'docs_search' all serve documentation purposes but have overlapping use cases. Descriptions help differentiate them, but the boundaries are not always clear.
Most tools follow a consistent verb_noun pattern (e.g., 'account_balance', 'token_manage', 'network_switch'), which is predictable and readable. However, there are minor deviations like 'health_check' (noun_verb) and 'foundry_contract' (adjective_noun) that break the pattern slightly. Overall, the naming is largely consistent with only a few inconsistencies that do not severely impact usability.
With 30 tools, the count feels excessive for a single server, leading to potential confusion and overlap. While Hedera is a broad domain, the server includes tools for documentation, code generation, project management, and multiple deployment frameworks, which could be better scoped into separate servers. This many tools may overwhelm agents and increase the risk of misselection due to the high number of similar functionalities.
The tool surface is highly complete for the Hedera domain, covering account management, token operations, smart contract deployment (across multiple frameworks), consensus services, network operations, and documentation. It includes CRUD/lifecycle coverage for key resources like accounts, tokens, and contracts, with no obvious gaps. Tools like 'stablecoin_manage' and 'hcs_topic' provide specialized functionalities that enhance coverage, making the set well-rounded for agent workflows.