Two jobs sit in one server: reading Aptos documentation, and writing the boilerplate a new Aptos project needs. The second is the reason to install it — a Move module, a wallet-connection component and the TypeScript bindings for a contract are exactly the files that are tedious to type and easy to get slightly wrong. Everything runs against a local checkout and the public docs repository, so there is no account and no key; the optional GitHub token only buys a higher read rate.
A Python MCP server for Aptos development. It reads the Aptos documentation repository, creates new fullstack, contract-only or client-only projects, generates components for them, runs Move contract tests, and produces TypeScript ABI interfaces from Move contracts.
- Search and navigation over the Aptos documentation repository, from structure down to a specific topic
- New Aptos projects scaffolded as fullstack, contract or client
- Generated pieces for an existing project — a Move module or table, a React wallet-connection component, a client function that queries a contract
- Move contract tests run against a local project path
- TypeScript ABI interfaces generated from a Move contract, so the front end is typed against the deployed code
Python 3.10 or later, plus Node.js and npm; the Aptos CLI is needed for some of the tooling. Install the mcp package (`uv add "mcp[cli]"` or pip), clone the repository, add `httpx`, then either run `mcp install aptos_mcp_server.py` or point the client at `uv --directory /path/to/aptos-mcp-server run aptos_mcp_server.py`. `GITHUB_TOKEN` is optional and only raises the GitHub API rate limit while reading the docs repository. The project is `aptos-mcp` 0.1.0 in pyproject; `mcp dev aptos_mcp_server.py` runs it under the MCP Inspector.