flow -monorepo

This MCP monorepo bundles two Flow-focused MCPs. The flow-mcp package provides core tools for interacting with the native Flow blockchain, including account management, balance checks, and native contract interactions. The flow-defi-mcp package focuses on DeFi and EVM-compatible interactions on Flow, covering tasks such as token price checks, token swaps on DEXs, and ERC20 token interactions. To work with these MCPs, install the monorepo dependencies and run the respective MCP tools via your preferred MCP runner (for example using npx as configured above). Each package exposes a set of commands/tools designed to be composable for scripting and automation.

Prerequisites:

• Node.js (recommended LTS) and npm/yarn/pnpm
• Git

Step-by-step:

1. Clone the repository: git clone <repository-url>
2. Navigate to the project root: cd path/to/flow-mcp-monorepo
3. Install dependencies for all packages (monorepo setup assumed):
   • If you use pnpm: pnpm install
   • If you use npm: npm install
   • If you use yarn: yarn install
4. (Optional) Bootstrap or link local packages if your workflow requires it (for example pnpm workspaces or yarn workspaces):
   • pnpm -i
   • yarn install
5. Run an MCP tool from the monorepo (examples):
   • Flow MCP tool: npx -y flow-mcp <command> [options]
   • Flow DeFi MCP tool: npx -y flow-defi-mcp <command> [options]
6. If the monorepo uses scripts, you can often invoke build/test independently from each package's folder, e.g.: cd packages/flow-mcp && npm run build cd ../flow-defi-mcp && npm run build

Notes:

• This is a monorepo containing two MCPs for Flow: core Flow interactions and DeFi/EVM-related flows.
• The exact package names used with npx may vary if the monorepo publishes packages with different npm names. If you publish locally, replace the npx targets with the appropriate local package identifiers.
• For monorepos using workspaces, ensure your tooling supports workspace hoisting and that dependencies are installed at the root.
• If you encounter permission errors on macOS/Linux, run with appropriate permissions or adjust your npm/pnpm/yarn configuration.
• Check each package's README.md for package-specific tools, CLI options, and environment variable requirements.