Home Assistant: setup, supported tools and cost

What you can do

Read one known entity state from your Home Assistant instance.

• home_assistant_get_state — reads information

Setup and execution

Execution

TaskVegas calls your existing application

Requirements

An externally reachable, supported HTTPS instance and its authorized credential are required. TaskVegas does not provision it.

Who pays

You pay for your application hosting and any AI-host plan; gateway limits also apply.

Create or recover a workspace, save the required connection, test it, enable the module, then approve the exact tools in your OAuth-capable MCP client. Searching the catalog grants no execution permission.

Permissions and boundaries

• Read one known entity; no service calls

Use only an instance and account you are authorized to access. Review the deployed project license and instance policy.

Only the named typed operations are available. Responses may be truncated; check returned identifiers, source links and error details before acting. Existing quotas and the operator pause switch apply. There is no owner-paid fallback.

Source and review evidence

Adapter version

taskvegas-wrapper-1

Reviewed

2026-10-06 · TaskVegas adapter contract review (docs/integrations-instances.md)

Contract evidence

fixture-tested

AI-host evidence

pending; account evidence: pending

Reviewed revision

5ffb355af5d10c5e7066a74deeb4e5ca98710061

Implementation

server/gateway/instances.js

Fixtures check the typed wrapper contract. Genuine authenticated hosted MCP tools/list and permitted call evidence is pending.

Upstream project license and deployed version require separate review; this wrapper calls an API and does not redistribute upstream server code.

Next steps

• Connect an OAuth-capable MCP client
• Understand costs and quotas
• Read compatibility evidence
• Open your workspace