Skip to content

fix(device): fit start's next steps to the session, and explain dcd mcp - #266

Merged
riglar merged 2 commits into
devfrom
docs/mcp-help-readme
Oct 26, 2026
Merged

riglar merged 2 commits into
devfrom
docs/mcp-help-readme

Conversation

@riglar

@riglar riglar commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

What

dcd device start next steps

  • The next steps were always the same three, so a queued session was told to run dcd device inspect, which then failed ("No screen hierarchy yet").
  • Now, when the device isn't ready, the first step is dcd device status <id>, plus a hint that start --wait waits for it.
  • When no app was given, it suggests dcd device install <id> <app>.
  • It ends with dcd device --help, so it's clear the list isn't everything.
  • The logic is in a new startNextSteps helper, with a unit test.

dcd mcp help text

  • Now reads "MCP server for AI agents, started by your MCP client (Claude, Cursor, VS Code)". The old line didn't say a person isn't meant to run it.

README

  • The MCP section only covered dcd-mcp. It now opens with a table comparing dcd mcp, the hosted https://api.devicecloud.dev/mcp and dcd-mcp, documents dcd mcp (config, sign-in, --read-only, local uploads, device tools), and shows how to add the hosted endpoint.

Testing

pnpm typecheck, pnpm lint (0 errors) and pnpm test:unit (461 passing).

Related

devicecloud-dev/dcd#1820 proposes a dashboard config generator for the MCP setup.

🤖 Generated with Claude Code

Reword the dcd mcp help line so it is clear an MCP client starts it,
not a person. Add a README section on dcd mcp and the hosted endpoint,
next to the existing dcd-mcp docs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@claude

claude Bot commented Oct 26, 2026

Copy link
Copy Markdown

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

This PR changes only docs: the README's MCP section and the one-line dcd mcp description string. I checked the documented behaviour (--read-only / DCD_MCP_READONLY, falling back to dcd_* tools only when the hosted server can't be reached) against src/commands/mcp.ts and src/mcp/bridge.ts, and it matches. No tests or other files refer to the old description string.

A queued or provisioning session can't be inspected yet, so start now
suggests dcd device status first and points at --wait. It suggests
install when no app was given, and ends with dcd device --help.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@riglar riglar changed the title docs(mcp): say the mcp command is for MCP clients to start fix(device): fit start's next steps to the session, and explain dcd mcp Oct 26, 2026
@riglar
riglar merged commit 13a7158 into dev Oct 26, 2026
10 checks passed
@riglar
riglar deleted the docs/mcp-help-readme branch October 26, 2026 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant