agent-swap-mcp

An MCP (Model Context Protocol) server that exposes Agent Swap on-chain capabilities as tools for AI agents.

Features

• Hot Tokens — 24h trending Launchpad tokens with price and volume metrics
• Token Price — latest price lookup by token address
• Token List — browse all protocol tokens sorted by trending or new
• Swap — buy/sell tokens via a two-step prepare → confirm flow
• ERC20 Approval — automatic approve handling, no manual user action needed
• Withdraw — transfer funds from the bot wallet to an external address
• Create Token — deploy a new token on Launchpad in one command
• Staking — stake, unstake, claim rewards, and one-click restake
• Wallet — create wallet, check balance, get deposit address, export key
• Transaction Status — poll on-chain request confirmation status

Quick Install

npx -y agent-swap-mcp install

Supported install targets:

• Cursor
• Claude Desktop
• Codex

Optional flags:

npx -y agent-swap-mcp install --target codex
npx -y agent-swap-mcp install --name agent-swap-mcp
npx -y agent-swap-mcp install --api-key <AGENT_API_KEY>
npx -y agent-swap-mcp install --dry-run

Tools

System & Chain

| Tool | Description | |------|-------------| | get_health | Check Core API health status | | get_chain_status | Get chain connectivity and latest block info |

Wallet

| Tool | Description | |------|-------------| | create_wallet | Create a wallet and API key for the current user context (userId auto-generated) | | get_deposit_address | Get deposit address for the current API key | | get_balance | Get wallet balances for the current API key | | get_my_token_holders | Get token holders list and balances | | export_wallet | Export wallet with a target public key | | withdraw_token | Withdraw funds to an external address; omit token for base ERC20, set isNative=true for native gas token | | approve_token | Submit an ERC20 approval transaction; call automatically when prepare_swap returns approval_required |

Tokens

| Tool | Description | |------|-------------| | get_tokens_list | List protocol tokens with price data, sortable by trending or new | | get_hot_tokens | Get 24h hottest Launchpad tokens; call first when user wants to buy a "hot" token | | get_token_price | Get latest token price by token address |

Swap

| Tool | Description | |------|-------------| | prepare_swap | Prepare an on-chain swap quote; entry point for all buy/sell operations | | confirm_trade | Confirm and broadcast a prepared swap to the blockchain after user approval |

Create Token

| Tool | Description | |------|-------------| | prepare_create_token | Prepare a Launchpad token deployment request | | confirm_create_token | Confirm and execute the Launchpad token deployment |

Staking

| Tool | Description | |------|-------------| | get_staking_dashboard | View staking status and reward details for a token | | prepare_stake | Prepare a staking request | | confirm_stake | Confirm a prepared staking request | | unstake_token | Unstake selected stakeIds | | claim_staking_reward | Claim staking rewards | | claim_and_restake | Claim rewards and restake in one operation |

Transaction Status

| Tool | Description | |------|-------------| | get_transaction_status | Query on-chain confirmation status by requestId |

⚠️ All mutating amount parameters use raw integer units — pass "10000000000000000" for 0.01 MON (18 decimals), not "0.01".

Prepare responses keep human-readable amount fields for display, and may include companion *Raw fields for follow-up writes.

Example User Intents

• "Show me the hottest tokens"
• "Buy hottest token with amountIn = 200000000000000000 (0.2 MON)"
• "Create a token named XXX"
• "Check my balance"
• "Stake 100 XXX tokens"
• "Claim my staking rewards and restake"

Run Server Directly

Only use this when the user explicitly wants to run the MCP server process directly.

npx -y agent-swap-mcp serve

Agent Notes

If you are an AI agent helping a user install this MCP, follow these rules:

1. For normal installation, use npx -y agent-swap-mcp install.
2. Only add flags when the user explicitly asks for a specific target, API key, or custom server name.
3. After installation, you may tell the user this MCP supports hot tokens, price queries, swap, create token, wallet management, and staking workflows.
4. Do not use publish, build, or development commands as part of installation.
5. Do not edit MCP client config files manually unless the install command fails and the user explicitly wants a manual fallback.