Repository navigation
Conversation
|
The following comment was made by an LLM, it may be inaccurate: |
![opencode-agent[bot]](https://avatars.githubusercontent.com/in/1549082?s=60&v=4){kind=small}
There was a problem hiding this comment.
Looks good. I checked every claim against the v1.19.3 source of opencode mcp add and they all hold: a name is required to skip the prompts, you give either --url or a command after --, --header is remote-only and --env local-only, both can be repeated and use KEY=VALUE (split at the first =), header values are stored as typed so {env:GITHUB_TOKEN} stays a literal reference, and adds without prompts go to the global config. Both config links point to existing headings.
Public API impact: none, this is documentation only.
No blocking concerns.
|
Maintainer CI-approval follow-up for this documentation-only PR, cross-referencing the existing request on #57233: At the current head
All three report The PR standards/compliance checks have passed. Independent fork verification is documented in the PR description, but it does not replace the required upstream checks. Could a maintainer approve the pending workflow runs, or confirm whether a different verification path is appropriate for this documentation-only change? Thanks for your time! |
Issue for this PR
Closes #55285
Type of change
What does this PR do?
The English and Simplified Chinese V1 CLI pages only show interactive
mcp add. Document the existing non-interactive remote/local forms, repeatable header/environment flags, literal{env:GITHUB_TOKEN}references, and V1's global-config destination.Earlier attempts (#32283, #32886, #32267) were closed unmerged by automated cleanup/template checks; these additions are still absent. No runtime behavior or V2 documentation changes.
How did you verify your code works?
Checked the flags, global-config write, and variable substitution against
v1.19.3source. New passages pass Prettier 3.6.2; both languages use identical commands, Bash syntax passes, and the links target existing configuration headings.bun run checkandpackages/webbun run buildpassed against this exact two-file candidate.[email protected]passed both documented commands and repeated-header/environment controls in fresh HOME/XDG directories with stdin closed. Checks assert global V1mcp[name]configuration, literal header references, values containing=, and command flags after--.The CLI checks only write configuration; they do not start an MCP server, connect to GitHub, authenticate, or call a model.
AI assistance was used to prepare and check this documentation change.
Screenshots / recordings
N/A — documentation only.
Checklist