Cuongpo Coti Mcp 1
Deploy private ERC20 and ERC721 on COTI and move tokens and NFTs from your agent without custom SDK glue.
Overview
ai.smithery/cuongpo-coti-mcp-1 is a Build-phase MCP server for COTI that lets agents manage accounts, deploy private ERC20 and ERC721 contracts, and transfer tokens and NFTs.
What is this MCP server?
- Manage COTI accounts from MCP-exposed tools
- Deploy private ERC20 and ERC721 contracts on COTI
- Transfer tokens and NFTs through agent workflows
- Smithery streamable HTTP remote; version 0.2.1 (cuongpo-coti-mcp-1 slug)
- MCP schema 2025-09-16
- Server version 0.2.1
- GitHub source cuongpo/coti-mcp shared with sibling listing
What problem does it solve?
Shipping private tokens and NFTs on COTI means juggling contracts, transfers, and agent context without a unified MCP layer.
Who is it for?
Solo builders prototyping confidential or NFT flows on COTI with MCP-first agents.
Skip if: Builders on non-COTI chains or teams avoiding any on-chain contract deployment from agents.
What do I get? / Deliverables
After install, your agent can deploy private ERC20/ERC721 on COTI and execute token and NFT transfers via Smithery MCP.
- Private ERC20 and ERC721 deploy paths via MCP
- Token and NFT transfer tooling for agents
- Registered @cuongpo/coti-mcp-1 Smithery remote
Recommended MCP Servers
Journey fit
How it compares
COTI private-token and NFT MCP variant, not a marketplace indexer or fiat on-ramp.
Common Questions / FAQ
Who is ai.smithery/cuongpo-coti-mcp-1 for?
Developers on COTI who need agent access to private ERC20, ERC721, and NFT transfers through Smithery MCP.
When should I use ai.smithery/cuongpo-coti-mcp-1?
Use it while building integrations for private tokens or NFTs on COTI, especially when automating deploy and transfer steps from Claude Code or Cursor.
How do I add ai.smithery/cuongpo-coti-mcp-1 to my agent?
Add remote server.smithery.ai/@cuongpo/coti-mcp-1/mcp with Authorization Bearer {smithery_api_key} in your MCP configuration.