Aptos Mcp

Created By
aptos-labs10 months ago
An AI-powered developer experience for Aptos that lets users vibe code and deploy full-stack dApps with minimal setup.
Overview

What is Aptos MCP?

Aptos MCP is an AI-powered developer experience designed for Aptos, enabling users to vibe code and deploy full-stack decentralized applications (dApps) with minimal setup.

How to use Aptos MCP?

To use Aptos MCP, ensure you have Node.js and npm installed, generate a Build Bot API Key, and follow the integration guides provided in the documentation to connect with your preferred interface.

Key features of Aptos MCP?

  • AI-assisted coding for dApps
  • Easy deployment of full-stack applications
  • Integration with various interfaces like Cursor and Claude Code
  • Comprehensive user and development guides

Use cases of Aptos MCP?

  1. Rapid development of decentralized applications on the Aptos blockchain.
  2. Simplifying the deployment process for developers.
  3. Providing AI-driven assistance for coding and debugging.

FAQ from Aptos MCP?

  • What are the prerequisites for using Aptos MCP?

You need Node.js and npm (version ≥ 5.2.0) installed, along with a Build Bot API Key.

  • Is there a user guide available?

Yes, a user guide is provided to help you get the best results from Aptos MCP.

  • Can I develop locally with Aptos MCP?

Yes, there are specific guides for local development with Aptos MCP.

Server Config

{
  "mcpServers": {
    "aptos-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@aptos-labs/aptos-mcp"
      ],
      "env": {
        "APTOS_BOT_KEY": "<bot_api_key>"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
aptos-labs
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago