Network Devices Mcp Sse Server

Name: Network Devices Mcp Sse Server
Author: aimiox

@aimiox

Repository Homepage

About Network Devices Mcp Sse Server

Model Context Protocol (MCP) servers and clients

#network-devices #mcp #sse-server

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "amxnet": {
      "command": "docker",
      "args": [
        "run",
        "-it",
        "-p 8765:8765",
        "-p 8002:8002",
        "aimiox/amxnet-mcp:latest"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Network Devices Mcp Sse Server?

The aimiox AMXNet Network Devices MCP Server enables seamless interaction with network devices through the OpenAI Agents SDK or any SSE-compatible MCP client. It provides a powerful interface for managing, monitoring, and controlling connected devices like servers, routers, switches, and more. The system consists of two main components: the AMXNet MCP Server (central server using WebSockets and SSE) and the AMXNet Device Client (lightweight C client running on each network device).

How to use Network Devices Mcp Sse Server?

Run the server via Docker (docker pull aimiox/amxnet-mcp:latest then sudo ./run_amxnet_mcp.sh) or manually with Docker, configuring ports with environment variables AMXNET_DEVICE_PORT (default 8765) and AMXNET_SSE_PORT (default 8002). Download the appropriate device client binary for each device architecture, make it executable, and run it with --name <device_name> --server <server_ip> --port <server_port>. Then use the provided amxnet_cli.py script with an OpenAI API key and the SSE endpoint to interact with the server.

Key features of Network Devices Mcp Sse Server

Device Management: Register, monitor, and control remote devices
File Operations: List, read, write, and search files on connected devices
System Monitoring: View system information, processes, and resource usage
Command Execution: Run shell commands on remote devices (premium version)
Cross-Platform Support: Works on Linux, OpenWRT, and OpenBSD devices
Secure Communication: Device connections with TLS encryption

Use cases of Network Devices Mcp Sse Server

List all network devices and check their current status
Retrieve detailed system information and resource usage of a device
List, read, and search files on remote devices
Monitor running processes on a device
Execute shell commands on devices (with proper permissions in premium version)

FAQ from Network Devices Mcp Sse Server

What is the difference between the free and premium versions?

The free version supports managing up to 2 devices. The paid version adds support for 100+ devices, full command execution and file modification, custom integrations, and priority support.

What architectures does the device client support?

Pre-built binaries are available for x86_64 (64-bit), ARM (32-bit), and MIPS architectures. The client has no library dependencies and a minimal resource footprint.

What ports does the server use?

The server listens on two ports: WebSocket port 8765 for device client connections, and SSE port 8002 for MCP host/AI agent connections. Both ports can be configured via environment variables.

How do I connect a device to the server?

Download the appropriate device client binary for your device architecture, make it executable (chmod +x amxnet_device_client_<ARCH>), then run it with --name <device_name> --server <server_ip> --port <port>.

Is the server compatible with the OpenAI Agents SDK?

Yes. The server uses SSE (Server-Sent Events) on port 8002, and the included CLI client (amxnet_cli.py) integrates with the OpenAI Agents SDK to enable AI agent interaction with network devices.