base-gasless-deploy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deploy_gasless_tokenA | Deploy an ERC-20 token on Base using CDP Paymaster (zero gas for user). Falls back to normal gas if no paymaster configured. Requires DEPLOYER_PRIVATE_KEY. |
| get_token_infoB | Get info about a deployed ERC-20 token: name, symbol, decimals, total supply, and owner balance. |
| estimate_gas_savingsB | Show how much gas was saved (or would be saved) by using the paymaster for a token deployment. |
| list_deployed_tokensB | List tokens deployed by an address in the current session. Tracks all deployments made through this MCP server. |
| transfer_tokensA | Transfer ERC-20 tokens gaslessly via paymaster. Falls back to normal gas if no paymaster. Requires DEPLOYER_PRIVATE_KEY (transfers FROM the deployer wallet). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
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.
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.