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/sort_order keep their current values. 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
push_metrics and push_number could be confused (both write to a source), but the descriptions explicitly clarify that one replaces the whole metrics list while the other updates a single value. The two read tools (list_sources vs get_widget_data) overlap somewhat but are separated by metadata/plan usage versus live metric values.
Four of five tools follow a clean verb_noun pattern (push_metrics, push_number, list_sources, delete_source). get_widget_data deviates slightly with a three-word noun phrase, but overall the convention is predictable.
Five tools cover the core write/read/delete lifecycle for a widget data-source server, which is well-scoped rather than bloated. It is slightly lean, since there is no dedicated tool for toggling source visibility.
Create/update (push), read (list/get), and delete are all present, giving reasonable lifecycle coverage. However, list_sources exposes enabled/hidden state and sort_order but no tool lets an agent toggle visibility or reorder sources, which is a notable gap.