Skip to main content
Glama
EVE-NG MCP Server

EVE-NG MCP Server

by moimran

EVE-NG MCP Server

A comprehensive Model Context Protocol (MCP) server for EVE-NG network emulation platform integration. This server exposes EVE-NG's full API capabilities through MCP's standardized interface, enabling LLMs to manage network topologies, labs, nodes, and configurations.

Features

๐Ÿ”Œ Connection Management

  • Secure authentication with EVE-NG servers

  • Connection testing and health monitoring

  • Session management with automatic reconnection

  • Support for both HTTP and HTTPS protocols

๐Ÿงช Lab Management

  • Create, list, and delete labs

  • Comprehensive lab information retrieval

  • Lab metadata management (description, author, version)

  • Import/export capabilities (planned)

๐Ÿ–ฅ๏ธ Node Management

  • Add and configure nodes with various templates

  • Start, stop, and manage node lifecycle

  • Bulk operations for multiple nodes

  • Node configuration and status monitoring

  • Comprehensive template and image support

๐ŸŒ Network Management

  • Create and manage networks (clouds, bridges, NAT)

  • Connect nodes to networks and each other

  • Topology visualization and management

  • Network configuration and monitoring

๐Ÿ“Š MCP Resources & Prompts

  • Dynamic resources for real-time lab status

  • Static resources for documentation and examples

  • Guided prompts for common workflows

  • Educational content generation

Related MCP server: Packet Tracer MCP

๐Ÿ”— Client Integrations

The EVE-NG MCP Server integrates seamlessly with popular MCP-compatible clients:

๐Ÿค– Claude Desktop

Use EVE-NG directly in conversations with Claude Desktop for natural language network management:

{
  "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"
      }
    }
  }
}

๐Ÿ“– Complete Claude Desktop Integration Guide โ†’

๐Ÿ’ป VS Code

Integrate with VS Code for enhanced network development workflows:

  • Lab deployment from configuration files

  • Automated testing and validation

  • Topology visualization and documentation

  • Custom tasks and debugging support

๐Ÿ’ป Complete VS Code Integration Guide โ†’

๐Ÿ” MCP Inspector

Test and debug the server using the MCP Inspector:

# Start server in SSE mode
uv run eveng-mcp-server run --transport sse --host 0.0.0.0 --port 8000

# Start MCP Inspector
npx @modelcontextprotocol/inspector

๐Ÿ”— All Integration Guides โ†’

Installation

Prerequisites

  • Python 3.11 or higher

  • UV package manager

  • Access to an EVE-NG server

# Clone the repository
git clone <repository-url>
cd eveng-mcp-server

# Install dependencies
uv sync

# Copy example configuration
cp .env.example .env

# Edit configuration as needed
nano .env

Configuration

The server can be configured using environment variables or a .env file:

# EVE-NG Server Settings
EVENG_HOST=eve.local
EVENG_PORT=80
EVENG_PROTOCOL=http
EVENG_USERNAME=admin
EVENG_PASSWORD=eve

# MCP Server Settings
MCP_TRANSPORT=stdio
MCP_LOG_LEVEL=INFO

See .env.example for all available configuration options.

Usage

Command Line Interface

# Run with stdio transport (default)
uv run eveng-mcp-server run

# Run with SSE transport
uv run eveng-mcp-server run --transport sse --host localhost --port 8000

# Test EVE-NG connection
uv run eveng-mcp-server test-connection --host eve.local --username admin --password eve

# Show configuration
uv run eveng-mcp-server config-info

# Show version
uv run eveng-mcp-server version

Available MCP Tools

Connection Management

  • connect_eveng_server - Connect to EVE-NG server

  • disconnect_eveng_server - Disconnect from server

  • test_connection - Test server connectivity

  • get_server_info - Get server information and status

Lab Management

  • list_labs - List available labs

  • create_lab - Create a new lab

  • get_lab_details - Get detailed lab information

  • delete_lab - Delete a lab

