Bulletd Digital Bullet Journal MCP Server

MCP日程管理

提供方 plattnum

日程管理 未标注 OAuth 授权 社区 / 第三方 ClaudeCursorVS CodeCodex

Organizational tracking systems are built for planned work— Jira tickets, sprint boards, quarterly OKRs. They don't capture the actual shape of your day: the ad-hoc debugging session, the quick rollout check, the thing someone asked you in Slack that ate an hour. bulletd is a digital bullet journal that lives where you work. It runs as a local MCP server with 16 typed tools, so your AI agent manag

一句话选型结论

按资料字段整理

Bulletd Digital Bullet Journal MCP Server 属于日程管理类 MCP 服务器,传输方式未标注,OAuth 授权,可直接接入 Claude、Cursor、VS Code 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

支持客户端

适用场景

productivityrusttui

安装与配置

未标注 OAuth 授权
上游未给出传输方式
  1. 1
    准备运行环境

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

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

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

按空闲时间自动排日程。

提醒与待办

设提醒、管待办清单。

时间协调

在多人之间找共同空档。

选择建议

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

值得选的地方

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

先想清楚的地方

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

更适合

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

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Bulletd Digital Bullet Journal MCP Server当前 未标注 未标注 未标注 无 2026-11-20
Todoist MCP Server 79e800d2 35 stdio · 本地进程 支持远程部署 有 2026-05-17
Outlook Calendar MCP 7 stdio · 本地进程 本地部署 有 2026-05-18
MCP Server Apple Events 5 stdio · 本地进程 本地部署 有 2026-05-17
y-cli 未标注 stdio · 本地进程 本地部署 无 2026-10-05
Google Calendar 未标注 HTTP · 远程 支持远程部署 有 2026-05-17

服务器档案

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

详细介绍

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

bulletd

A highly opinionated digital bullet journal for the terminal.

bulletd was inspired by and attempts to implement a subset of the Bullet Journal system — rapid logging, migration, and review — without the overhead of a full task management system. Everything is a bullet. There's no distinction between tasks, events, and notes — just bullets with a status. Each bullet can carry multi-line context notes — added at creation or edited later — so you can capture the "why" alongside the "what" if needed.

All data is stored as plain Markdown — one file per day, one GFM table per file. No database, no proprietary format. The files are readable in any text editor, any Markdown viewer, or on GitHub. The TUI and MCP server are just faster ways to work with them.

You open it in the morning, jot down what's on your plate, and throughout the day you capture what happens. At the end of the day (or whenever), you glance at what's still open and decide: done, move to tomorrow, drop it, or shelve it.

It's not Jira. It's not a project management tool. There's no priorities, no assignments, no due dates, no labels.

Why does this exist?

I've kept a paper bullet journal for years to deal with my day to day work tasks. I always wanted to just talk to it — say "add a bullet", "what's still open", "migrate that to tomorrow" — without the friction of pen and paper. But every digital tool I tried missed the point. TODO apps come with too much of the kitchen sink: priorities, labels, due dates, recurring tasks, and endless grooming. You spend more time managing the system than using it. MCP servers that wrap SaaS tools (Linear, Todoist, etc.) are slow as molasses — every call is a round trip to someone else's API.

The idea clicked when I saw the Task Tools in Claude's Cowork. An AI managing your daily log alongside you — that's what I wanted. I tried building it as a Claude Code plugin backed by Markdown files, but it was never fully deterministic. The AI has to read files into context, parse the format, and try to enforce schema rules with no guarantees. It mostly works, but it's fragile.

So bulletd fills that gap for me: a local MCP server that owns the data format. Instead of reading and rewriting Markdown files, the AI calls typed tools — add_bullet, complete_bullet, migrate_bullet — and the server handles parsing, validation, and persistence. The AI doesn't need to think about file formats or worry about corrupting your data. It just translates what you say into API calls. Fast, local, deterministic, and correct by construction.

Honestly, this probably has a shelf life. The moment AI agents can generate their own schemas and programmatic access on the fly — which Cowork and similar tools are inching toward — a hand-built MCP server for a bullet journal becomes redundant. But until that day, this works and it's fast.

Install```bash

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


Or build from source (requires Rust 1.85+):```bash
cargo install --path crates/bulletd-tui

