genlayer-cli-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRIVATE_KEY | No | Private key (alternative env var name) | |
| GENLAYER_PRIVKEY | No | Private key (alternative env var name) | |
| GENLAYER_PRV_KEY | No | Private key (alternative env var name) | |
| GENLAYER_PRIVATE_KEY | No | Private key (0x prefix + 64 hex chars or raw 64 hex chars) |
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 |
|---|---|
| genlayerB | Run the GenLayer CLI with full command access. This can perform state-changing operations. |
| genvm_lintC | Run genvm-lint for GenVM contract linting, validation, schema extraction, typechecking, setup, or downloads. |
| genlayer_deployB | Deploy a GenLayer Intelligent Contract with genlayer-js. Accepts privateKey; generates one when missing or invalid. |
| check_toolsA | Check whether node, genlayer, python, and genvm-lint are available to this MCP server. |
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 4 tools
Each tool targets a clearly distinct function: checking environment availability, running arbitrary CLI commands, deploying contracts, and linting. No overlap in purpose.
Tool names are inconsistent: 'check_tools' uses verb_noun, 'genlayer' is a single word, 'genlayer_deploy' and 'genvm_lint' use prefix_verb pattern. Mixed conventions reduce predictability.
Four tools is reasonable for a CLI wrapper server, covering core operations without being too few or excessive.
The set covers essential actions: environment check, CLI execution, deployment, and linting. Missing other possible genlayer commands, but core workflow is covered.