PIX4Dmatic MCP
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pix4d_get_statusB | Return PIX4Dmatic process and window status. |
| pix4d_launchC | Launch PIX4Dmatic or attach to the existing process. |
| pix4d_focusB | Focus the PIX4Dmatic main window. |
| pix4d_screenshotB | Save a screenshot of the current desktop. |
| pix4d_send_hotkeyB | Send a pywinauto hotkey string to PIX4Dmatic, for example '^o' or '{F5}'. |
| pix4d_type_textB | Type plain text into the focused PIX4Dmatic control. |
| pix4d_click_textC | Click a visible PIX4Dmatic UI control by accessible text. |
| pix4d_click_menuC | Click a menu or menu-like UI path by visible text labels. |
| pix4d_get_ui_treeB | Return a compact UI Automation tree for selector discovery. |
| pix4d_open_projectB | Open an existing PIX4Dmatic project file. |
| pix4d_read_latest_logsB | Read recent lines from the newest discovered PIX4Dmatic log file. |
| pix4d_find_log_errorsC | Summarize warnings and errors from the latest PIX4Dmatic log. |
| pix4d_start_processingD | Start processing by clicking the first matching processing control. |
| pix4d_wait_until_idleB | Wait until PIX4Dmatic appears idle based on process CPU and recent logs. |
| pix4d_check_outputsB | Check whether expected PIX4Dmatic outputs exist under a project directory. |
| pix4d_collect_diagnosticsB | Collect screenshot, recent logs, and status into a diagnostics directory. |
| pix4d_run_job_objectC | Run a job object against the current PIX4Dmatic session or an existing project_path. |
| pix4d_run_jobC | Load and run a JSON job file. |
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 18 tools
Most tools have distinct purposes, such as launching, opening projects, running jobs, and checking outputs, but there is some overlap between pix4d_click_menu and pix4d_click_text, which both involve clicking UI elements, and between pix4d_run_job and pix4d_run_job_object, which both handle job execution, potentially causing confusion.
All tool names follow a consistent 'pix4d_' prefix with snake_case and descriptive verb-noun patterns, such as pix4d_launch, pix4d_open_project, and pix4d_check_outputs, making them predictable and easy to understand.
With 18 tools, the count is slightly high but reasonable for a desktop automation server covering UI interaction, job processing, diagnostics, and monitoring, though it could be streamlined by merging overlapping tools.
The toolset covers key areas like launching, project management, job execution, UI automation, and diagnostics, but there are minor gaps, such as no explicit tools for closing projects or handling errors beyond logging, which agents might need to work around.