jasonwall1387/command-center-template — explained in plain English
Analysis updated 2026-05-18
Build a personal daily dashboard that shows your calendar, tasks, inbox, and metrics in one place
Preview and debug dashboard panels in a mock mode before connecting real accounts
Track whether your scheduled automations are running on time using a heartbeat health panel
| jasonwall1387/command-center-template | 100/rutgers-pbl-dining-2015 | a15n/a15n_old | |
|---|---|---|---|
| Stars | 0 | — | — |
| Language | HTML | HTML | HTML |
| Last pushed | — | 2015-12-01 | 2016-06-18 |
| Maintenance | — | Dormant | Dormant |
| Setup difficulty | moderate | easy | easy |
| Complexity | 3/5 | 1/5 | 1/5 |
| Audience | vibe coder | general | general |
Figures from each repo's GitHub metadata at analysis time.
Requires a paid claude.ai plan for MCP connectors, plus matching each connector's exact display name from claude mcp list.
Command Center is a template for building your own personal, one page morning dashboard that runs as a Claude artifact and pulls live data from the connectors you have already set up in claude.ai, such as Google Calendar, Todoist, Gmail, Cloudflare, Supabase, and Apollo.io. Because the page uses your own connected accounts directly in your browser, it stays private: an artifact that uses these live connectors cannot be shared publicly, has no exported copy carrying your credentials, and involves no server sitting in between. You do not need any real connectors to try it out. A built in mock mode renders the entire dashboard from a sample data file, and you can even force specific panels into an error state on purpose, so you can see exactly what a reconnect prompt or a stale data warning looks like before it ever happens for real. Setting it up means editing a single HTML file: filling in a small configuration block with your timezone and any optional database identifiers, listing your scheduled automations and when each should run so the dashboard can show a health status for them, and deleting the panels for any connector you do not use. The README walks through several specific problems the author ran into while building this against real connectors, such as connector names needing to match exactly what a command line tool reports, one connector wrapping its response data inside another layer than expected, and a task list connector silently limiting results unless you ask for more. To publish your finished dashboard you use the Claude Code command line tool rather than a browser, declaring which connectors the page is allowed to call and confirming their exact names first. An optional heartbeat system lets your own automations report their status into a small database so the dashboard can show which ones ran successfully and which are late or failing. This requires a claude.ai paid plan, since artifacts with live connectors are a paid feature, along with a recent version of the Claude Code CLI.
A template for a private, live morning dashboard built as a Claude artifact that pulls from your own claude.ai connectors like calendar, tasks, and email.
Mainly HTML. The stack also includes HTML, JavaScript, Claude MCP.
Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.
Mainly vibe coder.
This repo across BitVibe Labs
Verify against the repo before relying on details.