Konbu

MCP办公协作

提供方 krtw00

办公协作 未标注 API Key 社区 / 第三方 Claude DesktopClaudeCursorCodex

A self-hostable all-in-one planner combining calendar, notes, todos, and bookmarks. Built-in MCP server lets Claude Desktop, Cursor, and any MCP client operate your personal data via natural language. Single Go binary, MIT licensed.

一句话选型结论

按资料字段整理

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

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

工具与能力

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

能力标签

支持客户端

适用场景

plannercalendarnotes

安装与配置

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

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

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

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

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

表单与审批

填表单、走审批流。

团队协作

同步任务、汇总进展。

选择建议

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

值得选的地方

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

先想清楚的地方

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

更适合

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

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Konbu当前 未标注 未标注 未标注 无 未标注
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

服务器档案

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

详细介绍

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

konbu

Your personal digital planner, kept by an AI butler.

CLI · MCP · Self-hostable · AI-native

One Go binary that binds your memos, todos, schedule, and tables into a single planner — searchable from one place, kept by AI.

Connect Claude, Cursor, or any MCP client to your data.

日本語 | English


Try It

  • Cloud -- Use instantly at konbu-cloud.codenica.dev (free, no setup)
  • Self-hosted -- Run on your own server with Docker (see below)

What is konbu?

konbu is a personal digital planner — a Filofax-style system planner, digitized. A self-hostable Go binary that binds your memos, todos, schedule, and structured tables into one notebook, kept by an AI butler, and surfaces everything from a single search interface. It's yours alone — nothing is ever shared out. Not a replacement for Notion + Todoist + Calendar — a replacement for the act of searching four apps to find one thing.

What's different:

  • Native MCP server + CLI client -- Two parallel routes for the AI butler (Claude / Cursor / any MCP client) or shell / scripts to operate your planner.
  • Cross-resource full-text search -- One query across memos, todos, events, and structured tables. This is the core UX, not a side feature.
  • Structured tables (= table-memo, planned) -- Track blood pressure, household budgets, or inventory. Markdown can't express these; tables can.
  • BYOK AI chat -- Bring your own OpenAI/Anthropic API key, or use the included free tier.
  • Personal by design -- One notebook, for you only. Pulls in from outside (Google Calendar), never leaks out.
  • Self-hostable -- One Go binary, Docker compose, or use the hosted version.

End the state of having your day scattered across four different apps.

Features

  • Cross-resource Full-text Search -- Search across memos, todos, events, and structured tables in one query (core UX)
  • CLI & MCP Server -- Built-in CLI client and MCP server. AI agents like Claude and Cursor can read and write your data directly
  • AI Agent Chat -- "Add groceries to my todo" "What's on my schedule tomorrow?" in natural language. BYOK supported, free tier included
  • Memos -- Markdown notes with tagging, live preview
  • ToDo -- Inline task creation with due dates, tags, and notes
  • Calendar -- Monthly view with event CRUD and iCal import (personal, owner-only)
  • Structured Tables (= table-memo, planned) -- Track structured data (blood pressure, household budget, inventory) as rows × columns
  • Export/Import -- JSON export, Markdown ZIP export, iCal import
  • i18n -- English and Japanese

Quick Start```bash

cp .env.example .env
docker compose up -d


Open `http://localhost:8080` and create your account. The dev compose file sets `DEV_USER=dev@local` to skip registration.

### Production (with Traefik)```bash
# Edit .env with real credentials and your domain
docker compose -f docker-compose.prod.yml up -d

