stacks-clarity

Stacks Clarity MCP Server provides a comprehensive toolkit for Stacks development, focused on Clarity smart contracts, SIP compliance, security post-conditions, and performance optimization. It exposes a suite of 32 tools spanning SIP standards discovery, token (FT/NFT) development, security post-conditions, SIP-012 performance guidance, account management, testing helpers, Clarinet project support, and frontend development guidance. Users can query available SIPs, inspect token information, generate compliant transfer templates, analyze post-conditions, and obtain performance recommendations. Integration with Cursor or Claude Code allows you to run these tools directly from your development environment, enabling rapid prototyping and secure contract deployments. The server is designed to assist both token authors and dApp developers by providing ready-made templates, validation utilities, and guidance aligned with SIP standards and security best practices.

Prerequisites:

• Node.js and npm (npm ≥ 5.2.0)
• Clarinet CLI for contract development
• Stacks wallet for frontend integration
• Cursor IDE or Claude Code for MCP integration (optional but recommended)

Install and set up:

1. Clone the repository and install dependencies

git clone https://github.com/YOUR_USERNAME/stacks-clarity-mcp.git
cd stacks-clarity-mcp
npm install

2. Build the project (required before running the MCP server)

npm run build

3. Run or integrate with MCP tooling

• If using the published package, you can reference it via npx as shown in the Quick Setup example.
• If developing locally, ensure your build artifacts are accessible to the runtime (the dist/ output is generated by the build step).

4. Optional: Set up Cursor/Claude Code integration

• Create a Cursor MCP config at .cursor/mcp.json with the appropriate command and environment variables as described in the integration guides.

Note: After cloning, you should run npm install and npm run build before attempting to run the MCP server.

Environment and configuration tips:

• STACKS_NETWORK can be mainnet, testnet, or devnet depending on your environment.
• HIRO_API_KEY is optional but can unlock higher rate limits and enhanced features; obtain it from platform.hiro.so and add it to your config.
• The MCP config uses the server key stacks-clarity-mcp; you can customize the key to match your project naming conventions in your Cursor config.
• Ensure you build before running to generate dist/ assets; runtime tools expect the built output when invoking the MCP server.
• If you encounter issues, verify Node.js version compatibility with the MCP package and confirm that environment variables are properly passed to the runtime.
• Refer to integration_guides/ for Cursor, Claude Code, and development setup specifics.