Cloud · MODEL CONTEXT PROTOCOL
lmcmz flow mcp server
Model Context Protocol (MCP) server for Flow blockchain with direct RPC communication
WHAT IT CONNECTS
What lmcmz flow mcp server gives an AI Agent
- Balance checking for Flow and fungible tokens
- Domain resolution for `.find` and `.fn` domains
- Script execution for reading blockchain data
- Transaction submission and monitoring
- Account information retrieval
- Flow configuration based on environment variables
- `PORT` - HTTP port to listen on (if not set, defaults to stdio mode)
- `FLOW_NETWORK` - Flow network to connect to (mainnet, testnet, emulator)
- `FLOW_ACCESS_NODE` - Custom Flow access node URL
- `LOG_LEVEL` - Logging level (debug, info, warn, error)
- `/sse` - Server-Sent Events endpoint for real-time updates
- `/messages` - POST endpoint for sending tool requests
- `/health` - Health check endpoint
- `/` - Server information
- `get_balance` - Get Flow balance for an address
- `get_token_balance` - Get fungible token balance
- `get_account` - Get account information
- `resolve_domain` - Resolve a .find or .fn domain to an address
- `execute_script` - Execute a Cadence script
- `send_transaction` - Send a transaction to the blockchain
- `get_transaction` - Get transaction details by ID
- **v0.1.1** - Bug fix for formatArguments import issue in transaction service
- **v0.1.0** - Initial release with basic Flow blockchain integration
SECURITY
An MCP listing is not a security review
An MCP server may receive model context, credentials, local files, or permission to call external systems. Review its code, requested environment variables, network behavior, package provenance, and maintenance status before connecting it to an agent.