Let Claude Code users set the docs MCP server URL with VAADIN_DOCS_MCP_URL
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 35/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- json, markdown, python
調査の方向性
The server is declared in .mcp.json and the Claude-only declaration would go in .claude-plugin/plugin.json. The URL check lives in scripts/check_plugin.py, which needs to accept the ${VAADIN_DOCS_MCP_URL:-https://...} form, and the user-facing steps are in plugin/README.md. Done means both manifests resolve to the same URL once the default is substituted, the check script passes, and the README describes the variable. The release review against the Claude plugin directory is a separate maintainer step.
索引モデルが issue の本文から書いたものです。
説明
Customers on air-gapped networks may run their own Vaadin documentation MCP server. The plugin's .mcp.json hard-codes https://mcp.vaadin.com/docs, so today they have to block the hosted server and add their own by hand.
Proposal
Let Claude Code users point the vaadin server at their own URL with an environment variable that defaults to the hosted one:
"url": "${VAADIN_DOCS_MCP_URL:-https://mcp.vaadin.com/docs}"
An admin could set it for a whole organization through env in managed settings. The server keeps its name and its tools, so the skills don't change.
What I checked (Claude Code 2.1.318, Codex 0.163)
- Claude Code expands
${VAR:-default}in a plugin MCP server'surl. It reads the value from the shell and fromenvin settings. - Codex reads the same
.mcp.jsonand doesn't expand variables, so it would use the URL literally and the server would fail. In Codex's source (0.167), only${PLUGIN_ROOT}and${PLUGIN_DATA}are expanded, and only for stdio servers. Codex plugins also have no settings mechanism. - So the variable can't go in the shared
.mcp.json. What works is a Claude-only declaration undermcpServersin.claude-plugin/plugin.json. Claude Code loads it together with.mcp.json, and on a name clash it used the inline server. Codex reads only.mcp.json, through its own manifest. claude plugin validate --profile directoryraised nothing about the variable in the URL.
To do
- Declare the
vaadinserver inline in.claude-plugin/plugin.jsonwith the variable in its URL. Leave.mcp.jsonas it is for Codex. - Extend
scripts/check_plugin.pyso the two declarations can't drift: the same URL once the variable's default is substituted. Its https check needs to accept${VAADIN_DOCS_MCP_URL:-https://…}. - Document the variable in
plugin/README.md, replacing the block-and-add steps for Claude Code. - Before release, check that the Claude plugin directory's review accepts the variable in the URL, and that installs from claude.ai and Cowork still reach the hosted server.
Notes
- That the inline server wins over the same-named one in
.mcp.jsonis what Claude Code did in testing. I didn't find it documented. - A
VAADIN_DIRECTORY_MCP_URLwould only be useful if a self-hosted Directory server exists. - I left out Claude Code's
userConfig(prompted plugin settings). It asks users for the value when they enable the plugin, and the docs don't confirm that an admin can fill it in for them. - Codex users would keep replacing the server in
config.toml: a[mcp_servers.vaadin]entry takes the place of the plugin's server of the same name. That works in 0.163 but OpenAI doesn't document it.
- 主要言語
- Go
- スター
- 0
- フォーク
- 0
- 平均マージ
- 4日 10時間
- マージ済み PR(30日)
- 3
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
似ている issue
-
難易度 1/5 1時間未満 初心者へのやさしさ 86/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 64/100
projectdiscovery/cdncheck#554 ·
メンテナーはふだん 1 日以内に返信
-
triage needed
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 78/100
OpenSlides/openslides-go#342 ·
メンテナーはふだん 4 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 77/100