Understand the workspace.
Discover directories, inspect file metadata, search source text, read documents, and look into SQLite structure.
Meet DESCO — a private desktop command layer that lets AI assistants work with approved Windows files, processes, tests, and local data through 20 core MCP tools plus 13 Windows visual tools.
01 / WHAT CHANGES
Most assistants stop at instructions. DESCO provides a structured way for a compatible AI assistant to inspect a workspace, make approved changes, run tests, and return evidence — all through defined tools.
Discover directories, inspect file metadata, search source text, read documents, and look into SQLite structure.
Create files, make surgical edits, run managed processes, and execute project test suites with explicit tool calls.
Read process output, inspect test results, check process liveness, and restore backed-up files when needed.
02 / THE TOOLKIT
Explore the DESCO Windows runtime catalog: 20 original structured tools and 13 new visual tools. Client exposure depends on MCP tool registration. Search by name, filter by purpose, and see practical examples of what each action enables.
Tool availability is confirmed by the registered DESCO integration. Each tool's behavior and access depend on runtime configuration; this page does not imply every tool has been individually exercised in production.
03 / USE CASES
DESCO is a building block. These example workflows show where the existing tools fit into developer and operations work — without claiming actions outside the current toolkit.
04 / THE CONNECTION
Your assistant plans an action, DESCO exposes the right tool, your Windows runtime executes within its configured scope, and results flow back for verification.
ChatGPT or another compatible MCP client selects a defined action.
The Windows DESCO runtime offers 33 named tools. Each MCP client must register the tools it exposes; after a plugin refresh a new ChatGPT session displayed 33 tools and a filtered read-only window listing passed.
Approved local files, process sessions, and project test workflows.
05 / COMMON QUESTIONS
The owner Windows runtime now includes screen capture, window inspection, accessibility controls, mouse and keyboard actions. These tools passed local checks and a filtered visual call through ChatGPT. The remaining visual scenarios still require end-to-end acceptance.
The local Windows runtime must be running and reachable for DESCO desktop tools to work. Cloud-based research or scheduled tasks can be separate services, but they do not turn an offline Windows computer into an active tool runtime.
No. The interactive visual on this page is a product UI concept illustrating how a future DESCO operator dashboard could look. It is not connected to a customer's computer. The MCP runtime is separate. It has 20 established structured tools and 13 visual tools installed on the owner machine; this dashboard remains illustrative.
Contact DigiCrem to request a scoped product walkthrough. We can demonstrate compatible MCP client connection and representative tool calls in an approved test workspace.
Have a Windows workflow, MCP integration, or automation project in mind? Let's understand the job and build a small, verifiable starting point.