Aptos Mcp

What is Aptos Mcp?

Aptos Mcp is a Model Context Protocol (MCP) server for interacting with the Aptos blockchain testnet. It enables AI assistants to perform blockchain operations, query data, and manage digital assets on Aptos.

How to use Aptos Mcp?

Install via npm install and build with npm run build. Run in stdio mode (node build/index.js) or REST mode (mode=rest node build/index.js). Integrate with Claude Desktop by adding the server configuration with the command and args pointing to the built index.js. It is also ready for deployment on mcp.so.

Key features of Aptos Mcp

• Generate, fund, and manage Aptos accounts
• Transfer APT tokens and execute custom transactions
• Query blockchain information, blocks, events, and gas prices
• Manage fungible tokens and NFTs (create, mint, transfer)
• Simulate transactions for gas estimation

Use cases of Aptos Mcp

• Generate a testnet account, fund it from the faucet, and check its balance
• Transfer APT tokens between accounts using private keys
• Query current blockchain information and retrieve block data
• Deploy a new fungible token or create an NFT collection and mint NFTs
• Execute read-only view functions and query table items

FAQ from Aptos Mcp

What network does Aptos Mcp use?

Aptos Mcp uses the Aptos testnet by default, as stated in the configuration.

How do I deploy Aptos Mcp to mcp.so?

Push your code to a public GitHub repository, submit it via the mcp.so submission form, and the server will be hosted automatically. It supports both stdio and REST transports and includes a Dockerfile for containerized deployment.

What are the security considerations?

Private keys must never be shared or exposed. The server operates on testnet only. The testnet faucet has rate limits. Always simulate transactions before submitting. All addresses and inputs are validated.

Does Aptos Mcp support mainnet?

No, the server is explicitly configured for testnet only, as noted in the security notes.

What transport modes are available?

Aptos Mcp supports stdio mode (default) and REST mode (set mode=rest environment variable). It also supports both transports when deployed on mcp.so.