Markdown Sidecar MCP Server
lwsinclairLABSCO SUMMARY
The point is currency, not raw capability.
Aptos ships fast enough that a general model's Move knowledge goes stale — gas stations, the no-code indexer and the current wallet adapters all postdate most training data. This server carries the up-to-date guidance alongside tools that perform the platform setup, so the agent both knows the current pattern and can wire it up for you.
What it is
Aptos's own MCP server: tools that automate Aptos Geomi platform setup, plus development guides that keep an AI agent on current Move and Aptos practice rather than the version it was trained on.
What you get
- Aptos Geomi platform management automated, so project setup is not a manual walkthrough
- Gas stations for sponsored transactions, so your users can transact without holding gas themselves
- API keys and rate limits configured for production applications
- Current Move smart contract patterns instead of the outdated ones a general model reaches for
- Modern Aptos features — sponsored transactions, the no-code indexer, wallet adapters including Google login
- Correct CLI usage and workflows for today's Aptos commands
Requirements
Node ≥ 22.12.0 and npm ≥ 10, both bundled with node 22. A Geomi Bot API Key, created under Bot Keys at geomi.dev, supplied as APTOS_BOT_KEY in the MCP configuration. Integration guides are provided for Cursor, Claude Code and Codex.
Setup effort
One command plus a key — npx -y @aptos-labs/aptos-mcp, then supply credentials
USE CASES
01
Starting an Aptos project without the setup slog
The agent manages the Geomi project, keys and rate limits instead of you clicking through the console.
02
Giving your users transactions they don't pay gas for
Create a gas station for sponsored transactions and wire it into the app.
03
Writing Move that matches the current language
The agent follows the shipped patterns rather than the ones it half-remembers from training.
04
Adding a wallet flow people will actually complete
Use the current adapters, Google login among them, instead of an older integration path.
BEFORE YOU INSTALL
What to know first
Requires
- npx on PATH
- APTOS_BOT_KEY in your environment
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"aptos-mcp": {
"command": "npx",
"args": [
"-y",
"@aptos-labs/aptos-mcp"
],
"env": {
"APTOS_BOT_KEY": "<YOUR_APTOS_BOT_KEY>"
}
}
}
}Either way the server needs a Geomi Bot Key in APTOS_BOT_KEY — in the configuration block it is <YOUR_APTOS_BOT_KEY>; if you run the npx command yourself, set APTOS_BOT_KEY in that shell first. To create one: on geomi.dev, click your name in the bottom left corner, then Bot Keys, then Create Bot Key.
npx
TERMINAL
npx -y @aptos-labs/aptos-mcp
