Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PINNED_TOOLSNoComma-separated tool names to keep always visible. The web settings UI is the primary way to manage this.
HOMEASSISTANT_URLYesThe URL of your Home Assistant instance, used when running the server outside Home Assistant (Docker/PyPI HTTP server or local stdio).
ENABLE_TOOL_SEARCHNoReplace the full tool catalog with search-based discovery (tools deferred behind on-demand search). Recommended for smaller or local LLMs and clients without native deferred tool support.false
HOMEASSISTANT_TOKENYesA Home Assistant long-lived access token; an administrator's token is recommended (non-admin tokens work with limitations). Used when running the server outside Home Assistant (Docker/PyPI HTTP server or local stdio).
ENABLE_BETA_FEATURESNoMaster flag to enable beta features; it must be on before the filesystem/YAML sub-flags take effect.false
TOOL_SEARCH_MAX_RESULTSNoMax hidden tools returned per ha_search_tools call (range 2-10).5
HAMCP_ENABLE_FILESYSTEM_TOOLSNoFeature flag enabling the opt-in filesystem tools (ha_list_files, ha_read_file, ha_write_file, ha_delete_file), which also require the HA-MCP File & YAML Tools entry and beta feature flags.false

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription

No tools

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources