Enterprise DNAEnterprise DNA

MCP Servers

GeiserX/genieacs-mcp

MCP Server for GenieACS written in Go

Visit site ↗

Our verdict

Not reviewed yet

We have not reviewed GeiserX/genieacs-mcp yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About GeiserX/genieacs-mcp

GeiserX/genieacs-mcp is an MCP server for GenieACS written in Go. It provides a standardized interface for managing and interacting with GenieACS, a TR-069 auto-configuration server for CPE devices.

Best for

Developers already using GenieACS who want to connect it to MCP-compatible clients or workflows

Use cases

  • Integrating GenieACS device management into MCP-compatible workflows
  • Automating TR-069 device configuration and firmware updates
  • Building custom tools that query or modify CPE device parameters

Notes

12 stars on GitHub. Last updated 2026-05-27. Licensed GPL-3.0.

Pros

  • Written in Go for efficient performance and easy deployment
  • Leverages MCP protocol for standardized tool integration
  • Small codebase with low overhead

Cons

  • Very early stage with only 12 stars and limited community adoption
  • Requires existing GenieACS infrastructure to be useful
  • No documentation or usage examples beyond the repository description

Key facts

What we have checked

Days since the last commit
2
Checked GitHub
GitHub forks
4
Checked GitHub
GitHub stars
19
Checked GitHub
Open issues
0
Checked GitHub
Releases in the last 90 days
6
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

How to use

How to set it up

As the listing publishes it. We have not run this install.

Install

npx -y genieacs-mcp

Tools exposed

  • search_devices
  • get_parameter
  • reboot_device
  • push_firmware
  • refresh_parameter
  • set_parameter
  • connection_request
  • tag_device
  • create_preset
  • delete_preset
  • create_provision
  • delete_provision
  • delete_task
  • retry_task

Clients the listing names (not checked here)

Claude Desktop, Claude Code, Cursor, VS Code

Example client config

{
  "mcpServers": {
    "genieacs": {
      "command": "npx",
      "args": [
        "-y",
        "genieacs-mcp"
      ],
      "env": {
        "ACS_URL": "http://localhost:7557"
      }
    }
  }
}

Install

Add GeiserX/genieacs-mcp to your client

Not verified yet

Our lab has not run this server yet. "Config checked" on a client means the recipe matches that client's documented config format; it does not mean we ran it.

Claude Code

Config checked

Run in your terminal (runs on your computer)

claude mcp add --env ACS_URL=YOUR_ACS_URL --transport stdio geiserx-genieacs-mcp -- npx -y genieacs-mcp@0.3.7

Needs ACS_URL: replace each YOUR_ value with your own.

Version 0.3.7 · From the Official MCP registry, read · Format checked against Claude Code's config docs

Claude Desktop

Config checked

Add to claude_desktop_config.json (runs on your computer)

{
  "mcpServers": {
    "geiserx-genieacs-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "genieacs-mcp@0.3.7"
      ],
      "env": {
        "ACS_URL": "YOUR_ACS_URL"
      }
    }
  }
}

Needs ACS_URL: replace each YOUR_ value with your own.

Version 0.3.7 · From the Official MCP registry, read · Format checked against Claude Desktop's config docs

Cursor

Config checked

Add to .cursor/mcp.json (runs on your computer)

{
  "mcpServers": {
    "geiserx-genieacs-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "genieacs-mcp@0.3.7"
      ],
      "env": {
        "ACS_URL": "YOUR_ACS_URL"
      }
    }
  }
}

Needs ACS_URL: replace each YOUR_ value with your own.

Version 0.3.7 · From the Official MCP registry, read · Format checked against Cursor's config docs

VS Code

Config checked

Add to .vscode/mcp.json (runs on your computer)

{
  "inputs": [
    {
      "type": "promptString",
      "id": "acs-url",
      "description": "GenieACS NBI API URL (e.g. http://genieacs:7557)",
      "password": true
    }
  ],
  "servers": {
    "geiserx-genieacs-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "genieacs-mcp@0.3.7"
      ],
      "env": {
        "ACS_URL": "${input:acs-url}"
      }
    }
  }
}

Needs ACS_URL: replace each YOUR_ value with your own.

Version 0.3.7 · From the Official MCP registry, read · Format checked against VS Code's config docs

Codex

Config checked

Add to ~/.codex/config.toml (runs on your computer)

[mcp_servers.geiserx-genieacs-mcp]
command = "npx"
args = ["-y", "genieacs-mcp@0.3.7"]
env_vars = ["ACS_URL"]

Needs ACS_URL: replace each YOUR_ value with your own.

Version 0.3.7 · From the Official MCP registry, read · Format checked against Codex's config docs

  • ChatGPT: ChatGPT connects only to remote servers that need no API key.

Recipes come from the server's entry in the official MCP registry. Check the package name before you run it, and keep keys out of shared files.

Works with

What GeiserX/genieacs-mcp connects to

5 clients, each with how we know and when we checked.

Works withTypeHow we knowChecked
Claude CodeClientInstall recipe matches the client's documented formatRuns locally, version 0.3.7Config checkedClaude Code docs
Claude DesktopClientInstall recipe matches the client's documented formatRuns locally, version 0.3.7Config checkedClaude Desktop docs
CursorClientInstall recipe matches the client's documented formatRuns locally, version 0.3.7Config checkedCursor docs
VS CodeClientInstall recipe matches the client's documented formatRuns locally, version 0.3.7Config checkedVS Code docs
CodexClientInstall recipe matches the client's documented formatRuns locally, version 0.3.7Config checkedCodex docs

Stars and usage

How GeiserX/genieacs-mcp is growing

GitHub stars

19 to 19

stars. 28 Oct 2026 to 9 Nov 2026, 3 readings.

Source: GitHub. Checked .

Health and security

Is GeiserX/genieacs-mcp looked after, and what do its setup files show

Health score

56 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Recent activity30 of 30Last push 2 days ago
Releases15 of 156 releases in 90 days
Issue repliesNot countedThe latest check has no issue response reading (fewer than 3 measured issues, or issues switched off)
Maintainer0 of 15Owned by a single user
Official source0 of 20Community server

Security check static checks

100 out of 100

Reads what is published about the server: package advisories, licence, secrets in the documented setup and tool permissions. Nothing is installed or run, so this is not a security assessment. Checked by edna-static-v1 npm:genieacs-mcp@0.4.1. What it checks

Licence: GPL-3.0

  • Note The lab has not recorded this server's tool list yet, so tool permissions were not checked.

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.

← Back to MCP ServersSubmit your own entry →