Skip the UI. Launch with AI.
Copy one-shotted.xyz/llms.txt and send it to your AI agent. It'll set up the MCP, configure your client, and guide you through the entire Ethereum ICO launch. You sign every transaction yourself.
Wallet Safety
Never share a seed phrase or private key with an agent, website, or support contact.
ONE-SHOTTED's MCP flow is non-custodial: approvals happen in Rabby or WalletConnect, and the user signs every action directly.
Client Config Examples
Ethereum MCP client config, need to restart the client after.
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"one-shotted-eth": {
"command": "npx",
"args": ["-y", "one-shotted-eth-mcp"]
}
}
}Other MCP clients
Use the generic stdio config:
{
"mcpServers": {
"one-shotted-eth": {
"command": "npx",
"args": ["-y", "one-shotted-eth-mcp"]
}
}
}Verify It Works
After restarting, paste this into your agent:
Configure the ONE-SHOTTED Ethereum MCP, call get_launch_rules, and summarize the current limits and wallet options.
I will sign every wallet action myself. Never ask for my seed phrase or private key.If the agent returns token name limits, FDV guidance, and wallet options - you're ready to launch.
Troubleshooting
If npx is missing or blocked, install Node.js locally first, then retry the same MCP command.
If the client does not detect the MCP after editing config, fully restart the client so it relaunches the local subprocess.
If the approval page closes, a wallet request is rejected, or a session expires, ask the agent to retry the current step. The flow is designed around user-approved retries.