Wdttg Where Did The Time Go?

MCP办公协作

提供方 plattnum

办公协作 未标注 API Key 社区 / 第三方 ClaudeCursorVS CodeCodex

Stop filling out time entry forms. wdttg is a local MCP server and TUI that lets AI agents track your time in plain Markdown. Just say what you worked on — the server handles the rest.

一句话选型结论

按资料字段整理

Wdttg Where Did The Time Go? 属于办公协作类 MCP 服务器,传输方式未标注,API Key,可直接接入 Claude、Cursor、VS Code 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类办公协作 传输方式未标注 鉴权API Key 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

办公协作
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

time tracking freelancer rust tui terminal markdown local first

支持客户端

适用场景

time trackingfreelancerrust

安装与配置

未标注 API Key
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
日程与消息

查日程、发消息、约会议。

表单与审批

填表单、走审批流。

团队协作

同步任务、汇总进展。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude、Cursor、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在办公协作场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Wdttg Where Did The Time Go?当前 未标注 未标注 未标注 无 未标注
CowAgent 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Karakeep MCP 未标注 未标注 未标注 无 2026-05-17
agentscope 未标注 stdio · 本地进程 本地部署 有 2026-04-11
note-gen 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Everywhere 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

办公协作
字段来自项目仓库与公开索引,中文说明由本站标注
提供方plattnum上游标注的维护方 plattnum
分类办公协作本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

10.7 KB
来自项目仓库与上游目录的原文,未做删改

wdttg - Where Did The Time Go?

A terminal time tracker for freelancers, built in Rust. No cloud, no subscriptions, no app store approval queues. Just markdown files, a TUI, and an MCP server because life's too short for time entry forms.

More screenshots

Why this exists

I built the where-did-the-time-go Obsidian plugin to scratch this itch the first time around. It worked great, but I got tired of being tied to a specific application platform. Plugin approval on Obsidian takes forever, and at the end of the day the data format was already just markdown tables.

Markdown is everywhere now — every IDE reads it, every AI agent works well with it. So instead of fighting an approval process, I pulled the concept out into its own thing: a lightweight TUI for visualization and an MCP server so AI agents can do the heavy lifting.

The core idea is dead simple: I did X between A and B. Categorize it so I can report on it and bill from it.

This is not a task manager. My tasks live in tickets, ad-hoc journal entries, kanban boards — wherever makes sense at the time. This tool only cares about what you did and when. A meeting with a client. A two-hour dev session. A quick call that ran long. Log it, tag it, move on.

How it works with AI

The MCP server is the real unlock here. Instead of clicking through forms, I just tell Claude what I did:

> "I had a sprint planning meeting with Acme from 9 to 10:30 this morning"

Claude calls the MCP tools, validates the entry, checks for overlaps, and logs it. If I'm too vague, it asks for the missing pieces.

Why MCP instead of letting the AI edit markdown directly?

Without the MCP server, the AI would have to read the raw markdown into its context, parse the table, mentally compare timestamps to check for overlaps, format a new row correctly, and write the whole file back. Any of those steps can go wrong — the LLM might miscalculate a time comparison, botch the table formatting, or hallucinate that a time slot is free when it isn't. And every entry eats context tokens just to read and rewrite the file.

With the MCP server, create_entry handles all of that programmatically — parsing, validation, overlap detection, chronological sorting, atomic file writes. The AI just says "create this entry" and gets back a definitive yes or a structured error. No guesswork, no wasted tokens, no risk of corrupting the file.

The TUI and MCP server share the same data files, so entries created by AI show up in the timeline within ~200ms.

Features

  • Infinite vertical timeline — endless scrolling into the past or future with keyboard and mouse
  • MCP server for AI agent integration (Claude Code, Cursor, etc.)
  • GFM markdown storage — one file per month, human-readable and editable
  • Client/project/activity hierarchy with billable rates
  • Overlap detection and time snapping
  • Report generation with billable amounts
  • File watching for real-time sync between TUI and MCP

Install

macOS and Linux only. Windows is not yet supported.

From GitHub Releases (recommended)```bash

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/plattnum/wdttg-tui/releases/latest/download/wdttg-tui-installer.sh | sh


### From source

Requires Rust 1.85+ (2024 edition).```bash
git clone https://github.com/plattnum/wdttg-tui.git
cd wdttg-tui
cargo install --path crates/wdttg-tui

Getting Started

1. Initialize```bash

wdttg init


Interactive setup wizard — asks for time format (12h/24h), week start day, data directory, and your first client. Press Enter to accept defaults at each step.```
Welcome to wdttg! Let's set things up.

Time format [24h/12h] (24h):
Week start [monday/sunday] (monday):
Data directory (/Users/you/.local/share/wdttg/data):

Set up your first client:
  Client name (Personal): Acme Corp
  Hourly rate (0): 150
  Currency (USD):

✓ Config saved to ~/.config/wdttg/config.toml
✓ Client data saved to ~/.local/share/wdttg/data/clients.toml

2. Launch the TUI```bash

wdttg


### 3. Set up AI integration (optional)

The MCP server is launched automatically by your AI client — you don't run `wdttg serve` manually. Just add the config and your AI can create/query time entries for you.

See MCP Server Setup below.

### Export reports```bash
wdttg export --format csv --preset this-month          # CSV to stdout
wdttg export --format json --preset last-week           # JSON to stdout
wdttg export --format csv --start 2026-03-01 --end 2026-03-31 --client acme > report.csv

Or press x on the Reports tab to export the current view as CSV to your data directory.

Reinitialize```bash

wdttg init --force # resets preferences and client data (keeps time entries)


### Upgrading

After installing a new version, **restart any AI clients** (Claude Desktop, Claude Code, Cursor, etc.) that run the MCP server. They cache the old binary — the MCP server won't pick up changes until the AI client restarts and re-launches `wdttg serve`.```bash
cargo install --path crates/wdttg-tui   # or download new release
# Then restart Claude Desktop / reload Claude Code

MCP Server Setup

Claude Code

Add to your project's .mcp.json (or ~/.claude/mcp.json for global access):```json
{
"mcpServers": {
"wdttg": {
"command": "wdttg",
"args": ["serve"]
}
}
}


If running from source instead of an installed binary:```json
{
  "mcpServers": {
    "wdttg": {
      "command": "cargo",
      "args": ["run", "-p", "wdttg-tui", "--", "serve"],
      "cwd": "/path/to/wdttg-tui"
    }
  }
}

Available MCP Tools

Tool Description
Time entries
list_entries List time entries with date range, presets, and filters
get_entry Get a single entry by ID or start/end timestamps
create_entry Create a new time entry with validation and overlap checking
update_entry Update an entry (supports partial updates)
delete_entry Delete an entry by ID or timestamps
check_overlaps Check if a proposed time range conflicts with existing entries
available_slots Find free time gaps within a datetime range
Reports
generate_report Aggregated report by client/project/activity with billable amounts
get_status Today/week totals, entry counts, config summary
Clients & projects
list_clients List clients with their projects and activities
create_client Add a new client
update_client Update client fields
archive_client Archive/unarchive a client (cascades to projects + activities)
create_project Add a project under a client
update_project Update project fields
archive_project Archive/unarchive a project
create_activity Add an activity under a client
update_activity Update activity fields
archive_activity Archive/unarchive an activity

Testing with MCP Inspector

Use the MCP Inspector to interactively test and debug the server:```bash

From source

npx -y @modelcontextprotocol/inspector cargo run -p wdttg-tui -- serve

Or using the installed binary

npx -y @modelcontextprotocol/inspector wdttg serve


This opens a web UI (usually `http://localhost:6274`) where you can browse available tools, invoke them with custom inputs, and inspect results.

## Configuration

Configuration is split into two files:

### Preferences — `~/.config/wdttg/config.toml`

