Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Push any number to your iPhone Home Screen / Lock Screen widgets and Live Activities.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
WIDGETDASH_WRITE_KEY, WIDGETDASH_READ_KEY, WIDGETDASH_API_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"widgetdash": {
"command": "npx",
"args": [
"-y",
"widgetdash-mcp"
],
"env": {
"WIDGETDASH_WRITE_KEY": "your-value",
"WIDGETDASH_READ_KEY": "your-value",
"WIDGETDASH_API_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add widgetdash --env WIDGETDASH_WRITE_KEY=your-value --env WIDGETDASH_READ_KEY=your-value --env WIDGETDASH_API_URL=your-value -- npx -y widgetdash-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"widgetdash": {
"command": "npx",
"args": [
"-y",
"widgetdash-mcp"
],
"env": {
"WIDGETDASH_WRITE_KEY": "your-value",
"WIDGETDASH_READ_KEY": "your-value",
"WIDGETDASH_API_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"widgetdash": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"widgetdash-mcp"
],
"env": {
"WIDGETDASH_WRITE_KEY": "your-value",
"WIDGETDASH_READ_KEY": "your-value",
"WIDGETDASH_API_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
WIDGETDASH_API_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account purian, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: WIDGETDASH_WRITE_KEY, WIDGETDASH_READ_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 10 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Dialyne
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Real phone calls in France for AI agents: dial +33 numbers, menus, hold, AI disclosure.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Let your AI agent put any number on your iPhone.
WidgetDash shows numbers from any service on iPhone Home Screen widgets, Lock Screen widgets and Live Activities. This Model Context Protocol server lets Claude Desktop, Claude Code, Cursor and other MCP clients push data to your widgets and read it back. You just ask:
"Put my Stripe MRR on my iPhone widget."
npx comes with it).claude mcp add widgetdash -e WIDGETDASH_WRITE_KEY=your-write-key -- npx -y widgetdash-mcp
Edit claude_desktop_config.json (Settings → Developer → Edit Config), then restart Claude Desktop:
{
"mcpServers": { "widgetdash": { "command": "npx", "args": ["-y", "widgetdash-mcp"], "env": { "WIDGETDASH_WRITE_KEY": "your-write-key", "WIDGETDASH_READ_KEY": "your-read-key" } } } }
Add this to ~/.cursor/mcp.json for all projects, or .cursor/mcp.json for one project:
{
"mcpServers": { "widgetdash": { "command": "npx", "args": ["-y", "widgetdash-mcp"], "env": { "WIDGETDASH_WRITE_KEY": "your-write-key" } } } }
Other MCP clients that can launch a stdio server work the same way. The command is npx -y widgetdash-mcp, and the keys go in the environment variables below.
| Variable | Required | Description |
|---|---|---|
WIDGETDASH_WRITE_KEY | For writes | Write key from https://widgetdash.app/app. push_metrics, push_number and delete_source need it. |
WIDGETDASH_READ_KEY | No | Read key. list_sources and get_widget_data use it, or the write key if it isn't set. |
WIDGETDASH_API_URL | No | API base URL. Default: https://api.widgetdash.app. |
push_number.)| Tool | What it does |
|---|---|
push_number | Sets one value on a source, e.g. MRR = $12,400. Other metrics on the source stay as they are. The metric is matched by label. If the source doesn't exist yet, it is created. |
push_metrics | Creates or updates a source: title (display_name), SF Symbol icon, category, sort_order (new sources only; reorder in the app) and the full metrics list. The list replaces the source's current metrics. |
list_sources | Lists your sources (key, title, icon, hidden or shown) and how many your plan allows. The free plan allows 5. |
get_widget_data | Shows what's on the widget now: every enabled source with its metrics and last update time, or a single source. |
delete_source | Permanently deletes a source and ends any Live Activity for it. |
Each metric has a label, a value, an optional type, an optional color and an optional wide:
number: a big bold figure.text: a plain string.status: a colored badge.progress: a bar. The value must be 0 to 100, and a trailing % is removed for you.percentage: compact percent text.timestamp: a moment, shown as a live relative time such as "8 hours ago". Send an ISO 8601 time (2026-10-23T05:00:00Z) or Unix epoch seconds. Reads show the relative time plus the exact time.If you leave type out, values that look like numbers (42, $12,400, 3.5%) become number and everything else becomes text. With push_number, an existing metric keeps its current type, color and wide, and the source's other metrics are re-sent as they were stored: timestamps keep their exact time, and colors chosen by the source's color rules stay under the rules' control.
green, red, yellow, blue, gray, orange, purple or cyan.true gives the metric a full-width row of its own on Large widgets (iOS app 1.8 or later), for long text such as a title. Other text that shares a row shows up to two lines. Put wide metrics last to keep the others in one row.dollarsign.circle.fill, chart.bar.fill, server.rack or heart.fill.Fields you leave out (display_name, icon, category, raw_data) keep their current values. sort_order only places a new source: once it exists, its order is the one set in the app, so an agent can't undo it.
Authorization header of requests to the WidgetDash API. The server never logs them and removes them from any error text it returns.WIDGETDASH_API_URL, which is https://api.widgetdash.app by default.npm install
npm run build # compiles src/ to dist/ npm test # builds, then runs the end-to-end tests
npm test runs every tool through a real MCP client over stdio, against an in-memory mock of the WidgetDash API (test/mock-api.mjs). It needs no network and no keys, and it never contacts production.
To try it interactively, run npx @modelcontextprotocol/inspector node dist/index.js.
server.json is the entry for the official MCP Registry under the name io.github.purian/widgetdash-mcp, following schema 2025-12-11. The mcpName field in package.json must match that name for npm ownership verification. Status: draft. It hasn't been published yet, and the registry is still in preview, so check server.json against the current schema before running mcp-publisher publish.
MIT © WidgetDash