ScreenConnect MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTH_MODE | No | Auth mode: env reads local credentials; gateway uses only request headers. | env |
| LOG_LEVEL | No | Log level: debug, info, warn, or error. Logs go to stderr. | info |
| MCP_HTTP_HOST | No | HTTP bind address. The image uses 0.0.0.0. | 127.0.0.1 |
| MCP_HTTP_PORT | No | HTTP bind port. | 8080 |
| MCP_TRANSPORT | No | Transport mode: stdio or http. | stdio |
| MCP_ALLOWED_HOSTS | No | Optional comma-separated Host allowlist for /mcp. | |
| CONDUIT_S2S_SECRET | No | Required for HTTP. At least 32 characters; placeholder and repeated values are rejected. | |
| SCREENCONNECT_ORIGIN | No | Optional exact HTTPS origin for RESTfulAllowedOrigin. | |
| MCP_ALLOW_INSECURE_DEV | No | Set to 1 to permit missing S2S secret for local development, bound only to loopback. | |
| SCREENCONNECT_BASE_URL | Yes | Instance HTTPS URL, including an optional context path. Placeholder hosts are rejected. Required locally. | |
| SCREENCONNECT_API_SECRET | Yes | The extension's RESTfulAuthenticationSecret; never logged. Required locally. | |
| SCREENCONNECT_TOOL_TIERS | No | Comma-separated tool tiers: read,write,admin. Unknown names stop startup. | read |
| SCREENCONNECT_EXTENSION_ID | No | Extension GUID. Must be a GUID. | 2d558935-686a-4bd0-9991-07539f5fe749 |
| SCREENCONNECT_MAX_RESPONSE_CHARS | No | MCP output cap after redaction; maximum 1000000. | 60000 |
| SCREENCONNECT_MAX_UPSTREAM_BYTES | No | Streaming body cap before JSON parsing; maximum 128 MiB. Oversize fails closed. | 16777216 |
| SCREENCONNECT_REQUEST_TIMEOUT_MS | No | Per-call timeout and retry budget; maximum 120000 ms. | 30000 |
| SCREENCONNECT_ALLOW_PRIVATE_BASE_URL | No | Set to 1 to permit private HTTPS hosts locally. Ignored in gateway mode. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| screenconnect_sessions_searchB | Search sessions using safely quoted structured fields or an exclusive advanced raw filter. Pagination is client-side. |
| screenconnect_sessions_list_onlineC | List connected guest sessions. Session type defaults to Access. |
| screenconnect_sessions_get_by_nameC | Find sessions by exact name. |
| screenconnect_session_getC | Get one session by GUID. |
| screenconnect_session_get_detailsB | Get connections and newest-first events. Unknown detail fields are preserved in details; includeRaw returns the original payload. |
| screenconnect_session_get_guest_infoB | Get guest inventory, online state and derived uptimeSeconds (null when unavailable). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
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.
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.
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.
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.