Native (without Docker)```bash

Prerequisites: Go 1.25+, Node.js 22+, PostgreSQL 16+

Build frontend

cd web/frontend && npm ci && npm run build && cd ../..

Build server

go build -o bin/server ./cmd/server

Start (runs all SQL migrations automatically on boot)

DATABASE_URL="postgres://..." SESSION_SECRET="..." ./bin/server


## Configuration

| Variable | Required | Default | Description |
|---|---|---|---|
| `DATABASE_URL` | Yes | -- | PostgreSQL connection string |
| `SESSION_SECRET` | Yes | dev fallback | Session signing key |
| `PORT` | No | `8080` | Server port |
| `DEV_USER` | No | -- | Auto-login as this email (dev only) |
| `OPEN_REGISTRATION` | No | -- | Set `true` to allow anyone to register (for Cloud) |
| `BASE_URL` | No | -- | Public app URL used for OAuth callbacks |
| `GOOGLE_CLIENT_ID` | No | -- | Enable Google OAuth login |
| `GOOGLE_CLIENT_SECRET` | No | -- | Enable Google OAuth login |
| `WEBHOOK_SECRET` | No | -- | GitHub Sponsors webhook secret |
| `STRIPE_SECRET_KEY` | No | -- | Enable Stripe checkout and subscription billing |
| `STRIPE_WEBHOOK_SECRET` | No | -- | Verify incoming Stripe webhook events |
| `STRIPE_PRICE_MONTHLY` | No | -- | Stripe Price ID used for monthly Pro checkout |
| `STRIPE_PRICE_YEARLY` | No | -- | Stripe Price ID used for yearly Pro checkout |
| `GITHUB_FEEDBACK_TOKEN` | No | -- | GitHub token used to create anonymized feedback issues |
| `GITHUB_FEEDBACK_REPO` | No | -- | Repository to receive feedback issues, e.g. `krtw00/konbu` |
| `GITHUB_FEEDBACK_LABELS` | No | -- | Comma-separated labels added to forwarded feedback issues |
| `AI_ENCRYPTION_KEY` | No | -- | 64 hex chars used to encrypt BYOK AI keys |
| `DEFAULT_AI_PROVIDER` | No | `openai` | Server-side free-tier AI provider |
| `DEFAULT_AI_API_KEY` | No | -- | Server-side free-tier AI key |
| `DEFAULT_AI_ENDPOINT` | No | -- | Override free-tier provider endpoint |
| `DEFAULT_AI_MODEL` | No | -- | Override free-tier provider model |
| `R2_ACCESS_KEY_ID` | No | -- | Attachment upload credentials |
| `R2_SECRET_ACCESS_KEY` | No | -- | Attachment upload credentials |
| `R2_ENDPOINT` | No | Cloudflare R2 default | Attachment storage endpoint |
| `R2_BUCKET` | No | `konbu-attachments` | Attachment storage bucket |
| `R2_PUBLIC_URL` | No | -- | Optional public base URL for attachments |
| `SMTP_HOST` | No | -- | SMTP relay host for reminder emails (e.g. `smtp-relay.brevo.com`). Notifications are disabled unless all five `SMTP_*` variables are set. |
| `SMTP_PORT` | No | -- | SMTP relay port (typically `587` for STARTTLS) |
| `SMTP_USERNAME` | No | -- | SMTP relay login |
| `SMTP_PASSWORD` | No | -- | SMTP relay password / API key |
| `SMTP_FROM` | No | -- | From address for outgoing reminder emails |
| `NOTIFICATION_TICK_INTERVAL` | No | `1m` | Notification sweep interval (Go duration, e.g. `30s`, `2m`) |

### Reminders / notifications

When the `SMTP_*` variables above are all set, the server starts a single in-process sweep loop that sends email reminders for upcoming events and due ToDos. Each user opts in via **Settings** (`user_settings.notifications.enabled = true`) and can override the recipient email, lead time, due-time, and timezone.

Notifications are a **server-only feature** — they run inside the API server process and require PostgreSQL. The MCP `--standalone` mode (SQLite) does **not** send reminders.

### Docker Compose (prod) variables

| Variable | Description |
|---|---|
| `POSTGRES_PASSWORD` | PostgreSQL password |
| `KONBU_DOMAIN` | Domain for Traefik TLS routing |

## CLI

The CLI is a standalone client that connects to a remote konbu server via API. Server code is not included in the CLI binary.```bash
go install github.com/krtw00/konbu/cmd/konbu@latest

