Skip to main content
Glama
Tlazypanda

aptos-mcp

by Tlazypanda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
create_aptos_projectC
Create a new Aptos project using the Aptos CLI.

Args:
    project_name: Name of the project
    project_type: Type of project (fullstack, contract, client)
generate_aptos_componentC
Generate a new component for an Aptos project.

Args:
    component_type: Type of component (table, module, etc.)
    component_name: Name of the component
    project_dir: Project directory path
    options: Additional options as a string
test_aptos_contractC
Test an Aptos Move contract using the Aptos CLI.

Args:
    contract_path: Path to the contract directory or file
    function_name: Optional function to test specifically
    args: Optional list of arguments for the function
create_aptos_indexerC
Creates a new Aptos indexer project based on the example processor.

Args:
    project_name: Name of the indexer project
    processor_type: Type of processor (transaction, event)
create_gas_stationB
Creates a new Aptos gas station (fee sponsorship) project.

Args:
    project_name: Name of the gas station project
aptos_abi_generateC
Generate ABI for an Aptos contract.

Args:
    contract_path: Path to the contract directory
    output_format: Format of the output (ts, json)

Prompts

Interactive templates invoked by user choice

NameDescription
create_new_project_promptPrompt template for creating a new Aptos project
debug_move_contract_promptPrompt template for debugging Move contract errors

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.3/5.0

Scored across 6 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness3/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources