Cuongpo Coti MCP

What cuongpo-coti-mcp MCP server does

cuongpo-coti-mcp MCP server exposes COTI blockchain operations to MCP-compatible AI applications. Its tools cover account creation and import/export, account selection, network switching, AES-key encryption and decryption, message signing, and signature verification. It also provides native COTI balance and transfer operations.

The server focuses on private token workflows. For ERC20 contracts, agents can deploy contracts, inspect balances, decimals, allowances, and total supply, then mint tokens, transfer them, or approve spenders. For ERC721 collections, the available operations include deployment, minting, ownership and balance lookups, token URI retrieval, per-token approval, operator approval, and collection supply checks.

How it works

The MCP process runs locally and communicates with an AI client using the server configuration supplied by that client. Blockchain actions use configured COTI credentials: an AES key for API authentication, a private key for transaction signing, and the corresponding public key. Account tools can maintain multiple configured accounts and change which account is active.

Network tools allow the active configuration to move among COTI environments identified by the project as testnet, devnet, and mainnet. Transaction tools add lifecycle support beyond token methods: agents can call contract functions, inspect transaction status, retrieve logs, and decode event data.

Setup and configuration

The documented setup requires Node.js 18 or newer. Clone the repository, install its npm dependencies, and build the project before starting the generated Node entry point:

git clone https://github.com/davibauer/coti-mcp.git
cd coti-mcp
npm install
npm run build

A local Claude Desktop configuration starts the built server with node and build/index.js. Set these environment variables before use:

• COTI_MCP_AES_KEY
• COTI_MCP_PUBLIC_KEY
• COTI_MCP_PRIVATE_KEY
• COTI_MCP_CURRENT_PUBLIC_KEY

Multiple accounts can be supplied as comma-separated values for the AES, public, and private key variables. The current public key selects the active account. The project also documents installation through the Smithery CLI for Claude.

Tools and capabilities

cuongpo-coti-mcp MCP server groups its tools into these practical areas:

• Account and credential handling, including account creation, import/export, AES-key generation, encryption, decryption, signing, and verification.
• Network and native-token operations, including current-network lookup, network switching, native balance lookup, and native COTI transfers.
• Private ERC20 deployment and management, including allowance, balance, decimals, supply, minting, transfers, and approvals.
• Private ERC721 deployment and management, including minting, ownership, balances, token URIs, supply, and approval state.
• Contract and transaction inspection, including contract calls, transaction status, event logs, and event decoding.

Limitations and notes

The documented requirements include sensitive signing and authentication material, so the MCP client environment must be configured with the necessary COTI keys. The supplied setup example uses local process configuration rather than describing a hosted deployment. The documentation identifies MIT licensing and links to COTI documentation for protocol-specific details. Verify network and account selection before submitting transfers, mints, approvals, or contract transactions.