Model Context Protocol server

eb-stack mcp serves the version-one commands on stdin and stdout. One JSON-RPC object occupies one line. --workspace sets the root for the recipe file tools and exports EB_STACK_WORKSPACE for that process. When the flag is omitted, an existing EB_STACK_WORKSPACE is kept. Otherwise the server uses its current directory. eb-stack mcp --help prints those flags and exits 0.

The registry manifest is server.json at the repository root. The file uses the 2025-12-11 server schema (server.schema.json). The server name is io.github.stackhands/eb-stack. The package is the cargo crate eb_stack at the version in Cargo.toml, from https://crates.io, with transport stdio. One positional argument is mcp. --workspace is an optional named argument. Cargo installs the binary named eb-stack. The manifest has no runtime hint: cargo install runs once, and the client then runs that binary by name.

Build the binary

Rust 1.90 or newer builds this tree. The binary that the snippets below call is eb-stack.

cargo build --locked --release
install -Dm755 target/release/eb-stack ~/.local/bin/eb-stack
eb-stack mcp --help

Clients with an mcpServers file

A desktop client that reads a JSON file with a top-level mcpServers key takes the entry below. Restart the client after saving the file. A client that does not expand ${workspaceFolder} needs an absolute path in --workspace.

{
  "mcpServers": {
    "eb-stack": {
      "command": "eb-stack",
      "args": ["mcp", "--workspace", "/absolute/path/to/the/clone"]
    }
  }
}

Visual Studio Code and Copilot

A portable file uses a top-level mcpServers object. The Visual Studio Code file uses a top-level servers object. Copying one file onto the other without changing that key drops the server.

The Visual Studio Code file is .vscode/mcp.json in the workspace, or mcp.json in the user profile. ${workspaceFolder} expands in that file. type is stdio.

{
  "servers": {
    "eb-stack": {
      "type": "stdio",
      "command": "eb-stack",
      "args": ["mcp", "--workspace", "${workspaceFolder}"]
    }
  }
}

A workspace-root .mcp.json uses mcpServers. The Copilot user file does too. That user file is $COPILOT_HOME/mcp-config.json, or ~/.copilot/mcp-config.json when COPILOT_HOME is unset. A portable file does not expand Visual Studio Code input variables. Pass an absolute path there.

{
  "mcpServers": {
    "eb-stack": {
      "command": "eb-stack",
      "args": ["mcp", "--workspace", "/absolute/path/to/the/clone"]
    }
  }
}

Tools

The catalog has 60 tools. tools/list returns one tool for each CLI command in the table, and the recipe and easyblock tools that have no command. mcp publishes that catalog and has no tool of its own. Each command’s tool calls the same runner as that command. The text field of a successful result is that command’s stdout. Each argument is a name in the schema tools/list returns. The CLI reference records the flags.

Command

Tool

package inspect

eb_package_inspect

package plan

eb_package_plan

package bump

eb_package_bump

package latest

eb_package_latest

recipe easyblock

eb_recipe_easyblock

recipe templates

eb_recipe_templates

recipe hierarchy

eb_recipe_hierarchy

recipe check

eb_recipe_check

recipe lint

eb_recipe_lint

recipe format

eb_recipe_format

stack solve

eb_stack_solve

stack sbom

eb_stack_sbom

stack order

eb_stack_order

stack gap

eb_stack_gap

stack provided

eb_stack_provided

stack shadow

eb_stack_shadow

stack batch

eb_stack_batch

stack shard

eb_stack_shard

stack capacity

eb_stack_capacity

stack footprints

eb_stack_footprints

stack admit

eb_stack_admit

stack easystack

eb_stack_easystack

stack sections

eb_stack_sections

stack from-commit

eb_stack_from_commit

stack arch

eb_stack_arch

stack files

eb_stack_files

stack generation

eb_stack_generation

stack cuda-cc

eb_stack_cuda_cc

stack known-failures

eb_stack_known_failures

stack oom

eb_stack_oom

stack bot-classify

eb_stack_bot_classify

target list

eb_target_list

target doctor

eb_target_doctor

campaign run

eb_campaign_run

campaign status

eb_campaign_status

campaign finding claim

eb_campaign_finding_claim

campaign finding resolve

eb_campaign_finding_resolve

repro summary

eb_repro_summary

ledger append

eb_ledger_append

ledger head

eb_ledger_head

ledger tiles

eb_ledger_tiles

ledger find

eb_ledger_find

ledger show

eb_ledger_show

ledger verify

eb_ledger_verify

easyblock-reach

eb_easyblock_reach

pr-overlap

eb_pr_overlap

rebuild-set

eb_rebuild_set

component-reach

eb_component_reach

These tools edit files or run EasyBuild. They are not CLI commands.

Tool

Role

eb_recipe_read

Read one UTF-8 file inside the workspace root

eb_recipe_list

List one directory inside the workspace root

eb_recipe_edit

Replace an exact string in a workspace file

eb_recipe_apply_suggestion

Apply a review suggestion to the lines it is anchored on

eb_recipe_diff

Show what changed in each recipe since the server first saw it

eb_recipe_write

Create or overwrite a UTF-8 file inside the workspace root

eb_recipe_grep

Search workspace files for a literal, or a regular expression

eb_dep_versions

List easyconfig versions of one dependency in a local tree

eb_module_lint

Check Python modules that ship with recipes

eb_easyblock_dry_run

Run eb -x and return the commands the easyblock generates

eb_build_log

Read an EasyBuild log by step

eb_build_test

Run a build

eb_build_test runs only when EB_STACK_ALLOW_BUILD=1.