Genieacs Mcp
Give your agent TR-069 GenieACS NBI access to list and manage CPE devices when you run ISP or lab ACS infrastructure.
Overview
GenieACS MCP is an Operate-phase MCP server that connects agents to GenieACS NBI for TR-069 CPE device management.
What is this MCP server?
- stdio MCP to GenieACS NBI API via ACS_URL (required)
- Optional ACS_USER and ACS_PASS for basic auth
- npm genieacs-mcp (v0.0.11 in packages) and OCI drumsergio/genieacs-mcp
- Server metadata version 0.0.12—TR-069 ACS to LLM tooling
- Targets CPE device management for operators, not generic web apps
- Server version 0.0.12 in registry metadata
- 1 required env var ACS_URL; 2 optional auth vars
- 2 transport packages: npm stdio and OCI stdio
Community signal: 12 GitHub stars.
What problem does it solve?
You operate GenieACS but waste time translating CPE troubleshooting into manual NBI API calls while debugging with an AI assistant.
Who is it for?
Operators and indie ISPs who self-host GenieACS and want agent-assisted CPE visibility and management.
Skip if: Typical SaaS or mobile solo builders with no ACS/TR-069 footprint.
What do I get? / Deliverables
Your agent can interact with GenieACS NBI endpoints in-session once ACS_URL and credentials are configured on the MCP server.
- Agent-accessible GenieACS NBI operations context
- Stdio MCP config with ACS connection parameters
Recommended MCP Servers
Journey fit
How it compares
GenieACS NBI integration—not a generic Kubernetes or VPS MCP.
Common Questions / FAQ
Who is GenieACS MCP for?
Builders and operators running GenieACS TR-069 ACS who need Claude Code or Cursor to reach the NBI API for CPE management.
When should I use GenieACS MCP?
Use it during Operate infra work—device onboarding issues, parameter checks, or ACS-guided remediation with an agent in the loop.
How do I add GenieACS MCP to my agent?
Install genieacs-mcp, set ACS_URL and optional ACS_USER/ACS_PASS, and add the stdio MCP server to your agent configuration.