Machine-local settings. Created by `wdttg init`.```toml
[preferences]
time_format = "24h"
week_start = "monday"
day_start_hour = 6
day_end_hour = 22
snap_minutes = 15
tag_style = "flat"            # "flat" | "powerline" | "triangle"
# data_dir = "/custom/path"   # optional, overrides default data location

tag_style controls how tag chips are separated on timeline entries. flat is the default and works on any terminal. powerline uses Powerline chevron glyphs (U+E0B0) that blend chip colors — requires a Powerline / Nerd Font in your terminal. triangle uses U+25B6 and works on any Unicode terminal but doesn't blend as smoothly. Press T in the TUI to cycle styles at runtime; the chosen style is persisted to this file.

Client data — /clients.toml

Clients, projects, activities, and billing info. Lives alongside time entries so the whole data directory is portable and syncable (git, Dropbox, etc.).```toml
[bill_from]
name = "Jane Freelancer"
email = "jane@example.com"

[[clients]]
id = "acme"
name = "Acme Corp"
color = "#FF6B6B"
rate = 150.0
currency = "USD"

[[clients.projects]]
id = "webapp"
name = "Web App"
color = "#4ECDC4"

[[clients.activities]]
id = "dev"
name = "Development"
color = "#45B7D1"


## Data Format

Time entries are stored as GFM tables in `~/.local/share/wdttg/data/YYYY-MM.md`:```markdown
# 2026-03

| Start | End | Description | Client | Project | Activity | Notes |
|-------|-----|-------------|--------|---------|----------|-------|
| 2026-03-15 09:00 | 2026-03-15 10:30 | Sprint planning | acme | webapp | meeting | |
| 2026-03-15 11:00 | 2026-03-15 13:00 | API auth refactor | acme | webapp | dev | ticket ACME-412 |
| 2026-03-15 14:00 | 2026-03-15 14:30 | Quick sync with design team | acme | webapp | meeting | |
| 2026-03-15 14:30 | 2026-03-15 17:00 | Frontend dashboard work | acme | webapp | dev | |

Development```bash

cargo build # Build everything
cargo test # Run all tests
cargo test -p wdttg-core # Core library tests
cargo test -p wdttg-mcp # MCP integration tests
cargo run -p wdttg-tui # Run the TUI
cargo clippy --all-targets # Lint
cargo fmt --check # Check formatting
```

Workspace

Crate Purpose
wdttg-core Library: parsing, validation, storage, reporting
wdttg-tui Binary: terminal UI (ratatui + crossterm)
wdttg-mcp Library: MCP server tool implementations

Companion: bulletd

wdttg pairs well with bulletd — a terminal bullet journal built on the same principles: local-first, plain Markdown, MCP-enabled. Together they cover the daily workflow: bulletd captures what you need to do, wdttg captures how long it took. Both run as MCP servers, so your AI agent can manage your task log and time entries in the same conversation.

Organizational tracking systems — Jira, Linear, Asana — are built for planned work, not the ad-hoc reality of your day. You're not going to file a ticket for "check rollout status on Google Play Console" or "help debug staging." And MCP integrations to those systems are either nonexistent, not allowed, or painfully slow. These tools let you capture what actually happens locally, then reconcile back to the official system when it matters.

Support

If this is useful to you, consider buying me a coffee.

License

MIT - Do whatever you want with it.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Wdttg Where Did The Time Go? 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Wdttg Where Did The Time Go? 怎么在 Claude、Cursor、VS Code 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Wdttg Where Did The Time Go? 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Wdttg Where Did The Time Go? 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

Wdttg Where Did The Time Go? 支持哪些客户端?

资料标注支持 Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Wdttg Where Did The Time Go? 能提供哪些能力?

资料显示能力标签包括 time tracking、freelancer、rust、tui、terminal、markdown。具体工具清单以官方文档为准。

Wdttg Where Did The Time Go? 需要什么运行环境?

运行时为 Cross-platform。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。