Server Configuration
Describes the environment variables required to run the server.
Name | Required | Description | Default |
---|---|---|---|
HIRO_API_KEY | No | Optional API key for enhanced features and higher rate limits from Hiro platform | |
STACKS_NETWORK | No | The Stacks network to use (mainnet, testnet, or devnet) | testnet |
Schema
Prompts
Interactive templates invoked by user choice
Name | Description |
---|---|
No prompts |
Resources
Contextual data attached and managed by the client
Name | Description |
---|---|
No resources |
Tools
Functions exposed to the LLM to take actions
Name | Description |
---|---|
get_sip010_balance | Get the SIP-010 fungible token balance for a specific address. Returns the balance in base units (consider decimals for display). |
get_sip010_info | Get complete information about a SIP-010 fungible token including name, symbol, decimals, total supply, and metadata URI. |
generate_sip010_transfer | Generate a SIP-010 fungible token transfer transaction with proper post-conditions. Returns the transaction parameters for wallet signing. |
generate_sip010_template | Generate a complete, production-ready SIP-010 fungible token contract template with all security features and best practices. |
get_sip009_token_info | Get complete information about a specific SIP-009 NFT including owner, metadata URI, and actual metadata content. |
get_sip009_collection_info | Get information about a SIP-009 NFT collection including total supply and last token ID. |
generate_sip009_transfer | Generate a SIP-009 NFT transfer transaction with proper post-conditions. Returns the transaction parameters for wallet signing. |
generate_sip009_template | Generate a complete, production-ready SIP-009 NFT contract template with all security features and optional marketplace functionality. |
generate_fungible_post_condition | Generate a fungible token post-condition for SIP-010 tokens. Post-conditions are MANDATORY for all token transfers. |
generate_non_fungible_post_condition | Generate a non-fungible token post-condition for SIP-009 NFTs. Post-conditions are MANDATORY for all NFT transfers. |
generate_stx_post_condition | Generate an STX post-condition for STX transfers. Essential for payment and fee transactions. |
analyze_transaction_post_conditions | Analyze a contract call to determine what post-conditions are required for security. Essential for complex transactions. |
generate_post_condition_template | Generate a complete post-condition template for common transaction patterns with security best practices. |
analyze_contract_performance | Analyze a Clarity contract for performance bottlenecks and SIP-012 optimization opportunities. Provides detailed cost breakdown and optimization recommendations. |
estimate_operation_cost | Estimate the computational cost of specific Clarity operations based on SIP-012 cost functions. Useful for planning contract optimization. |
generate_optimization_recommendations | Generate specific optimization recommendations for Clarity contracts based on SIP-012 improvements and best practices. |
get_stacks_account_info | Get comprehensive information about a Stacks account including STX balance, nonce, tokens, and recent activity. |
check_stx_balance | Check the STX balance for a Stacks address. Simple and fast balance lookup. |
get_transaction_history | Get detailed transaction history for a Stacks address with pagination support. |
validate_stacks_address | Validate a Stacks address format and check if it's correctly formatted for the specified network. |
generate_clarinet_project | Generate a complete Clarinet project setup with proper structure, configuration, and starter contracts. |
generate_clarity_contract | Generate a complete Clarity contract with SIP compliance, security best practices, and comprehensive functionality. |
generate_contract_tests | Generate comprehensive test suites for Clarity contracts including unit tests, integration tests, and security tests. |
configure_clarinet_project | Configure Clarinet project settings for different networks, add dependencies, and set up development environment. |
get_mcp_version | Returns the version of the MCP server |
list_sips | Get a list of all available SIPs (Stacks Improvement Proposals) in the knowledge base. Use this first to discover available Stacks standards. |
get_sip | Get the complete content of a specific SIP (Stacks Improvement Proposal) by number, including any Clarity smart contract code. |
get_clarity_book | Get the complete Clarity Book - comprehensive Clarity language documentation covering all language features, syntax, and best practices. |
get_token_standards | Get the essential token standards for Stacks - SIP-009 (NFT) and SIP-010 (Fungible Token) complete with Clarity trait definitions and implementation guidance. |
search_sips | Search through all SIPs for content matching a specific query. Useful for finding standards related to specific topics. |
build_clarity_smart_contract | Build a Clarity smart contract - returns comprehensive resources for Clarity development including SIP standards, security patterns, and best practices. Use this tool when you need guidance on building smart contracts for Stacks. |
build_stacks_frontend | Build a Stacks dApp frontend - returns comprehensive resources for frontend development including wallet integration, transaction signing, and post-condition handling. Use this tool when you need guidance on building frontends for Stacks dApps. |
build_stacks_dapp | Build a complete full-stack Stacks dApp - returns comprehensive resources covering Clarity contracts, frontend integration, token standards, and security patterns. Use this tool when you need guidance on building complete Stacks applications. |
stacks_clarity_best_practices_prompt | PRIMARY PROMPT: Use this as the main system prompt when building any Stacks dApp or Clarity contract. Sets up mandatory MCP consultation workflow for Stacks development and ensures SIP compliance. |
stacks_clarity_development_reminder_prompt | MID-DEVELOPMENT REMINDER: Use this prompt when you notice the conversation has gone few exchanges without using MCP tools, or when implementing new Stacks features to reinforce MCP consultation habits. |
stacks_debugging_helper_prompt | ERROR RECOVERY PROMPT: Use this immediately when encountering Stacks/Clarity errors, stuck in debugging loops, or when about to try generic blockchain solutions. Redirects to MCP-first debugging approach. |