
hass-mcp-admin
by jeter-1
HA MCP Engineering Server
Stable v1.1.2 under
hass_mcp_adminis retained as historical repository source but is operationally retired. It is not covered by the Engineering dependency audit and is not a supported rollback option. The Engineering v2 add-on is developed in place at2.2.0-beta.6, based on the exactv2.0.1release, athass_mcp_engineering_beta/on port8100. Its existing technical “Beta” identity is retained to avoid a slug or runtime identity migration. SeeV2_BETA_ARCHITECTURE.mdbefore installing or migrating tools. Historical beta release and cache-refresh procedures are documented indocs/BETA_DEPLOYMENT.md. The beta approval workflow is documented indocs/CHANGE_GOVERNANCE.md. The facilitator decision and bounded-response contract are documented indocs/architecture/ADR-002-ENGINEERING-MCP-FACILITATOR.mdanddocs/TOKEN_EFFICIENCY.md. Beta 11 System Log security and Beta 12 connector-cache guidance are documented indocs/BETA_DEPLOYMENT.md. Beta 14 trace/time stabilization is documented indocs/AUTOMATION_RELIABILITY_ANALYSIS.md, and Beta 15 change-impact analysis is documented indocs/CHANGE_IMPACT_ANALYSIS.md. Beta 17 global configuration-integrity analysis and the Beta 18 reference classifier hardening are documented indocs/CONFIGURATION_INTEGRITY_ANALYSIS.md. Beta 24 pre-RC hardening, trusted-proxy setup, and bounded audit reads are documented indocs/BETA_24_RELEASE_NOTES.md,docs/RATE_LIMITING.md, anddocs/AUDIT_LOG.md. Beta 25 external human approval is documented indocs/EXTERNAL_APPROVAL.mdanddocs/BETA_25_RELEASE_NOTES.md. Beta 26 expiry lifecycle hardening is documented indocs/BETA_26_RELEASE_NOTES.md. RC2 release and deployed acceptance procedures are indocs/RC2_RELEASE_NOTES.mdanddocs/RC2_ACCEPTANCE.md. The Phase 1 single-server architecture pivot and its complete reviewedha-mcp7.14.1 policy inventory are documented inADR-005. Dev15 contract-level compatibility, partial quarantine, dashboard independence, and retry-cadence separation are documented inADR-006. The current Engineering development version is2.2.0-beta.6. Its F2 policy, risk, and elevated-approval semantics are recorded in ADR-012 anddocs/V2_2_0_BETA6_RELEASE_NOTES.md, anddocs/V2_2_0_BETA6_ACCEPTANCE.md. The inert update-and-recovery preflight foundation remains recorded inADR-011,docs/V2_2_0_BETA5_RELEASE_NOTES.md, anddocs/V2_2_0_BETA5_ACCEPTANCE.md. The inert knowledge-provenance foundation remains recorded inADR-010,docs/V2_2_0_BETA4_RELEASE_NOTES.md, anddocs/V2_2_0_BETA4_ACCEPTANCE.md. The inert signed compatibility-registry foundation remains recorded inADR-009, [docs/V2_2_0_BETA3_RELEASE_NOTES.md](docs/V2_2_0_BETA3_RELEA
Related servers

n8n
by n8n-io
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.

@modelcontextprotocol/server-everything
OfficialMCP server that exercises all the features of the MCP protocol

@modelcontextprotocol/server-filesystem
OfficialMCP server for filesystem access