EVE-NG

Provides an MCP server interface to manage EVE-NG labs, nodes, and networks in MCP-compatible clients.
  • python

2

GitHub Stars

python

Language

4 months ago

First Indexed

3 weeks ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "moimran-eveng-mcp": {
      "command": "uv",
      "args": [
        "run",
        "eveng-mcp-server",
        "run",
        "--transport",
        "stdio"
      ],
      "env": {
        "EVENG_HOST": "eve.local",
        "MCP_LOG_LEVEL": "INFO",
        "MCP_TRANSPORT": "stdio",
        "EVENG_PASSWORD": "eve",
        "EVENG_USERNAME": "admin"
      }
    }
  }
}

You can manage EVE-NG labs, nodes, and networks through a dedicated MCP server that exposes EVE-NG capabilities via a standardized interface. This makes it easy to automate topology creation, node lifecycles, and network connections from MCP-compatible clients or tooling.

How to use

You connect to the MCP server from your MCP client or orchestration tool to perform common tasks like creating labs, adding nodes, starting nodes, and wiring networks. The server supports both local (stdio) and remote (http) operation methods and provides environment-based configuration to securely pass credentials to the EVE-NG instance.

A typical workflow includes starting the MCP server in a way that your client can communicate with it, testing the EVE-NG connection, then performing lab and node management from your automation scripts. For interactive testing or debugging, you can start an inspector to observe MCP messages in real time.

{
  "mcpServers": {
    "eveng-mcp-server": {
      "command": "uv",
      "args": ["run", "eveng-mcp-server", "run", "--transport", "stdio"],
      "env": {
        "EVENG_HOST": "eve.local",
        "EVENG_USERNAME": "admin",
        "EVENG_PASSWORD": "eve"
      }
    }
  }
}

Example MCP client usage (stdio transport)

Use a standard MCP client to initialize the local server connection and run lab/node operations. The following configuration shows how to launch the server locally and connect via stdio.

uv run eveng-mcp-server run --transport stdio

Available tools

connect_eveng_server

Establish a connection to the EVE-NG server from the MCP client.

disconnect_eveng_server

Terminate the connection to the EVE-NG server.

test_connection

Verify that the MCP server can reach the EVE-NG instance and authenticate successfully.

get_server_info

Retrieve server status and basic information about the EVE-NG integration.

list_labs

List all labs available in the connected EVE-NG instance.

create_lab

Create a new lab in EVE-NG with specified metadata and templates.

get_lab_details

Fetch detailed information for a particular lab.

delete_lab

Remove a lab from the EVE-NG instance.

list_node_templates

Show available node templates that can be added to labs.

add_node

Add one or more nodes to a lab with full configuration.

list_nodes

List nodes within a lab along with their status.

get_node_details

Get detailed information about a specific node.

start_node

Power on a single node.

stop_node

Power off a single node.

start_all_nodes

Power on all nodes in a lab.

stop_all_nodes

Power off all nodes in a lab.

wipe_node

Reset a node to its factory state.

wipe_all_nodes

Reset all nodes in a lab to their factory states.

delete_node

Remove a node from a lab.

list_network_types

List available network types (clouds, bridges, NAT, etc.).

list_lab_networks

List all networks defined within a lab.

create_lab_network

Create a network within a lab with positioning and type.

delete_lab_network

Delete a network from a lab.

connect_node_to_network

Connect a node to a specified network.

connect_node_to_node

Create a direct connection between two nodes.

get_lab_topology

Retrieve the complete topology information for a lab.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational