hve-squadmcp
An outbound Model Context Protocol server that exposes the hve-squad as coarse, model-invocable tools — so an MCP host can call the squad directly instead of reimplementing it.
What this is
hve-squad ships a multi-agent squad — a coordinator, a roster of role personas, and a council that returns a most-restrictive-wins verdict. That squad normally runs inside a host that installed the package. This server turns it inside out: it is the squad's own MCP server, which other hosts consume.
It is the outbound inverse of the squad's inbound MCP template. The generator reads the deployed squad sources read-only and never duplicates agent logic, so the single source of truth for behaviour stays the personas and the routing instructions — not this package.
Two execution modes
Be precise about which one a claim refers to. They are at different maturity levels.
| Mode | Host | State | Behaves as the full package? |
|---|---|---|---|
| Delegated (stdio) | VS Code GitHub Copilot, local | works | Yes. VS Code dispatches the real deployed cast. Needs the built package plus an
apm install of the cast. |
| Embedded advisory | Copilot Studio, remote HTTP | works | Advisory parity. Each call runs one server-side dispatch against the real from-disk persona from the bundled cast, under Entra auth, gates, tenant isolation and cost caps. Text only. |
| Embedded async pipeline | Copilot Studio, remote HTTP | opt-in | Advisory parity, full cast. Data-driven routing runs research → plan → council → review → backlog and produces one sectioned artifact. Off by default. |
| Deterministic render | Copilot Studio, remote HTTP | opt-in | File output. Renders content YAML to a .pptx and returns a short-lived
user-delegation SAS link. No model call. |
| Code-executing implement / deploy | — | deferred | A real tool-calling backend and a persistent workspace. Not available — do not represent it as such. |
Bottom line. Deploy this and you get the full package locally in VS Code, the advisory tools in Copilot Studio today, and — with the pipeline enabled — the full advisory squad running end to end as an async pipeline. Advisory scope means finished text deliverables.
Where to go next
Scenario: idea → backlog
The full walkthrough — deploy, run the product profile from Copilot Studio, and create the epics, stories, and tasks in Azure DevOps, Jira, or GitHub.
Getting started
Build the server and register it in VS Code so Copilot can call the squad locally.
Tools
Every tool on the surface, the scope it needs, and where it is reachable from.
Deploy
Ship the remote HTTP server to Azure Container Apps and reach it from Copilot Studio.
Configuration
Operator settings, storage backends, and the automatic squad memory the server writes.
Contributing
The release contract, the cast pin, and the security invariants a change must hold.
Decision record
ADR-0001: why the surface is split into delegated and embedded, and where the trust boundary sits.
The trust boundary
This server never writes to Azure DevOps, Jira, or GitHub. It produces the plan; a certified native connector performs every write on the end user's own connection, under that connector's auth, DLP, and throttles. Caller input is always data, never instruction — only a persona charter carries authority. Every store path is tenant-scoped and traversal-guarded.