aptos-mcp
Related Servers
Alternatives to aptos-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAptos MCP is a comprehensive Model Context Protocol (MCP) server implementation for the Aptos blockchain, compatible with MCP clients like Claude Desktop or Cursor.ai. It provides a complete DeFi toolkit covering major Aptos protocols including pool discovery, lending, DEX operations, perpetual trading, liquid staking, and cross-protocol portfolio management.7 npmMIT

Aptos NPM MCPofficial
AlicenseBqualityBmaintenanceEnables users to manage API keys and perform Aptos Build actions through MCP-compatible interfaces like Claude and Cursor. This server facilitates development workflows on the Aptos blockchain by integrating directly with the Aptos Build platform.2215 npm13Apache 2.0- FlicenseAqualityCmaintenanceA comprehensive MCP server for MetaApp development, offering tools for project initialization, protocol exploration, and blockchain interaction.15-
- AlicenseAqualityDmaintenanceAn MCP server that serves documentation and enables AI-powered search, Q\&A, and document analysis for developer tools and guides.54MIT
- AlicenseAqualityDmaintenanceMCP server for Shelby Protocol that enables AI agents to read, write, and manage files on decentralized storage (Aptos) through tools like upload, download, list, delete, and account info.51MIT
- AlicenseAqualityCmaintenanceMCP server for reading, writing, and organizing API documentation in Apidog.126 npmMIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: generating ABI, creating indexers, creating projects, creating gas stations, generating components, and testing contracts. The descriptions specify different resources and actions, making misselection unlikely.
The naming follows a consistent verb_noun pattern with 'aptos' as a prefix (e.g., create_aptos_project, generate_aptos_component), except for 'aptos_abi_generate' which uses noun_verb order. This minor deviation slightly breaks the pattern but maintains overall readability.
With 6 tools, the count is well-scoped for an Aptos development server, covering key operations like project setup, component generation, and testing. Each tool earns its place without feeling excessive or insufficient for the domain.
The toolset covers creation and testing aspects well but has notable gaps in lifecycle management, such as updating or deleting projects/components, and lacks deployment or interaction tools (e.g., deploy_contract, call_function). This limits full workflow coverage for Aptos development.