Reported issues for Home Assistant MCP Server

Pod holds 7 of 7 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to Home Assistant MCP Server.

Most discussed

Add GitHub Actions CI/CD workflows

Summary

Add GitHub Actions workflows for continuous integration and automated npm publishing.

CI Workflow (.github/workflows/ci.yml)

• Trigger on push to main and pull requests
• Node.js 18.x and 20.x matrix
• Steps: install → lint → type-check (tsc --noEmit) → test (vitest run)
• Cache node_modules for speed

Publish Workflow (.github/workflows/publish.yml)

• Trigger on GitHub release creation (tag v*)
• Build → test → npm publish
• Requires

Read the thread · 2026-03-22 · closed · 1 comment

Create VS Code extension wrapper for Marketplace publishing

Summary

Create a minimal VS Code extension that registers this MCP server via contributes.mcpServers. This makes the server discoverable in the VS Code Marketplace with the @mcp search keyword, giving users one-click installation.

How It Works

The extension has no code — just a package.json manifest that tells VS Code how to launch the MCP server (via npx).

Tasks

• Create vscode-extension/ directory in repo
• Create vscode-extension/package.json with:
  • `publ

Read the thread · 2026-03-22 · closed · 1 comment

Add smoke test for MCP tool registration

Summary

Create a smoke test that verifies all 65 MCP tools register successfully on the server without errors, using mocked HA clients.

Tasks

• Mock RestClient, WsClient, and SftpClient (no real HA connection)
• Create MCP server instance
• Call all 5 register*Tools() functions with mocked clients
• Verify server has 65 registered tools
• Verify each tool has a name, description, and input schema
• Verify no duplicate tool names

Why

This catches registr

Read the thread · 2026-03-22 · closed · 1 comment

Set up vitest and unit tests for config and client layers

Summary

The project has zero tests. Unit tests are needed for the core modules before publishing.

Test Areas

config.ts — Configuration validation

• Valid config with all required env vars loads successfully
• Missing HA_URL throws descriptive error
• Missing HA_TOKEN throws descriptive error
• Optional SSH config is truly optional (no error when absent)
• SSH config validates when partially provided

sftp-client.ts — Path safety (security-critical)

• [

Read the thread · 2026-03-22 · closed · 1 comment

Add ESLint and Prettier configuration

Summary

The project has no linting or formatting configuration. Adding these ensures consistent code quality and catches issues before they reach production.

Tasks

• Add ESLint flat config (eslint.config.js) with TypeScript support
• Add Prettier config (.prettierrc)
• Add npm scripts: lint, format, check (lint + type-check combined)
• Install devDependencies: eslint, @eslint/js, typescript-eslint, prettier, eslint-config-prettier
• Run lint across

Read the thread · 2026-03-22 · closed · 1 comment

Complete package.json metadata for npm publishing

Summary

The package.json is missing several fields required/recommended for npm publishing.

Missing Fields

• author — package author name/email
• repository — "github:jarahkon/home-assistant-mcp-server"
• homepage — GitHub repo URL or docs URL
• bugs — "https://github.com/jarahkon/home-assistant-mcp-server/issues"
• engines — { "node": ">=18.0.0" } (project targets ES2022 and uses Node16 module resolution)
• files — `["dist", "README.md", "LICEN

Read the thread · 2026-03-22 · closed · 1 comment

Add LICENSE file

Summary

The package.json declares "license": "MIT" and the README mentions MIT, but there is no actual LICENSE file in the repository root. This is required for npm publishing and open source compliance.

Tasks

• Create LICENSE file in repo root with the full MIT license text
• Include correct year and copyright holder name

Context

This is a prerequisite for publishing to npm and the VS Code Marketplace.

Read the thread · 2026-03-22 · closed · 1 comment

Most recent

The remaining reports are on the project's issue tracker.