LabscoMCP early access ↗
akshitsinhaMCP SERVER

Devices MCP Server

Give an assistant the hardware on your desk — camera, microphone, speakers, screen and printer — as tools it can call.

by akshitsinha ↗Desktop & OS AutomationCommunity

LABSCO SUMMARY

The peripherals, addressable as tools.

Most servers reach outward to an API; this one reaches down to the machine — capture a frame, record the screen, print a file, play a sound. The per-class enable switches matter here, because they decide which of those an agent is allowed to touch at all.

What it is

An MCP server for the peripheral devices attached to your computer, covering cameras, printers, audio input and output, and displays through one interface.

What you get

  • Cameras enumerated with their details, stills captured, and video recording started and stopped
  • Screens listed, screenshots taken, and screen recording started and stopped
  • Audio devices listed, microphone recording started and stopped, and audio played through the speakers
  • Printers listed, files sent to print or rendered as PDF, print jobs inspected and cancelled
  • Each device class behind its own switch, so camera, printer, audio and screen can be enabled independently

Requirements

FFMPEG for screen and camera recording and PortAudio for audio recording, installed through your platform's package manager, then uv sync in the cloned repository. Configuration is by environment variables: the host and port it listens on, plus one switch per device class — camera, printer, audio and screen.

Setup effort

Build from source — git clone https://github.com/akshitsinha/mcp-device-server.git