Setup```bash

Set environment variables (recommended: add to ~/.zshrc or ~/.bashrc)

export KONBU_API=https://konbu.example.com
export KONBU_API_KEY=your-api-key

Or pass as flags

konbu --api https://... --api-key your-key memo list


Generate an API key in **Settings > Security** on the web UI.

### Commands

All commands support `--json` flag for machine-readable output.```
konbu memo list                        # List memos
konbu memo show <id>                   # Show memo content
konbu memo add "title" -c "content"    # Create memo (-c - for stdin)
konbu memo edit <id> --title "new"     # Update memo
konbu memo rm <id>                     # Delete memo

konbu todo list                        # List todos
konbu todo show <id>                   # Show todo details
konbu todo add "task" -t "tag1,tag2"   # Create todo
konbu todo add "task" -d 2025-04-01    # Create with due date
konbu todo edit <id> --desc "notes"    # Update todo
konbu todo done <id>                   # Mark done
konbu todo reopen <id>                 # Reopen
konbu todo rm <id>                     # Delete

konbu event list                       # List events
konbu event show <id>                  # Show event details
konbu event add "title" -s <RFC3339>   # Create event
konbu event edit <id> --title "new"    # Update event
konbu event rm <id>                    # Delete

konbu tag list                         # List tags
konbu tag rm <id>                      # Delete tag

konbu search "query"                   # Cross-search

konbu api-key list                     # List API keys
konbu api-key create "key-name"        # Create API key
konbu api-key rm <id>                  # Delete API key

konbu export json -o backup.json       # Export as JSON
konbu export markdown -o backup.zip    # Export as Markdown ZIP
konbu import ical calendar.ics         # Import iCal file

Short IDs (first 8 chars) can be used in place of full UUIDs.

MCP Server

konbu can run as a built-in MCP (Model Context Protocol) server in two modes — pick whichever fits.

Standalone mode (SQLite, no server required)

If you just want konbu as a local MCP backend for Claude Desktop, Cursor, or any MCP client, install the CLI and run it with --standalone. No PostgreSQL, no web server, no API key — everything is stored in a local SQLite file.```bash
go install github.com/krtw00/konbu/cmd/konbu@latest
konbu mcp --standalone


Data is persisted at `~/.konbu/konbu.db` by default. Override with `--db /path/to/db.sqlite` if needed.

**Claude Desktop** (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS, `%APPDATA%\Claude\claude_desktop_config.json` on Windows):```json
{
  "mcpServers": {
    "konbu": {
      "command": "konbu",
      "args": ["mcp", "--standalone"]
    }
  }
}

Cursor accepts the same config at ~/.cursor/mcp.json (or via the settings UI).

Docker

A multi-arch image (linux/amd64, linux/arm64) is published to GitHub Container Registry. Pull it directly — no build step needed:```bash
docker pull ghcr.io/krtw00/konbu-mcp:latest


For reproducible setups, pin to a release tag instead — e.g. `docker pull ghcr.io/krtw00/konbu-mcp:v0.2.0`.

Then point your MCP client at it. Data persists in a named volume:```json
{
  "mcpServers": {
    "konbu": {
      "command": "docker",
      "args": ["run", "--rm", "-i", "-v", "konbu-data:/data", "ghcr.io/krtw00/konbu-mcp:latest"]
    }
  }
}

Prefer building from source? docker build -f docker/Dockerfile.mcp -t konbu-mcp . from the repo root produces the same image (CGO-free, distroless static, ~22 MB).

Standalone mode exposes memo / todo / calendar event CRUD plus cross-resource search. Tags, attachments, and AI chat are server-only (use the connected mode below for those).

Connected mode (talk to a konbu server)