Node Management

  • list_node_templates - List available node templates

  • add_node - Add nodes to labs with comprehensive configuration

  • list_nodes - List lab nodes with status and details

  • get_node_details - Get detailed node information

  • start_node / stop_node - Control individual node power state

  • start_all_nodes / stop_all_nodes - Bulk node operations

  • wipe_node / wipe_all_nodes - Reset nodes to factory state

  • delete_node - Remove nodes from labs

Network Management

  • list_network_types - List available network types

  • list_lab_networks - List all networks in a lab

  • create_lab_network - Create networks with positioning

  • delete_lab_network - Remove networks from labs

  • connect_node_to_network - Connect nodes to networks

  • connect_node_to_node - Create point-to-point connections

  • get_lab_topology - Retrieve complete topology information

Testing

# Test EVE-NG connection
uv run eveng-mcp-server test-connection

# Run the server
uv run eveng-mcp-server run

๐Ÿ“š Documentation

Complete Guides

Integration Guides

Examples

๐ŸŽฏ Development Status

  • โœ… Production Ready - Complete MCP server implementation

  • โœ… EVE-NG Integration - Full API coverage with 25 tools

  • โœ… Client Integrations - Claude Desktop and VS Code support

  • โœ… Comprehensive Testing - Unit, integration, and E2E tests

  • โœ… Production Deployment - Docker, Kubernetes, systemd ready

  • โœ… Complete Documentation - API reference, guides, and examples

  • โœ… MCP Resources - 4 dynamic and static resources

  • โœ… MCP Prompts - 6 guided workflow prompts

๐Ÿš€ Quick Start

  1. Install: git clone <repo> && cd eveng-mcp-server && uv sync

  2. Configure: Copy .env.example to .env and set your EVE-NG credentials

  3. Test: uv run eveng-mcp-server test-connection

  4. Integrate: Follow our Claude Desktop or VS Code guides

  5. Deploy: Use our production deployment guide for production use

๐Ÿค Contributing

We welcome contributions! Please see our Contributing Guide for details on:

  • Code style and standards

  • Testing requirements

  • Documentation guidelines

  • Pull request process

๐Ÿ“„ License

This project is licensed under the MIT License - see the LICENSE file for details.

๐Ÿ†˜ Support

Available Tools

26 tools
add_nodeB

Add a node to a lab.

This tool adds a new node to an existing lab with the specified template, configuration, and positioning. The node will be created but not automatically started.

Inputs: arguments (required).

connect_eveng_serverC
    Connect to EVE-NG server and authenticate.
    
    This tool establishes a connection to the EVE-NG server using the provided
    credentials. The connection will be maintained for subsequent operations.
    

Inputs: arguments (required).

connect_node_to_networkC

Connect a node to a network.

This tool creates a connection between a node interface and a network in the lab, enabling communication through that network.

Inputs: arguments (required).

connect_node_to_nodeC

Connect two nodes together directly.

This tool creates a direct point-to-point connection between two nodes in the lab, enabling direct communication between them.

Inputs: arguments (required).

create_labC

Create a new lab in EVE-NG.

This tool creates a new lab with the specified name and metadata in the given path on the EVE-NG server.

Inputs: name (required), path, description, author, +1 more.

create_lab_networkC

Create a network in a lab.

This tool creates a new network (cloud, bridge, NAT, etc.) in the lab with the specified type and positioning.

Inputs: arguments (required).

delete_labA

Delete a lab from EVE-NG.

This tool permanently deletes a lab and all its associated resources from the EVE-NG server. This action cannot be undone.

Inputs: lab_path (required).

delete_lab_networkA

Delete a network from a lab.

This tool permanently removes a network from the lab. All connections to this network will be lost. This action cannot be undone.

Inputs: arguments (required).

delete_nodeB

Delete a node from a lab.

This tool permanently removes a node from the lab. All node data and configuration will be lost. This action cannot be undone.

Inputs: arguments (required).

disconnect_eveng_serverA
    Disconnect from EVE-NG server.
    
    This tool closes the connection to the EVE-NG server and cleans up
    any active sessions.
    

Inputs: no named parameters.

get_lab_detailsC

Get detailed information about a specific lab.

This tool retrieves comprehensive information about a lab including its metadata, nodes, networks, and current status.

