Skip to main content
Glama

✨ 제공 기능

유형

용도

MCP URI / 도구 ID

리소스

GenieACS 데이터 읽기 전용 사용

genieacs://device/{id}genieacs://file/{name}genieacs://tasks/{id}genieacs://devices/list

도구

GenieACS를 통해 CPE에서 작업 호출

reboot_devicedownload_firmwarerefresh_parameter

모든 기능은 단일 JSON-RPC 엔드포인트(/mcp)를 통해 노출됩니다.
LLM / 에이전트는 initialize → readResource → listTools → callTool 등의 작업을 수행할 수 있습니다.


Related MCP server: router-mcp

🚀 빠른 시작 (Docker Compose)

https://github.com/GeiserX/genieacs-container 의 지침을 따르세요. 해당 저장소의 docker compose 파일에 포함되어 있습니다.

📦 npm을 통한 설치 (stdio 전송)

npx genieacs-mcp

또는 전역으로 설치:

npm install -g genieacs-mcp
genieacs-mcp

이 명령은 플랫폼에 맞는 사전 빌드된 Go 바이너리를 다운로드하고, 모든 MCP 클라이언트와 호환되는 stdio 전송 방식으로 실행합니다.

🛠 로컬 빌드

git clone https://github.com/GeiserX/genieacs-mcp
cd genieacs-mcp

# (optional) create .env from the sample
cp .env.example .env && $EDITOR .env

go run ./cmd/server

🔧 구성

변수

기본값

설명

ACS_URL

http://localhost:7557

GenieACS NBI 엔드포인트 (끝에 / 제외)

ACS_USER

admin

GenieACS 사용자 이름

ACS_PASS

admin

GenieACS 비밀번호

TRANSPORT

(비어 있음 = HTTP)

stdio 전송을 사용하려면 stdio로 설정

.env 파일( .env.example에서 생성)에 넣거나 환경 변수로 설정하세요.

테스트

Inspector로 테스트했으며 현재 완전히 작동합니다. PR을 제출하기 전에 이 MCP 서버가 해당 환경에서 잘 작동하는지 확인해 주세요.

실제 MCP 클라이언트(클라이언트 LLM)를 통한 테스트는 부족하므로, 이 MCP 서버가 제공하는 서비스와 적절히 일치하지 않는 경우 설명을 개선하기 위한 PR을 제출해 주시기 바랍니다.

클라이언트 LLM을 위한 구성 예시:

{
  "schema_version": "v1",
  "name_for_human": "GenieACS-MCP",
  "name_for_model": "genieacs_mcp",
  "description_for_human": "Read data from GenieACS and run actions on CPEs (reboot, firmware update, parameter refresh).",
  "description_for_model": "Interact with an Auto-Configuration-Server (ACS) that manages routers. First call initialize, then reuse the returned session id in header \"Mcp-Session-Id\" for every other call. Use readResource to fetch URIs that begin with genieacs://. Use listTools to discover available actions and callTool to execute them.",
  "auth": { "type": "none" },
  "api": {
    "type": "jsonrpc-mcp",
    "url":  "http://localhost:8080/mcp",
    "init_method": "initialize",
    "session_header": "Mcp-Session-Id"
  },
  "logo_url": "https://raw.githubusercontent.com/GeiserX/genieacs-container/main/extra/logo.png",
  "contact_email": "acsdesk@protonmail.com",
  "legal_info_url": "https://github.com/GeiserX/genieacs-mcp/blob/main/LICENSE"
}

크레딧

GenieACS – 최고의 오픈 소스 ACS

MCP-GO – 현대적인 MCP 구현

GoReleaser – 간편한 멀티 아키텍처 릴리스

관리자

@GeiserX.

기여

언제든 참여해 주세요! 이슈를 열거나 PR을 제출해 주세요.

GenieACS-MCP는 Contributor Covenant 행동 강령을 따릅니다.

GenieACS 생태계

이 프로젝트는 GenieACS 작업을 위한 더 넓은 도구 세트의 일부입니다:

프로젝트

유형

설명

genieacs-docker

Docker + Helm

프로덕션 준비가 완료된 멀티 아키텍처 Docker 이미지 및 Helm 차트

genieacs-ansible

Ansible 컬렉션

동적 인벤토리 플러그인 및 장치 관리 모듈

genieacs-ha

HA 통합

TR-069 모니터링을 위한 Home Assistant 통합

n8n-nodes-genieacs

n8n 노드

GenieACS를 위한 워크플로우 자동화

genieacs-services

서비스 정의

Systemd/Supervisord 서비스 정의

genieacs-sim-docker

시뮬레이터

테스트를 위한 Docker 기반 GenieACS 시뮬레이터

GeiserX의 다른 MCP 서버

Available Tools

12 tools
connection_requestWake device (connection request)A
Idempotent

