EVE-NG MCP Server
Supports configuration via .env files, allowing users to set EVE-NG server credentials, connection settings, and MCP server parameters through environment variables.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@EVE-NG MCP Server list all labs on the EVE-NG server"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Using UV (Recommended)
# 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 .envConfiguration
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=INFOSee .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 versionAvailable MCP Tools
Connection Management
connect_eveng_server- Connect to EVE-NG serverdisconnect_eveng_server- Disconnect from servertest_connection- Test server connectivityget_server_info- Get server information and status
Lab Management
list_labs- List available labscreate_lab- Create a new labget_lab_details- Get detailed lab informationdelete_lab- Delete a lab
Node Management
list_node_templates- List available node templatesadd_node- Add nodes to labs with comprehensive configurationlist_nodes- List lab nodes with status and detailsget_node_details- Get detailed node informationstart_node/stop_node- Control individual node power statestart_all_nodes/stop_all_nodes- Bulk node operationswipe_node/wipe_all_nodes- Reset nodes to factory statedelete_node- Remove nodes from labs
Network Management
list_network_types- List available network typeslist_lab_networks- List all networks in a labcreate_lab_network- Create networks with positioningdelete_lab_network- Remove networks from labsconnect_node_to_network- Connect nodes to networksconnect_node_to_node- Create point-to-point connectionsget_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
๐ API Reference - Complete documentation for all 25 tools, 4 resources, and 6 prompts
๐ Deployment Guide - Production deployment with Docker, Kubernetes, and systemd
๐ง Troubleshooting Guide - Common issues and solutions
๐งช Testing Guide - Comprehensive testing procedures
Integration Guides
๐ค Claude Desktop Integration - Natural language network management
๐ป VS Code Integration - Enhanced development workflows
๐ All Integrations - Complete integration documentation
Examples
๐ Configuration Examples - Ready-to-use configurations
๐งช Test Scripts - Comprehensive test suite with examples
๐ Sample Labs - Example network topologies
๐ฏ 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
Install:
git clone <repo> && cd eveng-mcp-server && uv syncConfigure: Copy
.env.exampleto.envand set your EVE-NG credentialsTest:
uv run eveng-mcp-server test-connectionIntegrate: Follow our Claude Desktop or VS Code guides
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
Issues: GitHub Issues
Discussions: GitHub Discussions
Documentation: Complete Documentation
Available Tools
26 toolsadd_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
Scored across 26 tools
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.
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.
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.
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
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yoโฆ
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
A Model Context Protocol server for Wix AI tools
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Related MCP Servers
- AlicenseBqualityCmaintenanceA 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.51MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that allows LLMs to create, configure, validate, and explain Cisco Packet Tracer network topologies. It provides a comprehensive suite of tools for generating deployment scripts, CLI configurations, and automated network troubleshooting.2,699 PyPI377MIT
- AlicenseBqualityDmaintenanceAn MCP server that gives Claude and other LLM agents programmatic access to EVE-NG network labs, enabling creation, configuration, and management of virtual network topologies through natural language.142Apache 2.0

Network Sketcherofficial
AlicenseAqualityBmaintenanceLocal-first MCP server that lets AI agents design Cisco-style networks and generate L1/L2/L3 topology diagrams, device tables, and AI-ready context files.1612419Apache 2.0