Repository navigation
docs: connect an AI agent to the hosted MCP server or dcd mcp - #164
Open
finalerock44 wants to merge 4 commits into
Open
finalerock44 wants to merge 4 commits into
finalerock44 wants to merge 4 commits into
Conversation
A new page, Connect an AI Agent, sets up every client against both ways in: the hosted server (Claude Code, Cursor, VS Code, Claude Desktop, Codex and other OAuth clients), its read-only URL and API-key sign-in, and dcd mcp through the CLI, with dcd mcp install and the configs by hand. It also covers Connected apps, and points dcd-mcp users at the existing MCP Server page.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
…sion Review follow-ups on the Connect an AI Agent page: - The pages that said the standalone binary has no MCP server meant dcd-mcp, which is still npm-only. They now say both installs have dcd mcp, and the dcd-mcp page points new setups at Connect an AI Agent. - The MCP servers renew a dcd login session as they run, so the warnings that a long-running server stops when the session expires were out of date (api-keys, dcd login, MCP Server). An API key is still the advice for agents that run unattended. - API keys gets an Access section (Full access, Device sessions only), which the agent page links to. - Connect an AI Agent says to update the CLI when dcd mcp, or a client in dcd mcp install, is missing.
"gives an AI agent such as ... the tools to" ran the client list into the second object. It now reads "lets an AI agent, such as ..., drive cloud devices and run cloud tests".
Code reviewI found no bugs. The JSON, TOML and shell snippets are valid. Every relative link resolves, and so does the new CLAUDE.md says: "Flag a doc change that names a flag, input or endpoint the rest of the docs don't use, so a reviewer can confirm it exists." This PR names several. Please confirm they exist in the current CLI and API:
🤖 Generated with Claude Code |
The page now covers dcd mcp, the MCP server in the CLI, for running cloud tests from an AI agent: setting it up with dcd mcp install, running it headless with an API key (for example in CI), configs by hand, its dcd_* tools and read-only mode, and the older dcd-mcp. The CLI Reference and MCP Server pages point at it the same way.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A new page, Connect an AI Agent, sets up every client against both ways in: the hosted server (Claude Code, Cursor, VS Code, Claude Desktop, Codex and other OAuth clients), its read-only URL and API-key sign-in, and dcd mcp through the CLI, with dcd mcp install and the configs by hand. It also covers Connected apps, and points dcd-mcp users at the existing MCP Server page.