EVE-NG MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVENG_HOST | No | EVE-NG API base URL | http://192.168.122.10 |
| EVENG_PASSWORD | No | API password | eve |
| EVENG_USERNAME | No | API username | admin |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_labsA | List all labs on the EVE-NG server. Returns lab names, filenames, and paths. Optionally specify a folder path to list labs in a subfolder. |
| get_labB | Get detailed information about a lab including its nodes, networks, and topology. Returns lab metadata, all nodes with their status, and all networks. |
| create_labB | Create a new lab on the EVE-NG server. Specify a name, optional description, and folder path. |
| delete_labC | Delete a lab from the EVE-NG server. This is irreversible. |
| list_imagesA | List all available QEMU/Docker node images (templates) installed on the EVE-NG server. Returns template names and descriptions. |
| add_nodeB | Add a node (virtual device) to a lab. Specify the template (image name), name, RAM, CPU, and number of interfaces. Use 'list_images' first to see available templates. |
| start_nodeC | Start a single node in a lab. The node must already exist. |
| stop_nodeC | Stop a single node in a lab. |
| start_allB | Start all nodes in a lab simultaneously. |
| stop_allC | Stop all nodes in a lab simultaneously. |
| get_node_statusA | Get the current status of a node — whether it is running, stopped, or building. Also returns node details like RAM, CPU, template, and console URL. |
| push_configA | Push a startup configuration to a node. The node should be stopped before pushing config. The configuration is stored and applied on next boot. |
| get_node_configB | Get a node's current startup configuration text. |
| connect_nodesB | Connect two nodes by creating a network and attaching their interfaces to it. Specify the node IDs and interface IDs to connect. Use 'get_lab' first to see available nodes and their interface IDs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/axiom-works-ai/eveng-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server