tday
Your coding agent records narrated demo videos of the app you are building.
Hosted MCP Server
npx add-mcp 'https://tday.com/api/mcp'Installs into Claude Code, Codex, Cursor and more
Documentation
Connect your coding agent
Add the tday MCP server to Claude Code, Cursor, Codex or any MCP client, or install tday as a plugin, and check the setup.
Your coding agent records demos through tday's MCP server (@tday-com/mcp), which runs on your
machine over stdio. The prompt in tday's setup, and one you make with Send to a developer,
starts with the install line, carrying a capture token:
TDAY_CAPTURE_TOKEN=<your capture token> npx --prefix ~ -y @tday-com/mcp@latest install
[tab] Claude Code
The install line does everything. It runs
claude mcp addat user scope, so nothing is written into your repo, with your capture token in the server's environment:claude mcp add --scope user tday -e TDAY_CAPTURE_TOKEN=<your capture token> -- npx --prefix ~ -y @tday-com/mcp@latest serveThe install writes the exact version it ran as in place of
latest. When tday releases a newer one, the server updates that version itself, so your agent runs it from its next start (see Updates). It also installs the capture skill at~/.claude/skills/tday-capture/SKILL.md. In a Claude Code session that is already open, type/reload-pluginsto load the server (no restart needed). Running it again with a new token replaces the old server entry.
[tab] Cursor
The install line prints this for you, with an exact version in place of
latest. Add it to~/.cursor/mcp.json:{ "mcpServers": { "tday": { "command": "npx", "args": ["--prefix", "<your home directory>", "-y", "@tday-com/mcp@latest", "serve"], "env": { "TDAY_CAPTURE_TOKEN": "<your capture token>" } } } }Restart Cursor.
[tab] Codex
The install line prints this for you, with an exact version in place of
latest. Add it to~/.codex/config.toml:[mcp_servers.tday] command = "npx" args = ["--prefix", "<your home directory>", "-y", "@tday-com/mcp@latest", "serve"] env = { TDAY_CAPTURE_TOKEN = "<your capture token>" }Restart Codex.
[tab] Other MCP clients
Run the server over stdio, with
TDAY_CAPTURE_TOKENin its environment:npx --prefix ~ -y @tday-com/mcp@latest serveThen give your agent its instructions. This prints them, to add to your agent's rules or skills:
npx --prefix ~ -y @tday-com/mcp@latest skill
To set up one client only, pass --client claude, --client cursor or --client codex to install.
A Record it myself prompt carries no token: it uses your own tday login (see With your own tday login).
With your own tday login
If you have a tday account, you can sign in once instead of using a prompt's token:
curl -fsSL https://tday.com/install.sh | bash
It signs you in with a code you approve in a browser, on this or any other device, and adds the
tday server to every coding agent it finds
(Claude Code, Cursor, Gemini CLI and VS Code), and prints the setup for Codex. The server then uses
your login, so its entries carry no token, and it also offers your account's own tools. Each time it
starts, it asks tday what your login may use and lists only those tools: the demo tools appear once
your account can record demos for a brand. A Record it myself prompt ends with this line, for a
machine that does not have the tday tools yet.
One click in Cursor or VS Code
With a tday account, these buttons add the tday server to Cursor or VS Code. Your editor shows the
server and asks before adding it. The first time your agent uses tday, 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, check the
code matches and choose Authorize there.
Both run npx --prefix ~/ -y @tday-com/mcp@latest serve. Use them or the install line or the plugin, not
more than one: with two, your agent lists the tday tools twice.
For your account's tools only (brands, credits and what your plan includes, but no demos), VS Code can add tday's hosted connector instead. It runs on tday.com, so there is nothing to install, and signs you in with OAuth:
Install as a plugin
tday is also a plugin for Claude Code, Cursor, Codex and Grok Build. The plugin adds the same tday
server, the skill your agent follows to record a demo, and two commands, from your agent's own plugin
manager, with nothing else to install. Its source is
github.com/tday-com/tday-plugins.
[tab] Claude Code
claude plugin install tday --marketplace tday-com/tday-pluginsOr inside a session:
/plugin marketplace add tday-com/tday-plugins, then/plugin install tday@tday. Then type/tday:demo(optionally with a feature name) to record a demo, or/tday:demos-neededto see which features have no demo yet.
[tab] Cursor
git clone https://github.com/tday-com/tday-plugins.git ~/.cursor/plugins/local/tdayThen run Developer: Reload Window in Cursor.
[tab] Codex
codex plugin marketplace add tday-com/tday-plugins codex plugin add tday@tday
[tab] Grok Build
grok plugin marketplace add tday-com/tday-plugins grok plugin install tday
The first time your agent uses tday, it calls tday_sign_in, which shows you a link and a code.
Open the link in a browser where you are signed in to tday, on this computer or any other device (it
opens by itself when this computer has a browser), check the code matches and choose Authorize; the
agent carries on. Nothing has to reach the computer, so this works the same when your agent runs in a
sandbox, on a cloud machine or over SSH (to sign a sandbox or CI job in without an agent, see
Build tday into your platform). The sign-in is saved in
~/.tday/config.json, readable only by you, and every coding agent on your computer uses it. Codex
starts a plugin's server outside your repo, so there the agent first tells tday which folder you are
working in (tday_workspace).
The plugin names one version of @tday-com/mcp, and a newer plugin brings the next one: in Claude
Code, claude plugin update tday@tday. Your agent tells you when one is out. Use the plugin or the
install line, not both: with both, your agent lists the tday tools twice.
Check the setup
TDAY_CAPTURE_TOKEN=<your capture token> npx --prefix ~ -y @tday-com/mcp@latest doctor
doctor prints ok or FAIL for each of these:
| Check | What it needs |
|---|---|
| browser | Google Chrome, or Playwright's Chromium (npx -y playwright@1.62.1 install chromium). |
| ffmpeg | ffmpeg on your PATH, for demo videos. Restart your coding agent after installing it. |
| token | TDAY_CAPTURE_TOKEN from a prompt, your own TDAY_TOKEN, or your tday login. |
| tday | A working connection to tday with that token, and the brand it belongs to. |
Tokens
The token in a prompt belongs to one brand and covers what the prompt names: the whole product, some features, or some docs sections. A prompt that records demos expires after one day, on the date the prompt names; a prompt that only captures your UI expires after 7 days. When it does, copy a new prompt from tday and run its install line again (for Cursor and Codex, replace the token in the config). Until then, Revoke stops a token at once: on the Demos page, which lists every demo prompt someone copied, or for a capture prompt on its feature's page.
Updates
Your coding agent's config names an exact version of the tday MCP, so nothing changes under you
while you work. When tday releases a newer version, the server updates that version in your
coding agents' configs as it starts (Claude Code, Cursor, Gemini CLI and VS Code). Your agent runs
the new version from its next start: in a Claude Code session that is already open, type
/reload-plugins.
The server only moves to a version that tday names and that npm shows tday's own release process
published, and only ever to a newer one. An entry you wrote with @latest, or one already on a
newer version, is left alone. Set TDAY_MCP_AUTO_UPDATE=0 in the server's environment to keep the
version you have.
To update by hand, run npx --prefix ~ -y @tday-com/mcp@latest update. It moves every coding
agent's tday server to the newest version and keeps its settings and token. Use it for Codex,
whose config.toml tday never edits for you (it tells you the line to change), and once for an MCP
older than version 0.4.8 (released November 5, 2026), which cannot update itself. Your agent offers
it when it sees a newer version.
Environment variables
| Variable | Meaning |
|---|---|
TDAY_CAPTURE_TOKEN | The token from a prompt. |
TDAY_TOKEN | Your own tday token instead of a prompt's. The demo tools then take a brandId; demo_docs puts it in every demo_start call it writes. |
TDAY_API_URL | tday's address. Default https://tday.com. |
TDAY_CAPTURE_HOME | Where review pages, takes and bundles are kept. Default ~/.tday/capture, outside your repo. |
TDAY_MCP_AUTO_UPDATE | 0 keeps the version your agent's config names: the server never updates it. |
TDAY_CAPTURE_ASSUME_YES | 1 only for unattended capture runs in CI: it counts only with CI=true, and is ignored on a developer's machine. The review's confirmation code is then the only gate, and nobody is asked. A demo upload never asks. |
Supported setups
macOS, Linux and Windows (WSL2), with Node.js 18.17 or later. Any MCP client that runs stdio servers works: the tools are the same everywhere. See the demo tools reference.
This documentation is built and hosted on Mintlify, a developer documentation platform.