Key Concepts

Understanding these core concepts will help you effectively use the Poobah MCP Server.

ADO (Andromeda Digital Object)

An ADO is a smart contract built on the Andromeda framework. Think of ADOs as modular, reusable building blocks for blockchain applications.

Common ADO Types

ADO Lifecycle

1. Instantiate - Deploy a new ADO with initial configuration
2. Execute - Perform actions on the ADO (transfers, mints, etc.)
3. Query - Read data from the ADO (balances, ownership, etc.)

→ See DO Operations for ADO tools

Environments

Andromeda operates across multiple network environments:

Testnet (Galileo)

• Chain ID: galileo-4
• Purpose: Development and testing
• Tokens: Test tokens with no real value
• Recommendation: Start here for learning and development

Mainnet

• Chain ID: andromeda-1
• Purpose: Production deployments
• Tokens: Real assets with real value
• Recommendation: Use only for production-ready applications

Devnet

• Purpose: Bleeding-edge feature testing
• Tokens: Test tokens
• Recommendation: For testing unreleased features

→ Switch environments with switch_environment

Kernel

The kernel is the central hub for Andromeda services on each chain. It provides:

• ADO Registry: Tracks deployed ADOs
• Service Discovery: Locates ADODB, VFS, and other services
• Cross-chain Coordination: Routes messages between chains

Each chain has a default kernel, but you can connect to custom kernels.

→ See switch_kernel and get_kernel_info

VFS (Virtual Filesystem)

VFS provides human-readable paths for blockchain contracts, similar to a filesystem.

Path Format

/home/username/contract-name

Benefits

• Memorable names instead of long addresses
• Organized hierarchy
• Easy to share and reference

Example

Instead of:

andr14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9shptkql

Use:

/home/alice/my-nft-collection

→ Resolve paths with resolve_path

AMP (Andromeda Messaging Protocol)

AMP enables communication between ADOs, including cross-chain messaging.

Use Cases

• Local messaging: Send actions between contracts on the same chain
• Cross-chain messaging: Interact with contracts on other chains via IBC
• Kernel routing: Route messages through the kernel for special handling

Recipient Formats

• Raw address: andr1abc...
• VFS path: /home/alice/my-contract
• IBC path: ibc://galileo-4/andr1abc...

→ See AMP Operations for messaging tools

Wallet Modes

The MCP server supports three wallet connection modes:

Test Mode

• Uses a mnemonic phrase for signing
• Transactions execute automatically
• Best for development and testing

External Mode

• Prepares unsigned transactions
• You sign with an external wallet (e.g., Keplr)
• Use broadcast_transaction to submit
• Best for production with secure key management

Readonly Mode

• Can query data but cannot sign
• No private key access needed
• Best for data exploration and monitoring

→ See Wallet Operations for connection tools

Schemas

JSON schemas define the structure of ADO messages:

Instantiate Schema

Defines parameters for creating a new ADO.

Execute Schema

Defines available actions and their parameters.

Query Schema

Defines available queries and their parameters.

Response Schema

Defines the structure of query responses.

→ See Schema Operations for fetching schemas

Gas and Fees

Blockchain transactions require gas fees:

• Gas: Computational units consumed by the transaction
• Fee: Token payment for gas
• Auto fee: Let the system calculate appropriate fees
• Simulation: Estimate gas without executing

Simulation Mode

Most write operations support simulate: true to:

• Estimate gas costs
• Validate the transaction
• Catch errors before spending tokens