If you're running a konbu server (self-hosted or konbu Cloud), point the MCP server at it over HTTP. You get the full feature set: tags, attachments, and AI chat.

  1. Install the konbu CLI binary (see CLI section above)
  2. Generate an API key in Settings > Security on the web UI
  3. Add konbu to your MCP client config:```json
    {
    "mcpServers": {
    "konbu": {
    "command": "konbu",
    "args": ["mcp"],
    "env": {
    "KONBU_API": "http://localhost:8080",
    "KONBU_API_KEY": "your-api-key"
    }
    }
    }
    }

### Usage examples

After restarting your MCP client, interact with konbu in natural language:

- "What's on my schedule tomorrow?"
- "Add a dentist appointment next Friday at 1pm"
- "Create a todo to buy groceries with tag 'shopping'"
- "Show me notes tagged 'meeting' from last week"
- "Mark the 'review PR' todo as done"

## API

Base path: `/api/v1`

| Resource | Endpoints |
|---|---|
| Auth | `POST /auth/register`, `POST /auth/login`, `POST /auth/logout`, `GET /auth/setup-status`, `GET /auth/providers`, `GET /auth/google/login`, `GET /auth/google/callback` |
| User | `GET/PUT /auth/me`, `GET/PUT /auth/settings`, `POST /auth/change-password`, `POST /auth/delete-account` |
| API Keys | `GET/POST /api-keys`, `DELETE /api-keys/:id` |
| Memos | `GET/POST /memos`, `GET/PUT/DELETE /memos/:id`, `GET/POST /memos/:id/rows`, `POST /memos/:id/rows/batch`, `GET /memos/:id/rows/export`, `PUT/DELETE /memos/:id/rows/:rowId` |
| ToDos | `GET/POST /todos`, `GET/PUT/DELETE /todos/:id`, `PATCH /todos/:id/done`, `PATCH /todos/:id/reopen` |
| Events | `GET/POST /events`, `GET/PUT/DELETE /events/:id` |
| Calendars | `GET/POST /calendars`, `GET/PUT/DELETE /calendars/:id` (owner-only) |
| Tags | `GET/POST /tags`, `PUT/DELETE /tags/:id` |
| Search | `GET /search?q=...` |
| Chat | `GET/POST /chat/sessions`, `GET/PUT/DELETE /chat/sessions/:id`, `POST /chat/sessions/:id/messages`, `GET/PUT /chat/config` |
| Attachments | `POST /attachments`, `GET /attachments/*` |
| Export | `GET /export/json`, `GET /export/markdown` |
| Import | `POST /import/ical` |

## Development```bash
# Start PostgreSQL
docker compose up -d postgres

# Frontend dev server
cd web/frontend && npm run dev

# Run server
DEV_USER=dev@local go run ./cmd/server

# Build CLI
go build -o bin/konbu ./cmd/konbu

# Run tests
go test ./...
cd web/frontend && npm test
cd web/frontend && npm run test:e2e

Project Structure```

cmd/
server/ # API server
konbu/ # CLI client
internal/
handler/ # HTTP handlers
service/ # Business logic
repository/ # DB access (sqlc)
middleware/ # Auth, logging
client/ # API client (used by CLI)
mcp/ # MCP server
web/frontend/ # React + Vite SPA
sql/ # Schema and migrations
docker/ # Dockerfile
```

Roadmap

  • Browser push reminders (email reminders are already supported when SMTP_* env is configured)
  • Mobile UI improvements
  • CI test coverage
  • AI chat enhancements (context improvements, new model support)

Sponsors

If you find konbu useful, consider sponsoring the project.

License

MIT

常见问题

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

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

Konbu 怎么在 Claude Desktop、Claude、Cursor 里配置?

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

Konbu 收费吗?

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

Konbu 需要 API Key 吗?

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

Konbu 支持哪些客户端?

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

Konbu 能提供哪些能力?

资料显示能力标签包括 planner、calendar、notes、bookmarks、self hosted、golang。具体工具清单以官方文档为准。

Konbu 需要什么运行环境?

运行时为 Cross-platform。

热门专题

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

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