envi-classic-remote-sensing
Related Servers
Alternatives to envi-classic-remote-sensing
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables GUI automation for controlling PIX4Dmatic on Windows through MCP. Supports launching, focusing, capturing screenshots, sending hotkeys, clicking UI elements, opening projects, starting processing, and checking outputs.18-
- FlicenseNot gradedqualityCmaintenanceDesktop UI automation for AI agents: screenshots, window management, mouse, keyboard, UI Automation tree, OCR. Single Windows x64 binary, no dependencies.-
- AlicenseNot gradedqualityAmaintenanceEnables an AI agent to operate Windows applications through vision-driven UI Automation and record polished demo videos with pre-click camera zoom, narration, and cinematic effects.MIT
- AlicenseAqualityAmaintenanceWindows desktop automation MCP server — screenshot, mouse, keyboard & UI Automation. Lets LLM agents see and control your Windows desktop directly.3024919MIT
- FlicenseBqualityCmaintenanceEnables natural language control of Adobe Photoshop and Illustrator via COM automation on Windows, supporting design tasks and batch processing without UXP plugins.30-
- FlicenseNot gradedqualityCmaintenanceWindows desktop automation MCP server enabling screenshot capture, precise visual locating of UI elements via vision models, and automated mouse clicking.-
TDQS
Scored across 12 tools
Most tools have clearly distinct purposes, but 'invoke_menu' and 'run_recipe' both involve menu operations—the former is a single command, the latter a sequence of actions. This slight overlap is minor compared to the overall clarity.
All tools follow a consistent 'envi_classic_' prefix with snake_case naming and action-orientation (e.g., launch, register_inputs, capture_evidence). The only exception is 'health_check', which is a noun but fits the functional pattern.
With 12 tools, the set is well-scoped for a controlled remote sensing lab workflow, covering setup, execution, evidence collection, and finalization without redundancy.
The tools cover the entire lifecycle: health check, launch, input registration, stage planning, GUI interaction, evidence capture, output registration, finalization, and session closure. No obvious gaps exist for the stated purpose.