Logitech Sync MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOGITECH_SYNC_ORG_ID | Yes | Required organisation ID from Logitech Sync Portal. | |
| LOGITECH_SYNC_CA_FILE | No | Optional custom CA bundle. | |
| LOGITECH_SYNC_KEY_FILE | No | Private key path; an absolute path is recommended. | client-certificate/privateKey.pem |
| LOGITECH_SYNC_CERT_FILE | No | Client certificate path; an absolute path is recommended. | client-certificate/certificate.pem |
| LOGITECH_SYNC_TRUST_ENV | No | Explicitly allow HTTPX environment proxies and CA settings. | false |
| LOGITECH_SYNC_MAX_RETRIES | No | Bounded retries for 429/502/503/504 and transport errors. | 3 |
| LOGITECH_SYNC_API_BASE_URL | No | Documented API server; override only for administration or testing. | https://api.sync.logitech.com/v1 |
| LOGITECH_SYNC_FIXTURE_FILE | No | Offline fixture mode for tests and evaluations. | |
| LOGITECH_SYNC_TIMEOUT_SECONDS | No | Overall timeout for one attempt. | 30 |
| LOGITECH_SYNC_CACHE_TTL_SECONDS | No | Short in-memory cache to reduce quota usage. | 60 |
| LOGITECH_SYNC_MIN_REQUEST_INTERVAL_SECONDS | No | Minimum interval between network attempts. | 1 |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| logitech_sync_check_connectionA | Verify live mTLS access, or validate the configured offline fixture. |
| logitech_sync_list_placesA | Fetch one controlled page of rooms/desks using the native continuation cursor. |
| logitech_sync_search_inventoryA | Search across place and device inventory as one agent-oriented workflow. |
| logitech_sync_get_inventory_summaryA | Aggregate rooms, desks, coverage, device types/models/versions, status, and health. Use this before deeper reports to understand inventory shape without returning every raw device. Pagination is bounded and all counts clearly indicate whether the scan completed. Returns counters and ranked model/version buckets. It is read-only and uses a projection optimized for identity, coverage, and health aggregation. |
| logitech_sync_list_device_issuesA | Diagnose offline, unhealthy, stale, or incomplete-peripheral devices. |
| logitech_sync_get_occupancy_reportA | Report live room occupancy, known capacity, utilization, and over-capacity state. |
| logitech_sync_get_environment_reportA | Aggregate Spot/Rally Board sensor readings with explicit numeric filters. |
| logitech_sync_get_coverage_reportA | Audit room/desk contracts, licenses, and device warranties at a given date. |
| logitech_sync_list_network_inventoryA | Inventory reported device IPs, MACs, hostnames, and network interfaces. Search by network identifier, place, or device, and optionally filter by interface mode. Missing network fields remain absent rather than being invented because reporting varies by device model and firmware. This tool does not scan the network or change configuration. Returns bounded entries, interface-mode counts, and scan-completeness metadata. |
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 9 tools
Each tool has a clearly distinct purpose: connection check, coverage reports, environment sensors, inventory summary, occupancy, device issues, network inventory, places listing, and search. No overlap or ambiguity.
All tools follow a consistent pattern: 'logitech_sync_' + verb_noun (e.g., check_connection, get_coverage_report, list_device_issues). Underscores are used uniformly, and verbs are appropriate for the action.
9 tools is well-scoped for a monitoring/diagnostics server covering connection, reporting, inventory, issues, and search. Not excessive and each tool serves a specific need.
The tool set covers the main monitoring and diagnostic operations comprehensively: connection, coverage, environment, occupancy, issues, inventory, and search. Missing write/update operations, but the domain appears read-only, so minor gap.