Logitech Sync MCP

English | Français

A read-only Model Context Protocol server for the Logitech Sync Cloud API. It turns the API's place inventory endpoint into nine focused tools that AI clients can use to inspect rooms, desks, devices, health, occupancy, coverage, environmental readings, and network information.

The server is written in Python, managed with UV, and connects to Logitech Sync with mutual TLS (mTLS). Certificate material stays on the local machine and is never accepted as a tool argument or returned in a tool response.

This is an independent integration and is not affiliated with or endorsed by Logitech. See Notices.

Tools

All tools declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true.

Related MCP server: meraki-dashboard-api

Requirements

• UV

• A Logitech Sync organisation ID from Sync Portal → Settings → Sync Cloud API

• A PEM client certificate and its matching private key

• A compatible Logitech Select, Essential, or Sync Plus license

Quick start

git clone https://github.com/bouchecousue/logitech-sync-mcp.git
cd logitech-sync-mcp
cp .env.example .env

Place your credentials at the default paths:

client-certificate/certificate.pem
client-certificate/privateKey.pem

Set LOGITECH_SYNC_ORG_ID in .env, restrict the private key, then install and start the server:

chmod 600 client-certificate/privateKey.pem
uv sync --all-groups --no-editable
uv run --no-editable python run_server.py

The last command starts a stdio MCP server and waits for protocol messages on standard input. See the complete Getting Started guide for certificate setup, client configuration, validation, and troubleshooting.

MCP client configuration

Generic stdio configuration:

{
  "mcpServers": {
    "logitech-sync": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/logitech-sync-mcp",
        "run",
        "--no-editable",
        "python",
        "/path/to/logitech-sync-mcp/run_server.py"
      ]
    }
  }
}

The server loads .env from the project directory. Keep credentials out of the MCP client configuration when possible so they are not duplicated across configuration files.

Configuration

The organisation ID is a separate value: the server never attempts to infer it from the X.509 certificate subject.

Pagination, quotas, and output

According to the supplied Logitech documentation, the API allows 14,400 requests per day, supports a sustained rate of one request per second, and recommends exponential backoff. The client therefore:

• serialises network attempts at a minimum one-second interval;

• honours Retry-After without retrying early;

• applies bounded exponential backoff with jitter;

• caches pages briefly and caps the cache at 256 pages;

• detects cursor loops;

• bounds workflows with page_size, max_pages, and max_results;

• exposes nextResultOffset when an aggregated result has another local page;

• keeps text and structuredContent within a combined MCP response budget and reports truncation explicitly.

Tools support markdown and json text rendering and return schema-validated structuredContent. An omitted projection preserves Logitech's default projection, while [] requests place IDs only. Device child projections automatically include their required parent projection.

Security model

• .env, client-certificate/, private-key formats, caches, and local tooling files are excluded from Git.

• On POSIX systems, startup fails if the private key is readable by the group or other users.

• Server certificate verification remains enabled; the implementation has no verify=False path.

• HTTP redirects are disabled so the client certificate is not presented to another host.

• PEM data is never exposed through MCP arguments or results.

• Application logs never use stdout, which is reserved for the stdio protocol.

• API-provided strings are treated as untrusted data and escaped in Markdown output.

• The API URL and secret paths are administrator configuration, not model-controlled tool inputs.

Before publishing a fork or opening a pull request, run:

git status --short
git check-ignore -v .env client-certificate/privateKey.pem

Never commit an organisation ID, certificate, private key, captured API response, or real inventory fixture.

Development

uv sync --all-groups --no-editable
uv run --no-editable ruff check .
uv run --no-editable ruff format --check .
PYTHONPATH=src uv run --no-sync pytest --cov=logitech_sync_mcp
uv run --no-editable python -m compileall -q src

The live test consumes API quota and is disabled by default:

LOGITECH_SYNC_RUN_LIVE=1 uv run --no-editable pytest -m live tests/test_live.py

The deterministic evaluation set uses the versioned synthetic fixture, never a live inventory.

Documentation

• Getting Started

• Architecture

• French README

• Contributing

• Security policy

• Changelog

• Notices

License

Released under the MIT License.