ReMCP
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 compact runtime executes real ReMCP operations locally on this computer. Choose one domain tool, then one operation. Inspect before changing state and use the least invasive operation that satisfies the request. The parameters object is validated against the selected operation’s original closed schema.
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 |
|---|---|
| read_fileA | Read a plain text or line-oriented file on this computer: source, config, Markdown, scripts or logs. Use read_document for PDF, DOCX, XLSX and other structured documents. Legacy .docx/.pdf extraction remains supported for compatibility. Use offset and length to page through large text files; a negative offset reads from the end. |
| manage_filesA | Use this when the task is about files, directories, archives, or filesystem search on this computer. Choose exactly one operation; parameters must contain only that operation’s arguments and are validated against its closed schema. Write, edit, move, permission, and delete operations can change or remove local data, while read and search operations leave files unchanged. Use read_file for one known text file. |
| run_terminalA | Use this when the task needs a shell command or an existing ReMCP terminal session: start, read, wait, interact, stop, or list sessions. Choose exactly one operation; parameters are validated against that operation’s closed schema. Starting or interacting with commands can change local or external state, and force termination can lose unsaved process work; reading, waiting, and listing do not mutate the session. |
| control_computerA | Use this for semantic inspection or control of native desktop applications on this computer: windows, accessibility/UI elements, allowlisted app_catalog/app_task/app_execute/app_navigate workflows, waits, displays, app launch, text/input, clipboard, open/reveal, notifications, or short screen recording. Catalog and inspection steps observe state; an explicitly authorized app_task can modify a verified field or remote post, while other desktop actions may change application state. Require a verified target and permission for writes, and prefer semantic targets before raw coordinates. |
| view_imageA | Use this when the result must be pixels from this computer: read an existing image or capture the desktop, one window, monitor, or region. These operations return pixels without interacting with the visible UI. Use control_computer when semantic structure or an action is enough. |
| manage_systemA | Use this for operating-system or ReMCP runtime state: system/runtime/process facts, runtime preferences, services, event logs, networking, installed apps, environment, audio, or explicit power actions. Fact, log, and inventory operations only observe state; process termination, preference/service/audio changes, restart, and shutdown can interrupt work or change the machine. Use run_terminal for general shell commands. |
| manage_documentsA | Use this for structured document content: read PDF/DOCX/XLSX, edit DOCX/XLSX directly, or merge, split, extract, or inspect PDFs. DOCX/XLSX edits can replace the input when no separate output is supplied, and PDF write operations create or replace their requested output; read_document itself is read-only. Use read_file for plain line-oriented text. |
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 7 tools
The tools target distinct domains (system, documents, files, terminal, desktop, images) and descriptions explicitly cross-reference each other to guide selection. Minor overlap remains between read_file and manage_files for file reading, and between view_image and control_computer for screen capture, but the boundaries are clarified in the text.
All tools follow a snake_case verb_noun pattern, which is consistent. However, the noun plurality varies (manage_system singular vs manage_documents/manage_files plural), and the generic 'manage_' verb for three broad tools slightly breaks the specific verb pattern used elsewhere.
Seven tools is well-scoped for a general computer control server. Each tool covers a broad but distinct area, and the count avoids both thinness and bloat, with no redundant tools.
The surface covers system state, file operations, document handling, terminal sessions, desktop automation, and image capture. Lifecycle operations are present through the manage_* tools (read/write/edit/delete/search for files, process/service control for system, session lifecycle for terminal), leaving no obvious functional dead ends.