The brief: make server work observable
DSDillon needed a direct connection between an authorized client and its infrastructure. The connector needed to inspect server state, run commands and keep long running work accessible through a session reference.
The connector is version 1.0.0. It runs separately from the desktop Terminal 2.2.0 application and its Commander interface.
Ten tools with distinct purposes
The tool surface covers status, session listing, standard and administrative commands, standard and administrative session starts, session reading, input, signals and stopping. These actions have defined inputs and structured results.
| Operation family | Purpose |
|---|---|
| Status and list | Inspect the connector and its session records |
| Command | Run a bounded command and collect its result |
| Session start | Create an interactive process reference |
| Session read | Retrieve buffered output from a cursor |
| Input and lifecycle | Send input or request a permitted signal or stop |
Permissions follow the operation
The connector defines separate status, reading, execution and administrative scopes. Its HTTP authorization flow validates the bearer token, intended resource and required scope. The default scope set contains status and reading capabilities.
The owner grants capabilities to the connected client. Ordinary execution and administrative work have separate permissions. Approval bound to each individual command requires an additional workflow.
Output and failure are returned explicitly
A command result includes standard output, error output, exit code, duration and timeout state. Output limits are identified in the response. An unsuccessful command can therefore be distinguished from a request that never started.
Interactive work receives a session reference. Reading uses an offset and returns the next position, current status and remaining output information. A client can continue reading an existing job instead of launching another copy.
Interactive example / no live connection
What does the result tell the operator?
{
"example": true,
"task": "Service inspection",
"target": "Application staging",
"exit_code": 0,
"stdout": "Sample service status: active",
"stderr": "",
"timed_out": false
}The check returned a result. The operator can review the evidence before choosing another action.
Long running work has a bounded lifecycle
The service manages process sessions and retains a limited output buffer. It provides input and lifecycle controls for an authorized client. Expired or unknown sessions return a clear error.
Session state is held by the running connector process. A connector restart does not promise durable job recovery. A client project requiring restart persistence needs an additional job store and recovery design.
Keep an operational trail
The audit calls record the actor, tool, target context, command hash and outcome fields for relevant operations. The administrative route remains distinct from ordinary execution in those records.
Retention, access and coverage must be reviewed for a client deployment. A command hash helps identify the submitted content; it is not a full screen recording or proof of every external effect.
A working connection in the DSDillon toolset
This connector has been used for authorized build, test and publication tasks in the DSDillon environment. The operations return actual server responses. The public example below illustrates their shape using invented identifiers and output.
No public terminal, installer or administrative endpoint is exposed through the case study. Businesses can commission a connector around their own resources, permissions and supported clients.
Before you begin
Can an assistant inspect the server without command access?
The connector separates status and reading scopes from execution. Each tool checks its required permission.
Are desktop Terminal and the MCP connector the same application?
They are separate components in the DSDillon infrastructure toolset. The desktop app supplies an operator interface; the connector supplies tools to an authorized client.
Does the connector preserve sessions after a service restart?
The inspected implementation keeps session state in process memory. Durable recovery across restarts requires an additional design.
Developed by DSDillon. Published 26 September 2026.
