Constructor Research MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONSTRUCTOR_BROWSER | No | Names the browser executable to use for sign-in. Defaults to the first Chrome, Edge, Chromium or Brave found. | |
| CONSTRUCTOR_API_PATH | No | The API path used for Constructor platform-account requests. | /api/platform-account |
| CONSTRUCTOR_BASE_URL | No | The Constructor base URL. The host of a desk link must match this. | https://training.constructor.app |
| CONSTRUCTOR_STATE_DIR | No | The directory used for checkpoints, logs and local state. | ~/.local/state/constructor-research-mcp |
| CONSTRUCTOR_COOKIE_FILE | No | Pins one session file for every harness instead of the default per-harness session file. Defaults to unset, using ~/.config/constructor-research/sessions/<harness>.txt. | |
| CONSTRUCTOR_STORAGE_PATH | No | The API path used for Constructor platform-storage (disk/WebDAV) requests. | /api/platform-storage |
| CONSTRUCTOR_READINESS_SECONDS | No | After start, the MCP requests each public URL until it answers or this many seconds pass. 0 disables the readiness check. | 60 |
| CONSTRUCTOR_UPLOAD_SETTLE_SECONDS | No | After any upload to a disk, builds on that disk wait until this many seconds have passed. 0 disables the pause. | 30 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| build_imageB | Build a disk Dockerfile. IDs are generated automatically; omit build storage for the default. Waits up to wait_seconds (default 20), then continues in the background. Check get_deployment for the result. The Dockerfile rules in deploy_app apply. |
| list_imagesA | List images with native build statuses and Dockerfile paths. Optionally filter by disk. Compact results by default; detailed=true returns full image records. |
| list_filesB | List files and folders on a project disk (the Constructor desk's project folder). Non-recursive by default; recursive=true walks subfolders up to max_entries. |
| create_folderB | Create a folder on a project disk, including missing parent folders. Existing folders are left unchanged. |
| sync_filesA | Upload a local file or folder to a project disk. Compares by size and SHA-256 and sends only new and changed files; never deletes. New files and folders upload without asking. If existing files would be replaced, nothing is uploaded and status is confirm_required: ask the user once for the whole list, then repeat with confirm=true. dry_run=true only previews. Skips .git, node_modules, .env, .venv, pycache, .DS_Store and files over 100 MB. If the result is in_progress, repeat the same call to continue. |
| move_pathA | Rename or move files/folders on a project disk. Send every move for the request in one call: without confirm it returns the list (confirm_required) for the user to approve once; repeat with confirm=true. Never overwrites; the destination parent folder must exist. |
| delete_pathA | Delete files/folders (folders with all contents) on a project disk. Send every path for the request in one call: without confirm it returns what would be deleted (confirm_required) for the user to approve once; repeat with confirm=true. Cannot be undone. |
| deploy_appA | Deploy the WHOLE app in one request: prepare project/disk, build or reuse all images, resolve internal/public service references, configure and start. Runs in the background. IDs are automatic. To resume a failure, send deployment_id and service overrides (for example replacement image_id); successful builds are preserved. On failure, failure.log_tail and get_logs show what the build or service printed. Dockerfile rules: one Dockerfile per service named Dockerfile or .dockerfile; docker-compose is not supported. The Dockerfile must build everything itself; no separate setup script the user runs before the build. The app listens on 0.0.0.0 on a fixed port; only one port per service can be public. Services reach each other through internal references (bare host:port by default, http:// only when scheme is set), never localhost; do not bake compose-style fallback hosts (http://db:5432) into ENV. Files uploaded to a desk lose the executable bit: RUN chmod 0755 any entrypoint script you COPY. In nginx configs use only the IPv4 listen line. A volume belongs to one service; services cannot share a volume. Volume data survives restarts and image changes but is wiped if the service is deleted or the volume is removed or changed. The build context is the folder containing the Dockerfile, exactly like a local docker build in that folder. Test the image locally (docker build/run) before uploading. |
| update_appA | Update/add selected services in one request; preserve omitted settings. MCP handles builds, links and restarts in the background. Environment variables merge; supplied port/volume lists replace their lists. Resume a failed update using deployment_id and service overrides. The Dockerfile rules in deploy_app apply. |
| start_appA | Start all or selected services as one operation. MCP handles all requests. Waits up to wait_seconds (default 20); remaining execution continues in the background. Started does not mean ready. |
| stop_appA | Stop all or selected services as one operation. MCP handles all requests. Waits up to wait_seconds (default 20). Stopped means stop requests accepted, not verified teardown. |
| get_deploymentA | With deployment_id, observe/wait for background execution; the MCP owns execution. Each call waits up to wait_seconds (max 20); to wait longer, call again, as often as needed (a loop of get_deployment calls is fine), until execution is finished; do not answer the user while it is still in the background. Services carry status_changes and restarts_seen when the MCP saw the status change or a new container start. After sync_files (or manual upload) set files_uploaded=true; after cookie replacement checking the job resumes it. With no arguments, returns the map of all deployments: every deployment-enabled project with its applications and services (names, native statuses, public URLs, ports). With desk_url or project_id, returns that project's desks, images, hardware and applications; add application_id for one application. resume=false observes only. Never returns environment-variable values. |
| sign_inA | Signs the user in to their Constructor: https://constructor.app unless url names another one (any link from it, e.g. https://acme.constructor.app). Call it when the user asks to sign in, or when a tool returns needs_auth, after telling the user a sign-in window is about to open. It opens a separate Chrome window at the sign-in page; the user signs in there and the window closes by itself. There is one sign-in at a time: signing in to another Constructor replaces it, and the MCP works there afterwards. The session is kept for this harness only, and the MCP renews it automatically for up to 14 days. Waits up to wait_seconds; while the user is still signing in it returns sign_in_pending: call it again (no second window opens), then repeat the call that needed auth. |
| get_logsA | Last lines (default 20, up to 50) of a build or service log: why a build or start failed, how far a long build got, what a starting service prints. Constructor serves logs only live: a build log while the build runs, a service log for its current container while it runs (both replayed from the start, then streamed). The MCP follows the builds and services it starts or shows and keeps their last 50 lines, so they stay readable after the build ends or the container restarts; anything else can be read only while it runs. When a new container starts, the lines of the one before stay, above a '--- new container' marker, and restarts_seen counts them: that answers whether a service keeps restarting and why. An empty service log on a running service usually means a crash loop. |
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 14 tools
Most tools target clearly distinct resources/actions (file ops vs image ops vs service lifecycle vs observability). There is some conceptual overlap: deploy_app and update_app both trigger builds that build_image can do standalone, and get_deployment overlaps with get_logs for observing failures, but the descriptions give enough guidance to pick correctly.
All names are snake_case and verb-first (list_files, build_image, create_folder, sync_files, move_path, delete_path, deploy_app, start_app, get_deployment, get_logs). sign_in is a phrasal verb but fits the same convention cleanly.
14 tools is well within the ideal range and each earns its place across file management, image building, deployment lifecycle, and auth. Nothing feels redundant or thin.
Core workflows are covered: upload/move/delete files, build/list images, deploy/update/start/stop services, observe deployments and logs, and sign in. Minor gaps exist—no tool to read/download file contents from a disk and no image deletion—but agents can work around these.