Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoHTTP port. Default 3000.3000
DASHY_URLYesRequired. Origin only, http or https, with no userinfo, query, hash, or path. Do not append /api.
DASHY_TOKENNoRequired unless DASHY_TOKEN_FILE is set. Sent as Authorization: Bearer. Minimum 8 characters. Redacted in logs, errors, previews, and results.
DASHY_CONTACTNoContact token in the User-Agent. Must not contain the API token.
MCP_TRANSPORTNoTransport mode. Valid values are stdio or http. --http overrides.
DASHY_PER_MINUTENoLocal request budget. Default 30. Cache hits do not spend it.30
DASHY_TIMEOUT_MSNoUpstream timeout in milliseconds. Default 20000.20000
DASHY_TOKEN_FILENoOptional. Path to a chmod 600 file whose trimmed contents are the token. Used when DASHY_TOKEN is omitted.
DASHY_ALLOW_WRITESNoMust be the literal true before a confirmed write is sent.
DASHY_CACHE_TTL_SECNoRead cache TTL in seconds. Default 60. Writes clear the cache.60

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
dashy_systemA

Dashy process health, host resource snapshot, and the config JSON Schema. Reads only. Actions: health (GET /healthz), info (GET /system-info), schema (GET /schema.json). Dashy has no rebuild endpoint in 4.9.19.

dashy_configA

List config files, get one file as JSON, or replace a whole file. Replace runs only when confirm is true and DASHY_ALLOW_WRITES=true. Otherwise it is a dry-run and no HTTP write is sent. List accepts offset and limit applied after the fetch. Actions: list, get, replace.

dashy_keysA

Get or replace one top-level key: pageInfo, appConfig, sections, or pages. Replace overwrites that key. It does not merge. Writes run only when confirm is true and DASHY_ALLOW_WRITES=true. Actions: get, replace. Listing sections is get with key sections.

dashy_sectionsA

Add, get, shallow-merge, or delete a dashboard section. sid is a zero-based index or an exact section name. Add needs document.name. Writes run only when confirm is true and DASHY_ALLOW_WRITES=true. Actions: add, get, update, delete.

dashy_itemsA

List, add, get, shallow-merge, or delete a tile in a section. sid and iid are an index or an exact name or title. Add needs document.title. List accepts offset and limit applied after the fetch. Writes run only when confirm is true and DASHY_ALLOW_WRITES=true. Actions: list, add, get, update, delete.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 5 tools

Disambiguation4/5

The tools are partitioned by resource level (system, whole config file, top-level key, section, item), which is mostly clear. There is some inevitable overlap — dashy_config replace vs dashy_keys replace vs dashy_sections update can all mutate the same document, and dashy_keys get(key=sections) duplicates dashy_sections get — but the descriptions explicitly delineate scope.

Naming Consistency5/5

Every tool follows the same dashy_<resource> snake_case noun pattern, and the resource hierarchy (system → config → keys → sections → items) is coherent. Actions are consistently multiplexed via an action parameter rather than encoded in names, so the convention is applied uniformly.

Tool Count5/5

Five tools is well-scoped for a dashboard config server, and each one covers a distinct layer of the document rather than being a thin wrapper. The action-multiplexing keeps the surface small (~16 operations) while staying navigable.

Completeness4/5

Full lifecycle coverage exists for the hierarchical parts of the config (sections and items have add/update/delete), plus file-level and key-level read/write. Minor gaps: no way to create or delete a config file, and dashy_keys cannot add or remove top-level keys — though those keys are a fixed set, so agents can work around it.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues