Skip to main content
Glama
Sign In
omada-controller-mcp

omada-controller-mcp

by samhaque
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to omada-controller-mcp

No user-submitted related servers found.

    Related Servers

    • swagger-mcp

      emreycolakoglu
      A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server for navigating OpenAPI / Swagger specifications, enabling agents to search endpoints, retrieve parameters and schemas, and inspect authentication without loading the full spec into context.
      9
      15 npm
      MIT

    • Omada MCP Server

      Zesty0wl
      A
      license
      C
      quality
      B
      maintenance
      Enables managing TP-Link Omada SDN controllers through MCP, exposing 72 tools for sites, devices, clients, networks, switch ports, firewalls, schedules, and site settings, including reboot and PoE scheduling.
      72
      1
      MIT

    • unifi-console-mcp

      jaseonline
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to search, describe, and call roughly 180 undocumented UniFi OS/Network console API operations from a bundled OpenAPI spec, plus curated reads and typed configuration changes. Writes are off by default, require per-entity enablement, and use previews, verification, and rollback safeguards.
      29
      MIT

    • api-testing-agent

      SHREELASYABEZAWADA
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible clients to discover API endpoints from OpenAPI/Swagger specs, send HTTP requests, validate responses, and analyze status codes for automated API testing.
      1
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool serves a clearly distinct role: introspection (server_info), schema lookup (get_operation_schema), catalog management (refresh_catalog), discovery (search_operations), generic invocation (call_operation), and domain conveniences (list_sites, list_devices). No two tools have overlapping purposes; even the metadata tools chain together in an obvious workflow.

    Naming Consistency4/5

    Most tools follow a clean verb_noun snake_case pattern: get_, refresh_, search_, call_, list_. server_info is the only deviation, being noun_noun instead of get_server_info, but it remains readable and does not introduce style mixing.

    Tool Count5/5

    Seven tools is well within the ideal 3-15 range and appropriately scoped for a generic API wrapper with a couple of convenience helpers. Each tool earns its place without redundancy or bloat.

    Completeness5/5

    The dynamic call_operation plus catalog discovery tools give full coverage of the Omada API surface, while list_sites and list_devices address common high-level needs. The set covers discovery, schema inspection, invocation, and common queries with no obvious dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources