[FEATURE]: The documentation needs to include instructions for usage like `opencode mcp add github --url https://api.githubcopilot.com/mcp --header "Authorization=Bearer {env:GITHUB_TOKEN}"`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- cli, documentation
Research direction
The gap is in the MCP section of the CLI reference at https://opencode.ai/docs/zh-cn/cli/#mcp. Read pull request 31054 first to see how mcp add now accepts --url and --header, and how {env:...} is interpolated. Done means the section shows a working opencode mcp add example with a header that reads a token from an environment variable, matching the behaviour in that pull request.
Written by the indexing model from the issue text.
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
- The documentation needs to include instructions for usage like
opencode mcp add github --url https://api.githubcopilot.com/mcp --header "Authorization=Bearer {env:GITHUB_TOKEN}". - Although support for this type of CLI syntax was added at https://github.com/anomalyco/opencode/pull/31054 , there is no related documentation at https://opencode.ai/docs/zh-cn/cli/#mcp .
- Also see https://github.com/anomalyco/opencode/issues/32259#issuecomment-5288848611 .
- Also see https://github.com/anomalyco/opencode/issues/42484#issuecomment-6159310026 .
- Dominant language
- TypeScript
- Stars
- 213k
- Forks
- 28.4k
- Avg merge
- 8h 51m
- Merged PRs (30d)
- 289
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from anomalyco/opencode
-
reproduced
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
anomalyco/opencode#55369 · 1 comment ·
Maintainers usually reply within 1 day
-
reproduced
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
anomalyco/opencode#55351 · 1 comment ·
Maintainers usually reply within 1 day
-
opencode on clean macos zsh .export path not working because it append and it fails because no ~/.zshrc filePossibly taken @fihaaade claimed this 1 day ago. Openreproduced
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
anomalyco/opencode#55068 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anomalyco/opencode#54919 · 1 comment ·
Maintainers usually reply within 1 day
-
triaging
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
anomalyco/opencode#54887 · 1 comment ·
Maintainers usually reply within 1 day
All issues in anomalyco/opencode
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
vercel/streamdown#673 · 1 reaction ·
Maintainers usually reply within 1 day
-
docs(stream-protocol): document messageMetatadata on start/finish and the message-metadata chunkOpenfactory-active task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
agilepathway/label-checker#721 ·
Maintainers usually reply within 1 day
-
CLI Empathy needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
chromaui/chromatic-cli#1524 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day