I’ve been using Cursor for vibe coding, mostly to learn, experiment, and build basic things without overthinking structure too much.
I recently set up Aptos MCP with Cursor, and it actually made a noticeable difference in how useful the AI feels when working with Aptos / Move.
Before this, Cursor was fine for general coding help, but when it came to Aptos-specific stuff, the AI would sometimes guess APIs, mix SDK versions, or give answers that looked right but weren’t quite accurate.
With Aptos MCP enabled, the AI feels much more Aptos-aware. It understands Move syntax better, gives more realistic examples, and is more reliable when asking beginner-level questions like:
-
simple Move modules
-
basic token contracts
-
Aptos tooling / SDK usage
-
explaining errors or patterns in plain language
For someone like me; not trying to be a Move expert yet, just learning and building step by step this setup fits really well. It keeps the vibe-coding flow, but reduces the “is this even correct?” doubt.
The setup itself is straightforward (adding an mcp.json, API key, and enabling Agent mode in Cursor), and once it’s running, you can just talk to the agent like usual, except now it actually knows Aptos.
Overall, if you’re already using Cursor and are curious about Aptos or Move, this is a pretty practical upgrade to your workflow.