LearnHouse
Build, edit and run courses, learning paths and communities in your LearnHouse academy.
Plan EasyBuild recipes, CycloneDX SBOMs, and Resolvo stack locks.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 4/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 16/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Claude cannot connect eb-stack yet
The maker has not listed install details in the MCP Registry yet
ChatGPT cannot connect eb-stack yet
The maker has not listed install details in the MCP Registry yet
B · Others in Games, sports, food & learning that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Claude Code cannot connect eb-stack yet
The maker has not listed install details in the MCP Registry yet
Cursor cannot connect eb-stack yet
The maker has not listed install details in the MCP Registry yet
VS Code cannot connect eb-stack yet
The maker has not listed install details in the MCP Registry yet
cargo: eb_stackBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026
The registry name was verified with the GitHub account stackhands, which owns the repo
Code last changed today
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/stackhands-eb-stack)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed today, and the latest version (0.9.0) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Rust on your computer.
In the same category: LearnHouse, Anime Garden, WilmAI, Lumify Sports Intelligence, Savecraft
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Build, edit and run courses, learning paths and communities in your LearnHouse academy.
Finland's Wilma school system for parents and students: schedule, homework, exams and messages.
Schedules, scores, odds, splits & explainable AI bet confidence — 8+ sports, free instant key.
Savecraft serves real save game data and expert game knowledge to AI assistants.
| This one eb-stack | LearnHouse | Anime Garden | WilmAI | Lumify Sports Intelligence | Savecraft | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | Yes | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 5/5 | 4/4 | 3/3 | 4/4 | 3/4 |
| License | MIT | AGPL-3.0 | AGPL-3.0 | MIT | MIT | Apache-2.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Turn foreign and EasyBuild recipes into resolved, build-evaluated package bundles.
eb-stack parses conda-forge, Spack, PyPI, Comprehensive R Archive Network (CRAN), Cargo, LuaRocks, Raku, and EasyBuild recipes into one canonical package plan. It emits a planned CycloneDX Software Bill of Materials (SBOM), solves each product profile with Resolvo, writes one conventional .eb file per installable variant, and drives the recipes through a persisted remote build campaign.
A plan is not a build. package plan and package bump can establish only resolves. campaign run owns builds and binary-verified.
The GitHub release and the crates.io package are 0.7.4 and carry every command here.
The glossary defines closure, generation, baseline, and reachability. The longer path is the tutorial.
conda-forge / Spack / EasyBuild
│ ▼ canonical package.plan.json ─── package.sbom.cdx.json │ ▼ profile materialization + stack policy + Resolvo │ ├── locks/ .lock.json └── easyconfigs/ / / .eb │ ▼ target-routed campaign + typed findings
New packages and bumps use the same artifacts. A bump is an EasyBuild-origin plan plus SBOM and Resolvo lock, not a standalone text rewrite.
Report these claims independently:
package inspect establishes none of them. package plan and package bump can establish only resolves. campaign run owns the other two.
The crate is eb_stack on crates.io; the installed binary is eb-stack. Rust 1.90 or newer is required when building from source. rustc 1.83 stops while reading the crate index: the Cargo feature edition2024 is not stabilized. rustup toolchain install stable and rustup default stable provide a new enough compiler.
The GitHub release is 0.7.4, with installers and archives for Linux (x86-64, aarch64), macOS and Windows, and eb-stack --version prints 0.7.4 for it, as a build of this tree does. cargo install eb_stack --locked builds the same 0.7.4 from crates.io.
cargo binstall is not part of a Rust install. cargo binstall eb_stack fails with no such command: binstall until that program is installed on its own; it then installs the release binary.
From this checkout:
git clone https://github.com/stackhands/eb-stack.git
cd eb-stack cargo build --locked --release install -Dm755 target/release/eb-stack ~/.local/bin/eb-stack
Add ~/.local/bin to PATH. eb-stack --version then prints eb-stack 0.7.4. The test suite is cargo test --locked, in Tests. It is not required before the first solve.
Build the Rust binary on a suitable build host. EasyBuild installs belong on the target selected by the public target configuration, not necessarily on the machine running the CLI.
Documentation: https://eb-stack.rgoswami.me
The repository includes foreign-recipe and package-config fixtures, so the parsing boundary can be exercised without an EasyBuild installation or external robot tree:
eb-stack package inspect \
--source fixtures/foreign_ingest/conda_eon/recipe.yaml \ --format conda-forge \ --toolchain foss/2026.1 \ --package-config examples/packages/common.toml \ --package-config examples/packages/eon.toml \ --out-dir /tmp/eon-inspect
python3 -m json.tool /tmp/eon-inspect/package.plan.json >/dev/null python3 -m json.tool /tmp/eon-inspect/package.sbom.cdx.json >/dev/null
This writes the canonical build manifest and planned CycloneDX SBOM. It does not solve dependencies, emit recipes, or make a build claim; those stages need an EasyBuild robot tree and a configured build target.
The manual is organized around operator tasks:
The source manual lives in docs/orgmode/; the documentation workflow exports RST into docs/source/ and validates the Sphinx site.
eb-stack package bump \
--source tests/repro_fixtures/gromacs/GROMACS-2024.4-foss-2023b.eb \ --toolchain foss/2024a \ --easyconfigs tests/repro_fixtures/universe_foss_2024a \ --out-dir /tmp/gromacs-2024a
The output recipe is /tmp/gromacs-2024a/easyconfigs/g/GROMACS/GROMACS-2024.4-foss-2024a.eb; the same directory contains its manifest, SBOM, and default profile lock. Repeat --easyconfigs for overlays and use --stack-policy for European Environment for Scientific Software Installations (EESSI) or site preferences. preferred pins may fall back inside Resolvo; locked pins may not.
Known maintainer fixtures cover GROMACS, ScaFaCoS, MDTraj, Fiona, PuLP, and numba across foss-2023b to foss-2024a.
Package policy is public, layered TOML. Parsers preserve foreign names and syntax without package-name branches; Resolvo matches case/punctuation-equivalent robot names mechanically. Explicit ecosystem aliases, EasyBuild metadata, build policy, and independently installable profiles live in package config. Each profile emits one .eb file; Message Passing Interface (MPI) and OpenMP toolchain options alone do not require a suffix.
Profiles can declare platform and architecture target context. Foreign selectors are evaluated against those values before dependency solving, so a target-specific dependency becomes a real Resolvo requirement instead of disappearing with no message when planning runs on another host.
The Spack adapter parses Python into an abstract syntax tree (AST) without importing the recipe. It statically evaluates literal data, bounded loops, formatting, and when scopes; unsupported runtime expressions become source-located residuals rather than guessed dependencies.
Parser notes are informational. Planning consumes only typed residual records, so a note about successfully materializing dynamic source logic cannot accidentally enqueue Hermes work. Genuine residuals carry a category, severity, summary, and optional evidence and source provenance.
Conda revision numbers and compiler/stdlib/cross-build template requirements are toolchain diagnostics rather than package-authoring work. Unknown templates inside ordinary package identities remain explicit residuals.
Aliases use foreign = "EasyBuild" when both names share a version domain. Component-to-provider mappings use foreign = { provider = "EasyBuild", constraint = "drop" }, so a component release such as a Python package version is never imposed on its containing EasyBuild provider.
Package policy also has two generic EasyBuild inputs:
[build.easyconfig_parameters]
general_packages = ["ASPHERE", "KSPACE", "MOLECULE"]
[[build.patches]] filename = "Orbit-2.0-portability.patch" sha256 = "4f43b42fdcf84d0cf634d993dd944f252c8243dc612a919fe2825d56f937c8eb" source = "patches/Orbit-2.0-portability.patch"
[[dependencies.requirements]] name = "VTK" roles = ["run"]
By default, a layer that declares build.patches replaces the preceding patch list. Set patches_mode = "merge" in [build] to preserve patches extracted from conda-forge or Spack while adding EasyBuild policy patches. A merged entry with the same filename replaces that artifact, so a reviewed checksum and source path can refine foreign metadata without creating a duplicate.
Easyconfig parameters are typed data, not Python fragments. Requirements enter the canonical manifest and CycloneDX SBOM before Resolvo selects a version. Package planning requires every source and patch SHA-256; emitted checksums remain positional with sources first and patches second. Local patch assets are verified and copied beside every emitted recipe. Checksum-addressed remote patches retain their exact URL in patches; EasyBuild downloads and verifies them during the build.
scripts/fetch-upstream-trees.sh creates a checkout of the pinned easybuilders trees. Source the env.sh it writes so $EB_EASYCONFIGS is the develop easybuild/easyconfigs directory.
eb-stack package plan \
--source fixtures/foreign_ingest/conda_eon/recipe.yaml \ --format conda-forge \ --toolchain foss/2026.1 \ --package-config examples/packages/common.toml \ --package-config examples/packages/eon.toml \ --package-catalog examples/package-catalog/eon.toml \ --package-sources examples/package-sources/eon-companions.toml \ --easyconfigs "$EB_EASYCONFIGS" \ --easyconfigs fixtures/eon_foss_2026_1/easyconfigs \ --stack-policy examples/stacks/eon-foss-2026.1.toml \ --out-dir /tmp/eon
Against easybuild-easyconfigs develop 981d2123dd that prints:
closure_plan=/tmp/eon/closure.plan.json
closure_sbom=/tmp/eon/closure.sbom.cdx.json build_order=/tmp/eon/build-order.json manifest=/tmp/eon/package.plan.json sbom=/tmp/eon/package.sbom.cdx.json lock=/tmp/eon/locks/default.lock.json easyconfig=/tmp/eon/easyconfigs/e