Repository navigation
Releases
v0.1.1 — npm distribution and release hardening
Highlights
First npm release of the independent, unofficial Cloud-only Cloudroom MCP adapter. Existing GitHub v0.1.0 users can upgrade to v0.1.1.
npx --yes cloudroom-mcp@0.1.1Use command: "npx" with args: ["--yes", "cloudroom-mcp@0.1.1"] in your stdio MCP client. Node.js 22+ and a separately configured Cloudroom / room-cli installation are required; npm installs only the adapter.
Changes
- Add the
cloudroom-mcpexecutable, public package metadata, and pinned npm/Pi setup instructions in English and Korean. - Publish only 15 runtime/documentation/example files; exclude local code indexes, credentials, tests, and CI files.
- Keep the MCP-reported version synchronized with package.json.
- Safely bind option-like spawn titles with
--title=value. - Add packaging regression tests and shared-app parallel Modal CI.
- Return an actionable
github_registration_requires_approvalerror for Cloudroom's caller-proof gate without retries or security bypasses.
Verification
- 60 Node.js tests and 6 Python CI regression tests pass; Node.js 22 Modal CI passed for commit
5415e24947429ccb77138bdb8f01a08387ed7fd6. - Production dependency audit: zero known vulnerabilities at release validation.
- Clean tarball installation and the installed MCP executable's four-tool flow verified with a fake CLI.
- Live Personal spawn, unique-marker response, follow-up, incremental events, and stop verified on macOS / Node.js 26.13.0 / Cloudroom 142.0.0 / room-cli v142 using Codex (
gpt-6.1-sol,low). Stop does not delete the VM or thread.
Known limitation
A live attempt to register a missing GitHub project on Cloudroom v142 was refused with HTTP 401 caller_proof_required. Successful live GitHub registration/clone is not verified. Register missing repositories yourself in the trusted Cloudroom app, inspect projects, and resubmit the same spawn UUID and inputs. Existing matching projects skip this endpoint; Personal does not require it. The adapter does not forge caller proof or fall back to another execution target.
The default Devin model preset is unchanged and is not guaranteed to be available for every account. Configure a compatible provider/model/reasoning preset for your environment.
See CHANGELOG.md and the README for setup and limitations. The attached npm tarball and SHA-256 checksum cover the release artifact.
v0.1.0 — Initial release
Initial release
Cloud-only stdio MCP adapter for Cloudroom's room-cli, licensed under MIT.
Local Pi/Devin clients control execution; agents and workspaces run on Cloudroom Cloud VMs.
Included
- Exactly four tools:
thread_spawn,thread_tell,thread_get, andthread_stop. - Personal projects by default; optional allowlisted GitHub
owner/repositoryselection without local source uploads or checkout attachments. - Cloud defaults: provider
acp-devin, modelgpt-6-1-sol-high, reasoning levelhigh. - Explicit execution-setting verification, bounded output/deadlines, cross-process mutation locks, and no automatic write retries.
- MCP SDK v2, legacy 2025-11-25 stdio handshake support, and English/Korean setup documentation.
- Fixes for blank lock-directory configuration and cleanup errors overriding operation results.
Install
Use Node.js 22+ with a source checkout or extracted GitHub source archive:
npm ci
node server.mjsNo build step or npm package publication. The local Cloudroom control server and Cloud/provider authentication must already be configured. See the README for MCP client registration.
Verification
npm ci,npm run check, and all 55 tests passed.npm audit --omit=dev: 0 vulnerabilities.- Completed CodeRabbit implementation re-review: 0 findings.
- Integration coverage includes a real stdio MCP client, a legacy handshake, fake CLI operations, and mock HTTP repository registration.
Known limitations
- New GitHub registration through actual Cloud Devin execution has not been validated as one complete live E2E flow. No additional paid Cloud workloads were launched for this release.
- Repository registration uses an internal Cloudroom HTTP endpoint that may change across versions.
- Submission acceptance or an idle thread is not proof of task completion; correlate event IDs and sequences.
- Cloud agent execution can incur model and VM usage costs.