Ecosystem
The squad ships through three repositories. This one is the source of truth; the other two are distribution surfaces that carry the same cast to hosts an APM install cannot reach.
The three repositories#
| Repository | What it is | Documentation |
|---|---|---|
hve-squad |
This repository. The APM package and the authored squad source (squad-src/) that both other repositories are built from. |
peter-n91.github.io/hve-squad |
hve-squad-mcp |
An outbound Model Context Protocol server that publishes the squad as model-invocable tools, so MCP hosts can call it. | peter-n91.github.io/hve-squad-mcp |
hve-squad-plugin |
A generated, release-gated mirror of the squad's GitHub Copilot CLI plugin tree, published as a plugin marketplace. | peter-n91.github.io/hve-squad-plugin |
One cast, three doors. The roster, routing tables, and gates are authored
once here. The MCP server and the plugin do not fork that behavior — each is built
from a tagged hve-squad release, so a given version of any surface corresponds
to a known version of this package.
Which surface do I want?#
| If you want to… | Use | Install |
|---|---|---|
| Select the Squad Coordinator agent in VS Code Copilot Chat with the full cast in your repository | This APM package | apm install — see Getting Started |
| Run the squad from the GitHub Copilot CLI or the desktop app, with no APM install | hve-squad-plugin |
copilot plugin marketplace add |
| Call the squad as tools from an MCP host such as Copilot Studio | hve-squad-mcp |
stdio server locally, or a deployed HTTP endpoint |
hve-squad-mcp — the MCP server#
github.com/Peter-N91/hve-squad-mcp · docs site
The server exposes coarse, model-invocable tools that map onto the squad's routing intents
rather than onto individual agents: squad_research, squad_plan,
squad_review, squad_architect, squad_run, and
squad_federate, plus a deterministic squad_render_pptx file-output
tool. Every tool's input mirrors the /squad prompt arguments.
It runs in two modes, at different maturity levels:
- Delegated (stdio) — VS Code dispatches the real deployed cast, so it behaves as the full package. Requires the cast to be installed.
- Embedded (remote Streamable HTTP + Entra) — reaches hosts such as Copilot Studio, resolving personas server-side from the bundled cast under auth, gates, tenant isolation, and cost caps. Scope is advisory: finished text deliverables, not code-executing implement or deploy.
Read the status table first. The server's README and docs site are explicit about what works today versus what is a deferred execution expansion. Take claims about the remote surface from there rather than from this page.
Useful entry points on its site: Getting Started, Tools, Configuration, and Deploy.
hve-squad-plugin — the Copilot CLI plugin#
github.com/Peter-N91/hve-squad-plugin · docs site
That repository is generated output, never hand-edited. Its agents/,
skills/, and .github/plugin/plugin.json are regenerated by
scripts/Build-SquadPlugin.ps1
only when this repository cuts a release, extracted from that release's immutable git tag.
It exists so the distribution tree lives outside this working tree, mirroring the
hve-squad-mcp sibling-repo pattern.
The marketplace publishes two entries, installed as a pair:
copilot plugin marketplace add Peter-N91/hve-squad-plugin
copilot plugin install hve-squad@hve-squad-plugin
copilot plugin install hve-squad-hve-core@hve-squad-plugin
Two rules govern every later update. hve-squad-hve-core must be
uninstalled and reinstalled rather than updated — copilot plugin update
compares upstream hve-core's own version, so a moved pin reports already at latest
and the files never change. And do not also install the official hve-core
plugin next to it, or a dispatch can land on an unpinned second copy of every hve-core agent.
Both rules are explained in full on
Install: Copilot CLI.
Useful entry points on its site: Install: Copilot CLI, Install: Desktop app, Install: VS Code notes, Architecture, and Enterprise Push.
How releases stay aligned#
Neither sibling repository is a fork. Both are produced from a tagged
hve-squad release, and each records the tag it was built from — the plugin
repository states its source tag and extraction date in its README, and each MCP release is
pinned to a matching package version. When this repository cuts a release, the downstream
surfaces are regenerated from it rather than drifting on their own schedule. See
Maintaining for the release process on this side.