Skip to main content
Glama
ScreenConnect MCP Server

ScreenConnect MCP Server

by WYRE-AI

Related Servers

Alternatives to ScreenConnect MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read computers, clients, locations, alerts, and script catalog and history data from the ConnectWise Automate RMM REST API, and on explicit request reboot machines, run scripts or catalog commands, and create or update clients. Credentials are supplied per request via HTTP headers and never stored, supporting stateless multi-tenant use.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides governed access to ConnectWise Manage (PSA) data including service tickets, companies, contacts, configurations, projects, sales, time, schedule, finance, and procurement through 68 tools, with read-only mode by default and optional write operations, deployed to Azure with credentials stored in Key Vault.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Integrates with ConnectWise Manage API to enable ticket, company, and contact management operations. Supports filtering, pagination, and CRUD actions.
      8 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read managed endpoints, their software and hardware audit, patch status, agent procedures, alarms, tickets, organizations and machine groups, and, with explicit confirmation, deploy patches or run an agent procedure on an endpoint. Supports stateless multi-tenant access with per-request credentials for the VSA REST API.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with N-able RMM (N-sight) API to manage clients, sites, devices, and retrieve monitoring data such as checks, patches, and performance history.
      Apache 2.0

    TDQS

    C2.9/5.0

    Scored across 6 tools

    Disambiguation3/5

    Most tools return session data, with overlapping lookup paths: search, list_online, and get_by_name can all be used to find sessions. The descriptions clarify intended distinctions, but boundaries between search/get_by_name and get/get_details/get_guest_info still require careful reading.

    Naming Consistency3/5

    All names use snake_case with a screenconnect prefix, but the set mixes plural 'sessions' with singular 'session' and noun-first patterns like sessions_search with verb-first patterns like session_get_details. It remains readable, but the convention is not predictable.

    Tool Count5/5

    Six tools is well-scoped for a read-only ScreenConnect session inspection server. Each tool covers a distinct query mode or detail level, and there are no obviously redundant extras.

    Completeness3/5

    The surface covers session search, listing, lookup, details, and guest info well for read-only monitoring. However, it lacks any session control or management operations, such as disconnecting sessions or sending commands, which are central to a ScreenConnect domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues