Stacks Clarity MCP Server
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 |
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 |
|---|---|
| get_sip010_balanceB | Get the SIP-010 fungible token balance for a specific address. Returns the balance in base units (consider decimals for display). |
| get_sip010_infoB | Get complete information about a SIP-010 fungible token including name, symbol, decimals, total supply, and metadata URI. |
| generate_sip010_transferB | Generate a SIP-010 fungible token transfer transaction with proper post-conditions. Returns the transaction parameters for wallet signing. |
| generate_sip010_templateB | Generate a complete, production-ready SIP-010 fungible token contract template with all security features and best practices. |
| get_sip009_token_infoB | Get complete information about a specific SIP-009 NFT including owner, metadata URI, and actual metadata content. |
| get_sip009_collection_infoC | Get information about a SIP-009 NFT collection including total supply and last token ID. |
| generate_sip009_transferB | Generate a SIP-009 NFT transfer transaction with proper post-conditions. Returns the transaction parameters for wallet signing. |
| generate_sip009_templateB | Generate a complete, production-ready SIP-009 NFT contract template with all security features and optional marketplace functionality. |
| generate_fungible_post_conditionA | Generate a fungible token post-condition for SIP-010 tokens. Post-conditions are MANDATORY for all token transfers. |
| generate_non_fungible_post_conditionA | Generate a non-fungible token post-condition for SIP-009 NFTs. Post-conditions are MANDATORY for all NFT transfers. |
| generate_stx_post_conditionB | Generate an STX post-condition for STX transfers. Essential for payment and fee transactions. |
| analyze_transaction_post_conditionsB | Analyze a contract call to determine what post-conditions are required for security. Essential for complex transactions. |
| generate_post_condition_templateC | Generate a complete post-condition template for common transaction patterns with security best practices. |
| analyze_contract_performanceC | Analyze a Clarity contract for performance bottlenecks and SIP-012 optimization opportunities. Provides detailed cost breakdown and optimization recommendations. |
| estimate_operation_costB | Estimate the computational cost of specific Clarity operations based on SIP-012 cost functions. Useful for planning contract optimization. |
| generate_optimization_recommendationsC | Generate specific optimization recommendations for Clarity contracts based on SIP-012 improvements and best practices. |
| get_stacks_account_infoB | Get comprehensive information about a Stacks account including STX balance, nonce, tokens, and recent activity. |
| check_stx_balanceB | Check the STX balance for a Stacks address. Simple and fast balance lookup. |
| get_transaction_historyB | Get detailed transaction history for a Stacks address with pagination support. |
| validate_stacks_addressB | Validate a Stacks address format and check if it's correctly formatted for the specified network. |
| generate_clarinet_projectC | Generate a complete Clarinet project setup with proper structure, configuration, and starter contracts. |
| generate_clarity_contractC | Generate a complete Clarity contract with SIP compliance, security best practices, and comprehensive functionality. |
| generate_contract_testsC | Generate comprehensive test suites for Clarity contracts including unit tests, integration tests, and security tests. |
| configure_clarinet_projectC | Configure Clarinet project settings for different networks, add dependencies, and set up development environment. |
| get_mcp_versionB | Returns the version of the MCP server |
| list_sipsA | Get a list of all available SIPs (Stacks Improvement Proposals) in the knowledge base. Use this first to discover available Stacks standards. |
| get_sipA | Get the complete content of a specific SIP (Stacks Improvement Proposal) by number, including any Clarity smart contract code. |
| get_clarity_bookB | Get the complete Clarity Book - comprehensive Clarity language documentation covering all language features, syntax, and best practices. |
| get_token_standardsA | Get the essential token standards for Stacks - SIP-009 (NFT) and SIP-010 (Fungible Token) complete with Clarity trait definitions and implementation guidance. |
| search_sipsB | Search through all SIPs for content matching a specific query. Useful for finding standards related to specific topics. |
| build_clarity_smart_contractA | 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_frontendA | 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_dappA | 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_promptA | 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_promptB | 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_promptA | 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. |
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 36 tools
Most tools have distinct purposes, but there is some overlap in generation and analysis tools. For example, generate_clarity_contract and generate_sip009_template both create contracts, though one is generic and the other specific. Similarly, analyze_contract_performance and generate_optimization_recommendations both focus on optimization, which could cause confusion. However, descriptions help differentiate them, and most tools target unique resources or actions.
Tool names follow a highly consistent verb_noun pattern throughout, such as analyze_contract_performance, check_stx_balance, and generate_sip009_template. There are no deviations in naming conventions, with all tools using snake_case and clear, descriptive verbs. This predictability makes it easy for agents to understand and select tools.
With 36 tools, the count is excessive for the server's purpose of Stacks Clarity development and management. Many tools could be consolidated or removed without losing functionality, such as multiple generate_* tools or prompt tools. This large number may overwhelm agents and lead to inefficiency, indicating a poor scope management.
The tool set provides comprehensive coverage for Stacks Clarity development, including contract analysis, generation, testing, token standards (SIP-009/010), transaction handling, balance checks, and debugging. There are no obvious gaps; it supports full CRUD/lifecycle operations for contracts and tokens, along with essential utilities like address validation and version checking.