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
'Device automation MCP tools use semantic command contracts and execute through the agent-device client.',
74
-
installRequiresHumanApproval: true,
75
-
installSafetyNote:
76
-
'Agents should not install or update the package unless the human has approved the environment change. If the CLI is missing, ask the human to run the install command, then run the verify command.',
77
61
};
78
62
}
79
63
@@ -111,14 +95,6 @@ export function listTools(): unknown[] {
Copy file name to clipboardExpand all lines: website/docs/docs/agent-setup.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ Use MCP tools or the CLI in the integrated terminal. If `agent-device` is not on
54
54
55
55
## MCP server
56
56
57
-
`agent-device mcp` starts the official stdio MCP server. It exposes direct semantic tools for installed CLI commands, plus a `status` tool that returns package, install, verify, and help metadata. Tools run through semantic command contracts and `AgentDeviceClient`; local-only workflows are explicit boundaries rather than subprocess fallbacks.
57
+
`agent-device mcp` starts the official stdio MCP server. It exposes direct semantic tools for installed CLI commands, plus a `status` tool that returns package, install, verify, help, target, and capability metadata. Tools run through semantic command contracts and `AgentDeviceClient`; local-only workflows stay CLI-only rather than subprocess fallbacks.
58
58
59
59
MCP clients must not use this server as a generic shell runner. If the CLI is missing, agents should ask a human before installing or updating packages, then verify with `agent-device --version` and start with `agent-device help workflow`.
Copy file name to clipboardExpand all lines: website/docs/docs/commands.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ For MCP-aware clients that support direct tools, run:
29
29
agent-device mcp
30
30
```
31
31
32
-
The MCP server exposes direct semantic tools for installed commands. Tools use semantic input contracts through `AgentDeviceClient`; local-only workflows are explicit boundaries rather than subprocess fallbacks. It does not expose generic shell execution over MCP.
32
+
The MCP server exposes direct semantic tools for installed commands. Tools use semantic input contracts through `AgentDeviceClient`; local-only workflows stay CLI-only rather than subprocess fallbacks. It does not expose generic shell execution over MCP.
Copy file name to clipboardExpand all lines: website/docs/docs/security-trust.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ description: Security and trust guidance for agent-device local app automation,
10
10
## Local control
11
11
12
12
- Device automation runs through the installed CLI and platform tooling such as Xcode, ADB, macOS accessibility APIs, and Linux AT-SPI.
13
-
- The MCP server exposes direct semantic tools for `agent-device` commands. Tools use semantic contracts through `AgentDeviceClient`; local-only workflows are explicit boundaries rather than subprocess fallbacks. It does not expose generic shell execution over MCP.
13
+
- The MCP server exposes direct semantic tools for `agent-device` commands. Tools use semantic contracts through `AgentDeviceClient`; local-only workflows stay CLI-only rather than subprocess fallbacks. It does not expose generic shell execution over MCP.
14
14
- Mutating commands should run serially against one session. Use separate sessions/devices for parallel work.
0 commit comments