How deseti/mcp-moni works
Project type and purpose
• MCP Moni is a backend‐only, TypeScript-based MCP (Model Context Protocol) server that exposes blockchain tooling to AI assistants (e.g., Claude Desktop).
• Its purpose is to handle natural-language and JSON requests from an AI client, translate those into blockchain operations on the Monad testnet (via Viem and the Monad SDK), and return results or execute transactions.
File structure
• Top level:
• package.json / package-lock.json: Node.js project metadata
• tsconfig.json: TypeScript compiler configuration
• .env.example: environment variables template (private key, RPC_URL, CHAIN_ID)
• src/: TypeScript source
• src/index.ts: entry point that spins up the MCP server and registers tools
• src/config.ts & config.d.ts: loads and validates environment variables
• src/utilities.ts: helper functions shared across tools
• src/nft/: NFT-related tools (index.ts ties together types.ts and utils.ts)
• src/staking.ts, src/swap.ts, src/wrapUnwrap.ts: individual modules for staking, swapping, wrapping/unwrapping MON
• src/transfer.ts (embedded in swap? or implicitly in utilities) and src/staking.ts handle token transfers and liquid staking
• No frontend/UI: purely a modular service
README for additional insights
• Confirms components: MCP server, Viem library, Monad SDK
• Lists 20+ “tools” (get-mon-balance, execute-transfer, generate-nft-image, etc.)
• Describes flow: Claude Desktop → MCP Moni → blockchain testnet
• No database or caching layer mentioned
Detail & essential elements
• Tool module is individually represented, or group by domain with sub-labels
• That all private keys and signing happen locally (config → Viem signer)
• MCP adapter layer that parses natural-language/JSON into module invocations
• Don’t over-fragment: show logical groupings rather than every single TypeScript file