Skip to main content
Glama
lordbasilaiassistant-sudo

base-gasless-deploy-mcp

README.md
# base-gasless-deploy-mcp

MCP server for deploying ERC-20 tokens on Base with **zero gas** using CDP Paymaster. Falls back to normal gas if no paymaster is configured.

## Install

```bash
npx -y base-gasless-deploy-mcp
```

## Configuration

Add to your MCP client config (e.g. Claude Desktop):

```json
{
  "mcpServers": {
    "base-gasless-deploy": {
      "command": "npx",
      "args": ["-y", "base-gasless-deploy-mcp"],
      "env": {
        "DEPLOYER_PRIVATE_KEY": "0x...",
        "PAYMASTER_URL": "https://api.developer.coinbase.com/rpc/v1/base/..."
      }
    }
  }
}
```

### Environment Variables

| Variable | Required | Description |
|----------|----------|-------------|
| `DEPLOYER_PRIVATE_KEY` | Yes (write ops) | Private key for deploying/transferring |
| `PAYMASTER_URL` | No | CDP Paymaster RPC endpoint for gasless transactions |
| `CDP_PAYMASTER_URL` | No | Alias for PAYMASTER_URL |
| `RPC_URL` | No | Base RPC (default: https://mainnet.base.org) |

## Tools

### deploy_gasless_token

Deploy an ERC-20 token on Base. Uses paymaster for zero gas when configured.

**Params:**
- `name` (string) - Token name
- `symbol` (string) - Token symbol
- `supply` (string, default "1000000") - Total supply in human units
- `owner_address` (string) - Address that receives all tokens

### get_token_info

Get info about a deployed token (name, symbol, supply, owner balance).

**Params:**
- `token_address` (string) - Token contract address

### estimate_gas_savings

Show how much gas was saved by using the paymaster.

**Params:**
- `token_address` (string) - Token contract address

### list_deployed_tokens

List all tokens deployed by an address in the current session.

**Params:**
- `deployer_address` (string) - Deployer wallet address

### transfer_tokens

Transfer ERC-20 tokens gaslessly via paymaster.

**Params:**
- `token_address` (string) - Token contract address
- `to` (string) - Recipient address
- `amount` (string) - Amount in human units

## How It Works

1. Pre-compiled ERC-20 bytecode is embedded in the server (no Solidity compiler needed at runtime)
2. When `PAYMASTER_URL` is set, transactions are routed through the CDP Paymaster for gas sponsorship
3. If the paymaster fails or isn't configured, transactions fall back to normal gas from the deployer wallet
4. All deployments are tracked in-memory for gas savings reporting

## Related MCP Servers

| Package | Tools | What it does |
|---------|-------|-------------|
| `obsd-launchpad-mcp` | 14 | Deploy tokens, trade, earn OBSD |
| `base-security-scanner-mcp` | 8 | Scan contracts for vulnerabilities |
| `base-price-oracle-mcp` | 7 | On-chain price feeds from DEX pools |
| `base-multi-wallet-mcp` | 8 | Coordinated multi-wallet trading |
| `base-gasless-deploy-mcp` | 5 | Gasless ERC-20 token deployment |
| `base-flash-arb-mcp` | 7 | Detect arbitrage opportunities |
| `base-token-sniper-mcp` | 5 | Discover & trade new launches |
| `base-wallet-toolkit-mcp` | 7 | Wallet balances, gas, tokens |
| `base-contract-reader-mcp` | 6 | Read any smart contract (free) |
| `create-mcp-server-cli` | - | Scaffold a new MCP server |

## License

MIT

TDQS

A3.8/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: deploy_gasless_token creates tokens, estimate_gas_savings calculates gas savings, get_token_info retrieves token details, list_deployed_tokens lists deployments, and transfer_tokens handles transfers. The descriptions reinforce these distinct functions, making misselection unlikely.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: deploy_gasless_token, estimate_gas_savings, get_token_info, list_deployed_tokens, and transfer_tokens. This predictability aids agent understanding and tool selection without confusion.

Tool Count5/5

With 5 tools, the count is well-scoped for the server's purpose of gasless token deployment and management on Base. Each tool earns its place by covering essential operations without bloat, aligning with typical MCP server sizes of 3-15 tools.

Completeness4/5

The tool set provides strong coverage for the domain, including deployment, estimation, info retrieval, listing, and transfers, with clear CRUD-like operations. A minor gap exists in lacking explicit update or delete tools for tokens, but agents can likely work around this given the deployment focus.

Maintenance

ActivityMaintained
ResponsivenessNo issues