Install the EIC MCP stack and opencode via spack packages#356
Closed
aprozo wants to merge 3 commits into
Closed
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 eic#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.
Author
|
Superseded by #357 (same change from an org branch so CI gets credentials). |
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.
Draft — CI test build for the MCP packaging restructure (supersedes #328, per Wouter's review there: no single-file script in this repo, no runtime clone/build; everything installed properly via packages).
What
eic-mcp,opencode,rucio-eic-mcp-server,supergateway,uproot-mcp-server(xrootd-mcp-server/zenodo-mcp-serverwere already in).py-mcp +cli.containers/eic/eic-mcpand its DockerfileCOPY— the launcher now comes from theeic-mcpspack package (repo: eic/eic-mcp, reworked to service management only in Service management only: serve installed servers, never build or fetch eic-mcp#1) and lands in/opt/local/binvia the view.aprozo/eic-spack@feat/mcp-serverswhich carries the new recipes (py-mcp + missing deps, the servers, supergateway, opencode, py-pyjwt 2.10.1 override). Will be reverted toeic/eic-spackat the merge SHA once the eic-spack PR lands — keeping this PR draft until then.Why the current image ships a broken xrootd-mcp-server
npm install --global .from a git checkout never compiled the TypeScript (released tags have nopreparehook), andbuild/is gitignored with nofileslist sonpm packdrops the compiled tree anyway. The updated recipes build explicitly and neutralize the ignore; verified ineicweb/eic_xl:nightlythat the fixedxrootd-mcp-server/zenodo-mcp-serverinstalls shipbuild/src/index.jsand runnable console commands.Testing done (locally, inside eicweb/eic_xl:nightly)
eic-mcp upwith the installed servers → MCP initialize + tools/list served on ports 9101–9104 (11/16/13/9 tools), two concurrent clients OK, config writers for 7 LLM clients validated, port-conflict/stale-pidfile/missing-server edge cases pass, and no git/pip/npm/npx is ever spawned at runtime.opencode --versionruns inside the image (glibc OK).