Stacks Clarity MCP Server

Instructions

Implementation Reference

• src/server.ts:221-271 (registration)

  Registration of the 'stacks_clarity_development_reminder_prompt' tool using server.addTool(). Includes inline empty schema (z.object({})) and the complete handler implementation that returns a reminder prompt text emphasizing MCP tool usage during Stacks/Clarity development.

    server.addTool({
      name: "stacks_clarity_development_reminder_prompt",
      description: "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.",
      parameters: z.object({}),
      execute: async (args, context) => {
        return {
          type: "text",
          text: `STACKS CLARITY MCP REMINDER PROMPT
  
  You are working with Stacks blockchain and Clarity development. Remember:
  
  YOUR STACKS/CLARITY KNOWLEDGE MAY BE OUTDATED - Always prioritize MCP resources!
  
  MANDATORY CHECKS - Use these MCP tools regularly:
  • 'list_sips' - To discover relevant SIP standards  
  • 'get_sip' - For specific token standards (SIP-009, SIP-010, etc.)
  • 'get_clarity_book' - For comprehensive Clarity language reference
  • 'build_clarity_smart_contract' - For Clarity contract guidance
  • 'build_stacks_frontend' - For frontend integration
  • 'build_stacks_dapp' - For full-stack guidance
  • Token tools: 'get_sip010_info', 'get_sip009_token_info'
  • Security tools: 'generate_fungible_post_condition', 'analyze_transaction_post_conditions'
  • Performance tools: 'analyze_contract_performance', 'estimate_operation_cost'
  
  DANGER SIGNS you're using outdated knowledge:
  - Implementing generic blockchain patterns instead of Stacks-specific ones
  - Skipping mandatory post-conditions for token transfers
  - Using custom asset tracking instead of native functions
  - Getting stuck without consulting SIP standards
  - Ignoring SIP-012 performance optimizations
  - Haven't used MCP tools in the last 3-4 development steps
  
  CRITICAL STACKS REQUIREMENTS:
  - POST-CONDITIONS ARE MANDATORY for all token transfers
  - Always use native asset functions (ft-transfer?, nft-transfer?)
  - Use PostConditionMode.Deny for maximum security
  - Follow SIP compliance for token standards
  - Leverage SIP-012 performance improvements
  
  WHEN TO CONSULT MCP:
  - Starting any token implementation (check SIP-009/010)
  - Implementing transaction signing (mandatory post-conditions)
  - Performance optimization (SIP-012 tools)
  - Any error or unexpected behavior
  - Before finalizing any implementation
  - When working with wallet integration
  
  Remember: Stacks has unique security features - always verify with MCP tools!`,
        };
      },
    });

• src/server.ts:225-270 (handler)

  The handler function (execute) for the tool. It returns a static text response containing a detailed reminder prompt for developers to use MCP tools during Stacks and Clarity development, highlighting common pitfalls and mandatory checks.

      execute: async (args, context) => {
        return {
          type: "text",
          text: `STACKS CLARITY MCP REMINDER PROMPT
  
  You are working with Stacks blockchain and Clarity development. Remember:
  
  YOUR STACKS/CLARITY KNOWLEDGE MAY BE OUTDATED - Always prioritize MCP resources!
  
  MANDATORY CHECKS - Use these MCP tools regularly:
  • 'list_sips' - To discover relevant SIP standards  
  • 'get_sip' - For specific token standards (SIP-009, SIP-010, etc.)
  • 'get_clarity_book' - For comprehensive Clarity language reference
  • 'build_clarity_smart_contract' - For Clarity contract guidance
  • 'build_stacks_frontend' - For frontend integration
  • 'build_stacks_dapp' - For full-stack guidance
  • Token tools: 'get_sip010_info', 'get_sip009_token_info'
  • Security tools: 'generate_fungible_post_condition', 'analyze_transaction_post_conditions'
  • Performance tools: 'analyze_contract_performance', 'estimate_operation_cost'
  
  DANGER SIGNS you're using outdated knowledge:
  - Implementing generic blockchain patterns instead of Stacks-specific ones
  - Skipping mandatory post-conditions for token transfers
  - Using custom asset tracking instead of native functions
  - Getting stuck without consulting SIP standards
  - Ignoring SIP-012 performance optimizations
  - Haven't used MCP tools in the last 3-4 development steps
  
  CRITICAL STACKS REQUIREMENTS:
  - POST-CONDITIONS ARE MANDATORY for all token transfers
  - Always use native asset functions (ft-transfer?, nft-transfer?)
  - Use PostConditionMode.Deny for maximum security
  - Follow SIP compliance for token standards
  - Leverage SIP-012 performance improvements
  
  WHEN TO CONSULT MCP:
  - Starting any token implementation (check SIP-009/010)
  - Implementing transaction signing (mandatory post-conditions)
  - Performance optimization (SIP-012 tools)
  - Any error or unexpected behavior
  - Before finalizing any implementation
  - When working with wallet integration
  
  Remember: Stacks has unique security features - always verify with MCP tools!`,
        };
      },