MCP Desktop Tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| screenshot_fullscreenB | Capture the entire screen or a specific display |
| screenshot_regionC | Capture a rectangular region of the screen |
| screenshot_windowC | Capture a specific window by title (partial match) |
| browser_openA | Launch Chromium browser and navigate to a URL |
| browser_navigateB | Navigate the current browser page to a URL |
| browser_clickC | Click an element on the page by CSS selector |
| browser_typeC | Type text into an input element on the page |
| browser_readC | Read content from the current page |
| browser_screenshotC | Take a screenshot of the current browser page |
| browser_closeB | Close the browser instance |
| desktop_mouse_clickB | Click at screen coordinates using the mouse |
| desktop_mouse_moveC | Move the mouse cursor to screen coordinates |
| desktop_keyboard_typeC | Type text using the keyboard (simulates key presses) |
| desktop_keyboard_hotkeyC | Press a keyboard shortcut (e.g. ctrl+c, alt+tab) |
| desktop_window_listA | List all visible windows with their titles, process names, and positions |
| desktop_window_focusC | Focus a window by title (partial match) |
| desktop_window_resizeC | Resize and/or move a window by title |
| desktop_app_launchC | Launch an application by path, name, or URI |
| desktop_clipboard_readA | Read the current clipboard text content |
| desktop_clipboard_writeC | Write text to the clipboard |
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 20 tools
Each tool has a clearly distinct purpose with no ambiguity. The browser tools handle web interactions, desktop tools manage OS-level operations, and screenshot tools capture different screen areas, all with specific, non-overlapping functions.
All tools follow a consistent snake_case naming pattern with clear verb_noun structure (e.g., browser_click, desktop_clipboard_read, screenshot_fullscreen). The naming is predictable and organized by domain prefixes (browser_, desktop_, screenshot_).
With 20 tools, the count is slightly high but reasonable for the broad scope of desktop automation covering browser control, OS interactions, and screenshot functionality. Each tool serves a distinct purpose, though some could potentially be consolidated.
The toolset provides comprehensive coverage for desktop automation, including full browser control (navigation, interaction, reading), OS operations (clipboard, keyboard, mouse, windows), and screenshot capabilities (fullscreen, region, window). No obvious gaps exist for the stated purpose.