Inputs: lab_path (required).

get_lab_topologyC

Get lab topology information.

This tool retrieves the complete topology of the lab including all nodes, networks, and their connections.

Inputs: arguments (required).

get_node_detailsC

Get detailed information about a specific node.

This tool retrieves comprehensive information about a node including its configuration, status, interfaces, and connectivity.

Inputs: arguments (required).

get_server_infoB
    Get EVE-NG server information and status.
    
    This tool retrieves detailed information about the EVE-NG server
    including version, status, capabilities, and system information.
    

Inputs: no named parameters.

list_lab_networksC

List all networks in a lab.

This tool retrieves information about all networks configured in the specified lab, including their types and connections.

Inputs: arguments (required).

list_labsC

List available labs in EVE-NG.

This tool retrieves a list of all labs available in the specified path on the EVE-NG server, including their basic information.

Inputs: path.

list_network_typesB

List available network types in EVE-NG.

This tool retrieves all available network types that can be used to create networks in labs (bridge, cloud, nat, etc.).

Inputs: arguments (required).

list_nodesB

List all nodes in a lab.

This tool retrieves information about all nodes in the specified lab, including their status, configuration, and connectivity.

Inputs: arguments (required).

list_node_templatesB

List available node templates in EVE-NG.

This tool retrieves all available node templates that can be used to create nodes in labs, including their supported images and options.

Inputs: arguments (required).

start_all_nodesB

Start all nodes in a lab.

This tool starts all nodes in the specified lab. Nodes will be started according to their configured delay settings.

Inputs: arguments (required).

start_nodeC

Start a specific node.

This tool starts a node in the lab. The node must be in stopped state to be started successfully.

Inputs: arguments (required).

stop_all_nodesA

Stop all nodes in a lab.

This tool stops all running nodes in the specified lab. All nodes will be gracefully shut down and their states preserved.

Inputs: arguments (required).

stop_nodeB

Stop a specific node.

This tool stops a running node in the lab. The node will be gracefully shut down and its state will be preserved.

Inputs: arguments (required).

test_connectionB
    Test connection to EVE-NG server.
    
    This tool verifies that the connection to the EVE-NG server is working
    properly and returns server status information.
    

Inputs: arguments (required).

wipe_all_nodesA

Wipe all nodes in a lab (reset to factory state).

This tool wipes all nodes in the lab, deleting all user configuration including startup-configs, VLANs, and other settings. The next start will rebuild all nodes from their selected images.

Inputs: arguments (required).

wipe_nodeA

Wipe a specific node (reset to factory state).

This tool wipes a node, deleting all user configuration including startup-config, VLANs, and other settings. The next start will rebuild the node from the selected image.

Inputs: arguments (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelogโ€ฆ

    TDQS

    A3.5/5.0

    Scored across 26 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific resources and actions in the EVE-NG domain. For example, connect_node_to_network vs connect_node_to_node handle different connection types, while start_node vs wipe_node perform fundamentally different operations on nodes. No tools appear to overlap or cause confusion.

    Naming Consistency5/5

    All 26 tools follow a consistent verb_noun or verb_noun_noun pattern throughout. Examples include create_lab, delete_node, list_network_types, and connect_node_to_network. The naming is perfectly uniform with no mixing of conventions or stylistic deviations.

    Tool Count4/5

    With 26 tools, the count is on the higher side but reasonable for a comprehensive network emulation platform like EVE-NG. The tools cover server management, lab operations, node lifecycle, and network configuration, which justifies the breadth. It's slightly heavy but well-scoped for the domain.

    Completeness5/5

    The toolset provides complete CRUD/lifecycle coverage for EVE-NG's core domain. It includes server connection/disconnection, lab creation/deletion/listing, node addition/deletion/starting/stopping/wipe, network management, and detailed information retrieval. No obvious gaps exist for typical emulation workflows.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      C
      maintenance
      A Model Context Protocol server that integrates with Nautobot to provide network automation and infrastructure data to AI assistants like Claude, allowing them to query and interact with network Source of Truth systems.
      5
      1
      MIT