Setup```bash

bulletd init


This creates a config file and data directory. You'll be prompted for where to store your daily logs.

## Usage```bash
bulletd        # Open the TUI
bulletd serve  # Start the MCP server (for AI agent access)

Daily Log

The main view is your daily log. Each bullet has a status:

Status Meaning
Open Not yet acted on
Done Completed
Migrated Moved to another day
Cancelled Dropped
Backlogged Shelved for later

Grouped View

Press g to toggle grouped-by-status view. Bullets are partitioned into sections — Open, Done, Migrated, Cancelled, Backlogged — with headers showing the count for each group. Empty groups are hidden. The MCP API supports this too: pass group_by: "status" to list_bullets and the AI gets pre-grouped results without having to sort them itself.

Keybindings

Key Action
a Add a new bullet
e Edit the selected bullet
d Mark done
o Reopen (set back to open)
x Cancel
m Migrate to tomorrow
u Unmigrate
b Move to backlog
D Delete
Enter Grab and reorder
j/k Navigate up/down
h/l Previous/next day
r Review open tasks for this day
O View all open tasks across recent days
H Migration history for selected bullet
g Toggle grouped-by-status view
i Toggle icon style (minimal/emoji)
q Quit

Data Format

Daily logs are stored as plain Markdown files — one per day, using GFM tables. They're readable in any text editor, any Markdown viewer, or on GitHub. No database, no proprietary format.```

2026-04-06

Status Bullet Notes Migration ID
📌 Fix flaky auth test Relies on wall clock timing b7
✅ Deploy to staging f4
➡️ Update SDK Blocked on v2.1 to 2026-04-07/m4 a9

### MCP Server

bulletd includes an MCP server so AI agents can read and write your journal programmatically:```bash
bulletd serve

This exposes tools for adding bullets, changing status, migrating tasks, and querying open items — all over stdio transport.

Claude Code

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


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

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:```json
{
"mcpServers": {
"bulletd": {
"command": "bulletd",
"args": ["serve"]
}
}
}


Restart Claude Desktop after saving.

#### Available MCP Tools

| Tool | Description |
|------|-------------|
| **Bullets** | |
| `add_bullet` | Add a bullet to a day's log |
| `list_bullets` | List bullets for a date, filter by status or group_by="status" |
| `list_open_bullets` | List all open bullets across recent days |
| `update_bullet` | Update a bullet's text |
| **Status** | |
| `complete_bullet` | Mark a bullet as done |
| `cancel_bullet` | Mark a bullet as cancelled |
| `open_bullet` | Set a bullet back to open |
| `batch_set_status` | Change status of multiple bullets at once |
| **Migration** | |
| `migrate_bullet` | Migrate a bullet to another day (defaults to tomorrow) |
| `unmigrate_bullet` | Reverse a migration, reopening the source bullet |
| `backlog_bullet` | Move a bullet to the backlog |
| `migration_history` | Trace a bullet's migration chain across days |
| **Notes** | |
| `append_note` | Append a note line to a bullet |
| `update_notes` | Replace all notes on a bullet |
| `clear_notes` | Clear all notes from a bullet |
| **Reorder** | |
| `move_bullet` | Move a bullet to a new position (top, bottom, or index) |

#### 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 bulletd-tui -- serve

# Or using the installed binary
npx -y @modelcontextprotocol/inspector bulletd serve

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

Philosophy

The Bullet Journal method works because of friction. Migrating a task forces you to decide if it's still worth doing. Tasks that aren't worth rewriting die naturally. bulletd preserves that friction digitally — there's no "snooze all" button, no auto-migration. Every open bullet asks you to make a choice.

Companion: wdttg

bulletd pairs well with wdttg (Where Did The Time Go?) — a terminal time tracker 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 问
答案由本站依据条目字段整理,不引用上游原文
Bulletd Digital Bullet Journal MCP Server 怎么安装?

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

Bulletd Digital Bullet Journal MCP Server 怎么在 Claude、Cursor、VS Code 里配置?

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

Bulletd Digital Bullet Journal MCP Server 收费吗?

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

Bulletd Digital Bullet Journal MCP Server 需要 API Key 吗?

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

Bulletd Digital Bullet Journal MCP Server 支持哪些客户端?

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

Bulletd Digital Bullet Journal MCP Server 能提供哪些能力?

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

Bulletd Digital Bullet Journal MCP Server 需要什么运行环境?

运行时为 Cross-platform。

热门专题

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

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