MCP Webcam Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port to run on | 3333 |
| MCP_HOST | No | Public-facing URL for user instructions and MCP client connections | http://localhost:3333 |
| BIND_HOST | No | Network interface to bind the server to | localhost |
| MCP_TRANSPORT_MODE | No | Set to `stdio` for STDIO mode, defaults to `streaming` | streaming |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| captureA | Gets the latest picture from the webcam. You can use this if the human asks questions about their immediate environment, if you want to see the human or to examine an object they may be referring to or showing you. |
| screenshotB | Gets a screenshot of the current screen or window |
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 2 tools
The tools have overlapping purposes—both capture visual data from the user's environment—with 'capture' targeting the webcam and 'screenshot' targeting the screen, but descriptions could lead to confusion as 'capture' mentions examining objects the human shows, which might overlap with screen content. The boundaries are somewhat unclear, especially for agents interpreting use cases.
Tool names follow a consistent verb-based pattern ('capture' and 'screenshot'), both being single words describing the action. There are no deviations in style or casing, making them readable and predictable, though 'screenshot' is more specific than 'capture' in terms of naming convention.
With only 2 tools, the server feels under-scoped for a webcam domain, as it lacks operations like video capture, settings adjustment, or multi-camera support. This minimal set may limit agent functionality, making it borderline too few for comprehensive visual input handling.
The tool surface is significantly incomplete for a webcam server; it covers basic image capture from webcam and screen but misses essential operations such as starting/stopping video, configuring camera settings, or handling multiple inputs. This creates gaps that could lead to agent failures in more complex visual tasks.