Home / Servers

hass-mcp-admin

by jeter-1

HA MCP Engineering Server

Stable v1.1.2 under hass_mcp_admin is 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 at 2.2.0-beta.6, based on the exact v2.0.1 release, at hass_mcp_engineering_beta/ on port 8100. Its existing technical “Beta” identity is retained to avoid a slug or runtime identity migration. See V2_BETA_ARCHITECTURE.md before installing or migrating tools. Historical beta release and cache-refresh procedures are documented in docs/BETA_DEPLOYMENT.md. The beta approval workflow is documented in docs/CHANGE_GOVERNANCE.md. The facilitator decision and bounded-response contract are documented in docs/architecture/ADR-002-ENGINEERING-MCP-FACILITATOR.md and docs/TOKEN_EFFICIENCY.md. Beta 11 System Log security and Beta 12 connector-cache guidance are documented in docs/BETA_DEPLOYMENT.md. Beta 14 trace/time stabilization is documented in docs/AUTOMATION_RELIABILITY_ANALYSIS.md, and Beta 15 change-impact analysis is documented in docs/CHANGE_IMPACT_ANALYSIS.md. Beta 17 global configuration-integrity analysis and the Beta 18 reference classifier hardening are documented in docs/CONFIGURATION_INTEGRITY_ANALYSIS.md. Beta 24 pre-RC hardening, trusted-proxy setup, and bounded audit reads are documented in docs/BETA_24_RELEASE_NOTES.md, docs/RATE_LIMITING.md, and docs/AUDIT_LOG.md. Beta 25 external human approval is documented in docs/EXTERNAL_APPROVAL.md and docs/BETA_25_RELEASE_NOTES.md. Beta 26 expiry lifecycle hardening is documented in docs/BETA_26_RELEASE_NOTES.md. RC2 release and deployed acceptance procedures are in docs/RC2_RELEASE_NOTES.md and docs/RC2_ACCEPTANCE.md. The Phase 1 single-server architecture pivot and its complete reviewed ha-mcp 7.14.1 policy inventory are documented in ADR-005. Dev15 contract-level compatibility, partial quarantine, dashboard independence, and retry-cadence separation are documented in ADR-006. The current Engineering development version is 2.2.0-beta.6. Its F2 policy, risk, and elevated-approval semantics are recorded in ADR-012 and docs/V2_2_0_BETA6_RELEASE_NOTES.md, and docs/V2_2_0_BETA6_ACCEPTANCE.md. The inert update-and-recovery preflight foundation remains recorded in ADR-011, docs/V2_2_0_BETA5_RELEASE_NOTES.md, and docs/V2_2_0_BETA5_ACCEPTANCE.md. The inert knowledge-provenance foundation remains recorded in ADR-010, docs/V2_2_0_BETA4_RELEASE_NOTES.md, and docs/V2_2_0_BETA4_ACCEPTANCE.md. The inert signed compatibility-registry foundation remains recorded in ADR-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.

NOASSERTION198,904

@modelcontextprotocol/server-everything

Official

by modelcontextprotocol

MCP server that exercises all the features of the MCP protocol

89,105

@modelcontextprotocol/server-filesystem

Official

by modelcontextprotocol

MCP server for filesystem access

SEE LICENSE IN LICENSE89,105

mcp-server-fetch

Official

by modelcontextprotocol

A Model Context Protocol server providing tools to fetch and convert web content for usage by LLMs

89,105