widgetdash-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WIDGETDASH_API_URL | No | API base URL. | https://api.widgetdash.app |
| WIDGETDASH_READ_KEY | No | Read key from https://widgetdash.app/app. Optional. Used by list_sources and get_widget_data, or the write key if not set. | |
| WIDGETDASH_WRITE_KEY | Yes | Write key from https://widgetdash.app/app. Required for push_metrics, push_number and delete_source. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| push_metricsA | Create or update a WidgetDash data source shown on the user's iPhone Home Screen / Lock Screen widgets and Live Activities. Sets the source's title, SF Symbol icon, category and its full list of metrics (label + value + type + color). The metrics list REPLACES the source's current metrics; use push_number to change a single value. Omitted display_name/icon/category keep their current values; sort_order only applies when the source is created. Requires WIDGETDASH_WRITE_KEY. |
| push_numberA | Quickest way to put a single number or value on the user's iPhone Home Screen / Lock Screen widget via WidgetDash, e.g. 'Stripe MRR = $12,400' or 'Open tickets = 7'. Sets one metric (matched by label) on a source, keeping the source's other metrics, title and icon; creates the source if it does not exist. Requires WIDGETDASH_WRITE_KEY. |
| list_sourcesA | List the data sources on the user's WidgetDash iPhone widgets (source_key, title, icon, enabled/hidden) plus the plan's source usage (the free plan allows 5 sources). Uses WIDGETDASH_READ_KEY, or the write key if no read key is set. |
| get_widget_dataA | Read what is currently shown on the user's WidgetDash iPhone widgets: every enabled source with its metrics and last update time, or one source if source_key is given. Uses WIDGETDASH_READ_KEY, or the write key if no read key is set. |
| delete_sourceA | Permanently delete a data source (and its data) from the user's WidgetDash iPhone widgets. Ends any Live Activity for it. Only do this when the user asks to remove it. Requires WIDGETDASH_WRITE_KEY. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct action, and the push_metrics vs push_number overlap is explicitly resolved in the descriptions (full metric list replacement vs single value update). The only mild ambiguity is between get_widget_data and list_sources, since get_widget_data also enumerates sources with metrics, though list_sources uniquely adds plan usage metadata.
All five tools follow a clean snake_case verb_noun pattern (delete_source, get_widget_data, list_sources, push_metrics, push_number). Verbs are semantically meaningful and consistent within the read (get/list) and write (push/delete) families.
Five tools map exactly onto the domain's core operations: list sources, read widget data, full upsert, quick single-value upsert, and delete. No redundant tools and nothing that feels like padding.
The lifecycle is largely covered: read, list, create/update (both full and incremental), and delete. Minor gaps exist — sources are listed with enabled/hidden state but there is no tool to toggle visibility, reorder, or remove an individual metric, so agents must rewrite the whole metric list to make such changes.