Send a TR-069 connection request so a CPE device contacts GenieACS now instead of at its next periodic inform. Use it to run tasks that are already queued, or to apply a preset change without waiting. It queues nothing itself. Succeeds when the device answered; fails with ACS error 504 when the device is unreachable (offline, or behind NAT without STUN). Example: connection_request(device_id="202BC1-BM632w-000001").

Inputs: device_id (required).

delete_taskDelete queued taskA
DestructiveIdempotent

Remove a task from the GenieACS queue before the device runs it, for example a firmware download or reboot queued by mistake, or a faulted task you do not want retried. GenieACS already deletes a task once the device has run it, so every task you can see in genieacs://tasks/{device_id} is either waiting or faulted. Fails with ACS error 503 while the device is in a session with GenieACS; try again a few seconds later. Use retry_task instead to run a faulted task again. Example: delete_task(task_id="67abc123def4560012345678").

Inputs: task_id (required).

download_firmwarePush firmware or file to deviceA
Destructive

Tell a CPE device to download and apply a file stored on GenieACS: a firmware image, a configuration file or another file the device accepts. A wrong image can leave a device unusable, so check the file's metadata (genieacs://file/{name}: OUI, product class, version) against the device first. GenieACS queues a download task and sends a connection request at once; the transfer itself can take minutes after the tool returns. Check genieacs://tasks/{device_id} and genieacs://faults/{device_id} afterwards. Example: download_firmware(device_id="202BC1-BM632w-000001", file_id="firmware-v2.0.bin").

Inputs: file_id (required), device_id (required), filename. Returns: task, status, message, task_id, +1 more

get_parameterRead cached device parametersA
Read-onlyIdempotent

Read TR-069 parameter values GenieACS has cached for a device, without contacting the device: firmware version, serial number, uptime, WiFi SSID, IP addresses and so on. Values are what the device reported at its last inform or refresh, with a timestamp each; call refresh_parameter first when you need a value from the device now. Give one path or a comma-separated list; an object path such as "Device.WiFi" returns every cached leaf under it. Returns found=false for an unknown device id, and lists paths with no cached value under missing.

Inputs: device_id (required), parameter_path (required). Returns: found, missing, device_id, parameters

manage_presetCreate, replace or delete presetA
DestructiveIdempotent

Create, replace or delete a GenieACS preset. A preset is a fleet-wide rule: at their next inform, every device matching its precondition gets its configurations applied, so a broad precondition (or an empty one) reconfigures the whole fleet. Confirm the precondition and the devices it matches (search_devices with the same filter) before a put. action="put" creates or overwrites the preset with body; action="delete" removes it. body is a JSON object: weight (integer, higher wins), precondition (a MongoDB-style filter as a JSON string, e.g. "{"_tags":"office"}"), and configurations (an array of {type: "value" | "provision" | "add_object" | "delete_object", ...}). Example body: {"weight":0,"precondition":"{"_tags":"pilot"}","configurations":[{"type":"provision","name":"myScript"}]}. Read genieacs://presets/list first.

Inputs: name (required), action (required), body.

manage_provisionCreate, replace or delete provision scriptA
DestructiveIdempotent

Create, replace or delete a GenieACS provision script. A provision is JavaScript that GenieACS runs during the inform session of every device a preset applies it to, so replacing one changes how those devices are configured. Scripts use the GenieACS sandbox API (declare, commit, clear, ext, log); ext() calls extension scripts that run on the ACS host with full privileges, so treat a provision as code running on your ACS. action="put" uploads or overwrites the script (raw JavaScript, not JSON; GenieACS answers 400 on a syntax error); action="delete" removes it. Presets reference provisions by name. Read genieacs://provisions/list first. Example script: log("Device " + DeviceID.ID + " informed");

Inputs: name (required), action (required), script.

reboot_deviceReboot deviceA
Destructive

Reboot a CPE device through GenieACS. Use it when a device needs a restart, for example after a configuration change or to recover an unresponsive device. The device drops its service while it restarts. GenieACS queues the task and sends a connection request at once: status "done" means the device ran it in that session, "queued" means it runs at the device's next inform. A reboot does not confirm the device came back; read Device.DeviceInfo.UpTime (or InternetGatewayDevice.DeviceInfo.UpTime) with refresh_parameter afterwards. Example: reboot_device(device_id="202BC1-BM632w-000001").

Inputs: device_id (required). Returns: task, status, message, task_id, +1 more

refresh_parameterRefresh parameter from deviceA
Idempotent

Ask a CPE device for the current value of a TR-069 parameter, or of every parameter under an object path, and store it in GenieACS. Use it when get_parameter's cached value may be stale. It changes nothing on the device. GenieACS queues a getParameterValues task and sends a connection request at once: status "done" means the fresh value is already stored, so read it with get_parameter; "queued" means it arrives at the device's next inform. Example: refresh_parameter(device_id="202BC1-BM632w-000001", parameter="Device.DeviceInfo.SoftwareVersion").

Inputs: device_id (required), parameter (required). Returns: task, status, message, task_id, +1 more

retry_taskRetry faulted taskA
Idempotent

Run a faulted task again: GenieACS clears the task's fault, and the device runs the task at its next session. Read genieacs://faults/{device_id} first to see why it failed; retrying a task whose cause is unchanged faults again. A task that has not faulted is left as it is. Example: retry_task(task_id="67abc123def4560012345678").

Inputs: task_id (required).

search_devicesSearch devicesA
Read-onlyIdempotent

Find CPE devices in GenieACS with a MongoDB-style filter: by tag, manufacturer, model, firmware version, last inform time or any TR-069 parameter. It only reads. Examples: {"_tags":"office"}; {"InternetGatewayDevice.DeviceInfo.Manufacturer":"Huawei"} (GenieACS adds ._value to parameter paths); {"_lastInform":{"$lt":"2026-01-01T00:00:00Z"}} for devices silent since that date; {"_id":{"$regex":"^202BC1-"}}. Query operators such as $eq, $ne, $gt, $lt, $in, $nin, $exists, $regex, $and and $or work; $where, $function, $accumulator and $expr are refused, and a $regex pattern may be at most 256 characters. By default each device comes back as a summary (id, last inform, tags, manufacturer, product class, serial); ask for other fields with projection. Results come in pages of limit (default 50, at most 200); page with skip.

Inputs: query (required), skip, sort, limit, +1 more. Returns: more, skip, count, limit, +1 more

set_parameterSet device parametersA
DestructiveIdempotent

Write one or more TR-069 parameter values on a CPE device, overwriting the current values: WiFi SSID or key, periodic inform interval, management server URL, or any writable parameter. A wrong value can cut the device off (a wrong WAN or ACS URL setting, for example). parameter_values is a JSON array of [path, value] or [path, value, xsdType] tuples; xsd types include xsd:string, xsd:boolean, xsd:unsignedInt, xsd:int and xsd:dateTime, and GenieACS infers the type when it is omitted. Example: [["InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.SSID","Lab-2","xsd:string"]]. GenieACS queues the task and sends a connection request at once: status "done" means the device applied it, "queued" means it runs at the next inform. A read-only or unknown parameter makes the device fault the task; see genieacs://faults/{device_id}. Read the current value with get_parameter first.

Inputs: device_id (required), parameter_values (required). Returns: task, status, message, task_id, +1 more

tag_deviceAdd or remove device tagA
DestructiveIdempotent

Add a tag to a CPE device or remove one. Tags group devices: presets match on them (precondition {"tags":"office"}) and search_devices finds by them. Adding or removing a tag can therefore make a preset apply to the device, or stop applying, at its next inform. Tags are case-sensitive. Use letters, digits, "-" and "": GenieACS rejects a tag with other characters (a "." for example) with a 404. Fails with ACS error 404 when the device id does not exist. Example: tag_device(device_id="202BC1-BM632w-000001", tag="office", action="add").

Inputs: tag (required), action (required), device_id (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.5/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action, and subtle pairs are explicitly separated: get_parameter (cached) vs refresh_parameter (fresh from device), delete_task vs retry_task, manage_preset vs manage_provision. Several tools queue tasks, but their purposes (reboot, download firmware, set/refresh parameters) are clearly different, and connection_request is explicitly documented as queueing nothing.

    Naming Consistency4/5

    Eleven of twelve tools follow a clean verb_noun snake_case pattern (get_parameter, set_parameter, delete_task, reboot_device, tag_device, search_devices, etc.). The outlier is connection_request, which drops the leading verb; manage_preset/manage_provision also fold create/update/delete into an action parameter rather than separate names, a minor inconsistency.

    Tool Count5/5

    Twelve tools is well within the ideal range and each earns its place: device discovery, parameter read/write/refresh, task lifecycle, firmware, presets, provisions, tagging, and connection requests. Nothing feels redundant or missing for the apparent ACS-management scope.

    Completeness4/5

    The surface covers the core TR-069 lifecycle: discover/tag devices, read/write/refresh parameters, reboot, download firmware, manage tasks (delete/retry), and CRUD presets/provisions. Minor gaps remain—no tool to list or upload the files that download_firmware references, and no dedicated task/fault listing tool (deferred to resource URIs), which agents can partly work around.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      A high-performance Go-based MCP server that provides a microservice architecture for orchestrating diverse tools through gRPC and HTTP/REST APIs. Enables seamless integration of language-agnostic tools including ML capabilities, web search, calculations, and human interaction for intelligent agent workflows.
      2
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provider-agnostic MCP server for managing heterogeneous infrastructure (SSH, Proxmox VE, Virtualizor, Hetzner Cloud, Cloudflare) via a JSON inventory, exposing tools for VM/container management, DNS, firewalls, and SSH operations.
      MIT