tday

Name: tday
Author: tday.com

Local

tday.comMedia & Design0Updated 1d ago

Repository Visit website

About tday

tday lets coding agents record narrated demos of app features in a separate local app instance and upload footage for editing and sharing. It supports web, Electron desktop, terminal, and simulator-based apps.

Key features

01Records app demos through a coding agent
02Uses a separate app instance with throwaway data
03Checks footage for possible on-screen secrets
04Uploads footage and demo metadata to tday

Use cases

01Recording a newly built feature
02Reviewing which features still need demos

MCP support

The `tday` MCP server runs locally over stdio and lets a coding agent use tday's demo-recording workflow.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config

{
  "mcpServers": {
    "com-tday": {
      "command": "npx",
      "args": [
        "-y",
        "@tday-com/mcp"
      ]
    }
  }
}

Run commandnpx -y @tday-com/mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages

npm@tday-com/mcp0.4.13stdio

Tools

Saved tool list · updated 2d ago

Parameter	Type	Required	Description
appUrl	string	No	The running app's address, e.g. http://localhost:3000 (not needed with cdpUrl)
cdpUrl	string	No	A running desktop app's debugging address on this machine, e.g. http://127.0.0.1:9222, to capture in its own window
device	enum	No	desktop \| mobile
headed	boolean	No	Show the browser window (e.g. to let the developer sign in)
window	string	No	With cdpUrl: part of the address of the app window to capture, when it has several
repoDir	string	No	The repo root (default: the current directory)
featureIds	array	No	tday feature ids from the capture prompt or demo_features (empty = all features a capture prompt's token allows)
colorScheme	enum	No	light \| dark
storageState	string	No	A Playwright storage-state JSON file with a signed-in session

Details

From the project README

tday for coding agents

Record narrated demo videos of your app with the coding agent you already use. Ask your agent to "record a tday demo of the newest feature": it starts a separate demo copy of your app on your computer, walks through the feature one narrated line at a time, checks the take for anything private on screen, and uploads it. tday adds the voice, the cursor, the camera moves and the style, and the demo arrives in tday ready to edit and share.

It works with web apps, desktop apps built on Electron, terminal tools, iPhone apps in the iOS Simulator, Android apps on the emulator and Mac apps. You need a tday account (tday.com).

Install

Claude Code

claude plugin install tday --marketplace tday-com/tday-plugins

Or inside a session: /plugin marketplace add tday-com/tday-plugins, then /plugin install tday@tday.

Cursor

git clone https://github.com/tday-com/tday-plugins.git ~/.cursor/plugins/local/tday

Then run Developer: Reload Window in Cursor.

Only the MCP server, in one click

These add the tday MCP server alone (no skill or commands) to Cursor or VS Code, pinned to this version. Use them or the plugin, not both.

Codex

codex plugin marketplace add tday-com/tday-plugins
codex plugin add tday@tday

Grok Build

grok plugin marketplace add tday-com/tday-plugins
grok plugin install tday

First use

Ask your agent to record a demo. The first time, it calls tday_sign_in, which shows you a link and a code. Open the link on any device where you are signed in to tday (it opens by itself when this computer has a browser), check the code matches and choose Authorize; the agent carries on. It works the same from a sandbox, a cloud machine or over SSH. The sign-in is saved in ~/.tday/config.json on your computer, readable only by you, and every coding agent on the computer uses it. It lasts 90 days.

In Claude Code you can also type /tday:demo (optionally with a feature name) or /tday:demos-needed to see which features have no demo yet.

What it runs and what it sends

The tday MCP server. The plugin adds one MCP server, tday, which your agent starts with npx --prefix ~/ -y @tday-com/[email protected] serve: the @tday-com/mcp package from npm, pinned to that version. It runs on your computer over stdio, in your repo; npx resolves it from your home directory so your repo's own package.json is never read. The package is published by tday's release workflow only, under its own license.
What leaves your computer. The demo footage and the screens you choose to upload, and metadata about them (the feature, the steps, the narration). Never your source code, .env values or secrets: a take with a possible secret on screen is held back until it is fixed. See what leaves your machine and demo safety.
Who it talks to. tday (tday.com), with your sign-in. The npm registry, once a day, to see whether a newer version is out. GitHub's or GitLab's public API, without a token, to check whether your repo is public before a note is saved in it (sending only the repo's name). For a terminal demo, a symbols font from cdn.jsdelivr.net.
On your computer. A separate demo instance of your app with throwaway data (your own server and data are never touched), a browser or simulator to record it in, and scratch files under ~/.tday/capture, removed at the end. Notes on how your app was started go in your repo's .tday folder, and nothing is committed for you.

The plugin also carries a skill with the steps the agent follows, and the two commands above.

License

The files in this repository are licensed under the MIT license (see LICENSE). The @tday-com/mcp package they start is distributed on npm under its own license.

The tday name, the tday logo and Cali (the icon in assets/) are tday's trademarks. The license does not grant permission to use them.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

Read the getting-started guide

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.