Install the EIC MCP stack and opencode via spack packages - #357
Draft
aprozo wants to merge 10 commits into
Draft
Conversation
The eic-mcp launcher and every MCP server now come from eic-spack recipes and land in /opt/local/bin via the environment view (supersedes #328: no bundled script, no runtime clone/build). - xl/spack.yaml: add eic-mcp, rucio-eic-mcp-server, supergateway, uproot-mcp-server (xrootd-/zenodo-mcp-server were already in) - packages.yaml: version requires for the servers and bridge; py-mcp +cli
For headless LLM-client use inside eic-shell (farm nodes, CI reproducers). Installed from the per-platform GitHub release binary.
Points at aprozo/eic-spack feat/mcp-servers (develop@dd8a73e + the new recipes). Revert to eic/eic-spack at the merge SHA before undrafting.
py-typer (newest builtin: 0.23.2) pins py-click@:8.1.8, which cannot unify with the environment's click 8.3+ (flask via pyrobird). The MCP servers only need mcp core, so the eic-spack recipes default the cli variant off.
The previous pin predated py-mcp defaulting ~cli, so the typer/click conflict was still in the DAG. Also picks up the py-pyjwt import-test path fix, and drops the fork indirection now that the branch lives on eic/eic-spack.
aprozo
force-pushed
the
feat/eic-mcp-spack
branch
from
July 17, 2026 16:40
de3b9cd to
3d658cc
Compare
The MCP servers now speak streamable HTTP themselves and eic-mcp starts them directly, so the stdio bridge is gone from the environment. The three server pins move to '@main' — the only pin that builds before the v0.2.0 tags exist — mirroring the precedent eic-mcp already sets; flip them to '@0.2.0:' once the tags are pushed (grep TODO(push)).
Author
|
Pushed: supergateway dropped from spack.yaml/packages.yaml; the three server pins track |
# Conflicts: # eic-spack.sh # spack-environment/packages.yaml # spack-environment/xl/spack.yaml # spack-packages.sh
Both picks (#5637, #5639) verified to apply cleanly in sequence onto v2026.06.0.
Author
|
opencode is back in the env — via the now-merged upstream recipe (spack/spack-packages#5639, 55be3f7 added to the cherry-picks) instead of an eic-spack copy. |
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
1 participant
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.
Supersedes #328 (per review there: no bundled script, no runtime clone/build — everything installed properly via packages) and replaces #356 (same change from a fork, where CI has no secrets).
Three commits:
eic-mcp,rucio-eic-mcp-server,supergateway,uproot-mcp-server(xrootd/zenodo were already in); packages.yaml version requires +py-mcp +cli.eic-spack.shpoints at the recipes branch (EIC MCP servers and the eic-mcp launcher eic-spack#986 head, i.e. develop@dd8a73e + the new recipes). This commit is dropped/reverted to the merge SHA before undrafting.Why the current image ships a broken xrootd-mcp-server, test evidence (all recipe installs verified in
eicweb/eic_xl:nightly, 22/22 end-to-end launcher tests, MCP served on 9101–9104): see the eic-spack PR and eic/eic-mcp#1.Draft until the eic-spack PR merges and the pin is finalized.