You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
cloudfall-mcp lacks the fleet-declaring tools: add ssh-key, server-type, server #3
cloudfall-mcp is the agent's entry point to Cloudfall, but two commands that start a project's life are missing from it: init (lay out a project) and add ssh-key|server-type|server (declare the fleet). The readiness evaluation of 2026-09-14 counted 20 of 26 CLI leaf commands covered by the MCP server and listed init, add, and dashboard as absent.
The result is that an agent operating through MCP can validate, audit, plan, and deploy, but cannot declare the first server. It has to fall back to writing YAML by hand, which is precisely the guessing that cloudfall add exists to remove (schema-validated document, project validated afterwards, failed validation rolled back, existing resources never overwritten).
each returning the same envelope as the CLI. init is a judgment call: the MCP server already runs inside a project, so init may belong to the CLI only. Decide and document it either way.
Acceptance
The three add_* tools appear in the tool list and are covered by sdk/tests/test_agent_tools.py
The MCP instructions string tells the agent these tools write resources into the project and that the project is re-validated afterwards
Implemented in 206f719: cloudfall-mcp now exposes add_ssh_key, add_server_type, and add_server, each returning the cloudfall add envelope, writing into the project only, and re-validating it. They are covered in sdk/tests/test_agent_tools.py, described in the MCP instructions string, and listed in sdk/README.md. cloudfall init stays CLI-only: the server refuses to start outside a project, so the project exists before any tool can be called.
Triage: close confirmed. The triage script flagged this as a hand-close with no merged PR, but the fix went straight to main in 206f719, which is an ancestor of the current main.
Checked again on main after the treaty port (#14):
add ssh-key, add server-type and add server are treaty commands without mcp=False, so cloudfall mcp serve still exposes them as tools (sdk/src/cloudfall/app.py). Only init, dashboard serve and two others opt out
sdk/README.md still lists add_ssh-key, add_server-type and add_server
init stays CLI-only, as decided above
One gap, not a reason to reopen: sdk/tests/test_agent_tools.py went away in the port. sdk/tests/test_authoring.py tests the add_* functions, but no MCP-level test checks that the three tools show up in the tool list. The test at sdk/tests/test_agent_server.py that reads --list-tools would be an easy place to add that check.
Triage: close confirmed again (206f719 is on main). It stays closed. The gate keeps re-flagging this hand-close every tick; the question of how to stop that waits on #31.
Triage: close confirmed. The fix, 206f719, is on main, checked 2026-10-11. This marker clears SUSPECT_CLOSE, so the gate stops re-flagging this issue. It comes back only if the issue is reopened and closed again.
Activity
romamo commentedon Sep 14, 2026
Implemented in 206f719:
cloudfall-mcpnow exposesadd_ssh_key,add_server_type, andadd_server, each returning thecloudfall addenvelope, writing into the project only, and re-validating it. They are covered insdk/tests/test_agent_tools.py, described in the MCP instructions string, and listed insdk/README.md.cloudfall initstays CLI-only: the server refuses to start outside a project, so the project exists before any tool can be called.mcp: add the fleet-declaring tools add_ssh_key, add_server_type, add_…
evaluations: add the 2026-09-14 CLI agent audit of cloudfall 0.1.0
shipmill-romamo commentedon Oct 8, 2026
Triage: close confirmed. The triage script flagged this as a hand-close with no merged PR, but the fix went straight to main in 206f719, which is an ancestor of the current
main.Checked again on
mainafter the treaty port (#14):add ssh-key,add server-typeandadd serverare treaty commands withoutmcp=False, socloudfall mcp servestill exposes them as tools (sdk/src/cloudfall/app.py). Onlyinit,dashboard serveand two others opt outsdk/README.mdstill listsadd_ssh-key,add_server-typeandadd_serverinitstays CLI-only, as decided aboveOne gap, not a reason to reopen:
sdk/tests/test_agent_tools.pywent away in the port.sdk/tests/test_authoring.pytests theadd_*functions, but no MCP-level test checks that the three tools show up in the tool list. The test atsdk/tests/test_agent_server.pythat reads--list-toolswould be an easy place to add that check.shipmill-romamo commentedon Oct 10, 2026
Triage: close confirmed again (206f719 is on
main). It stays closed. The gate keeps re-flagging this hand-close every tick; the question of how to stop that waits on #31.shipmill-romamo commentedon Oct 11, 2026
Triage: close confirmed. The fix, 206f719, is on
main, checked 2026-10-11. This marker clears SUSPECT_CLOSE, so the gate stops re-flagging this issue. It comes back only if the issue is reopened and closed again.