MoveFlow Aptos MCP Server

What is MoveFlow Aptos MCP Server?

A Model Context Protocol (MCP) server that enables AI assistants to interact with the MoveFlow protocol on the Aptos blockchain. It provides a standardized interface for AI tools to create, manage, and interact with cryptocurrency streaming payments.

How to use MoveFlow Aptos MCP Server?

Install via npm (npx @moveflow/aptos-mcp-server) or clone the repository, install dependencies, build, and start with environment variables like APTOS_NODE_URL, APTOS_NETWORK, and READ_ONLY_MODE. Integrate with AI assistants (e.g., Claude Desktop, Cline) by adding the server configuration. Use available MCP tools like create-stream, withdraw-stream, and get-stream-info via natural language commands.

Key features of MoveFlow Aptos MCP Server

• Full MCP compatibility for tool discovery and input validation
• Stream management: create, withdraw, close, extend, pause, resume
• Batch operations: create or withdraw from multiple streams at once
• Multiple security modes: read-only, client-side signing, direct signing
• Self-documenting API with standardized schema validation
• Resource URIs for listing active streams and stream details

Use cases of MoveFlow Aptos MCP Server

• AI assistants automating recurring cryptocurrency payments on Aptos
• Creating and managing multiple payment streams in a single transaction
• Querying stream status and balances without executing transactions
• Securely integrating payment streaming into chatbot or agent workflows
• Testing and developing MoveFlow interactions using MCP tools

FAQ from MoveFlow Aptos MCP Server

What does read-only mode do?

It allows only querying blockchain data (e.g., stream info) and prevents any transaction execution. Enable with READ_ONLY_MODE="true".

How are private keys handled?

The server avoids storing private keys. In default client-side signing mode, transactions are prepared but not signed; client applications handle signing. Direct signing mode (for testing) requires APTOS_PRIVATE_KEY.

What are the required environment variables?

APTOS_NODE_URL and APTOS_NETWORK are required. READ_ONLY_MODE, SIGNING_MODE, and APTOS_PRIVATE_KEY are optional depending on the mode.

Which networks are supported?

mainnet, testnet, devnet, and local. Set via APTOS_NETWORK. For test/dev networks, an optional APTOS_FAUCET_URL can be provided.

How do I integrate with Cline?

Configure a server file (e.g., moveflow-aptos.json) in ~/Documents/Cline/MCP or use natural language commands within Cline to set up the tool.