worklog-mcp

🇺🇸 English · 🇷🇺 Русский

An MCP server that records finished work in your daily log. Point it at a directory of log files; it appends one done item to the checklist of the newest one.

If you keep a note per day with a checklist of what got done, the assistant that did the work can write the line itself. The directory is configured once, when the server starts, so it never travels through the conversation — the model sees the file's name and the line it wrote, and nothing else.

{
  "mcpServers": {
    "worklog": {
      "command": "worklog-mcp",
      "args": ["serve", "--dir", "/path/to/your/notes"]
    }
  }
}

That is the whole setup. The assistant now has append and check.

Install

uv tool install worklog-mcp

Requires Python 3.13+. No editor, vault format or note-taking app is assumed: a log file is any text file with a markdown checklist in it.

Add it to your agent

claude mcp add worklog -- worklog-mcp serve --dir /path/to/notes

{
  "mcpServers": {
    "worklog": {
      "command": "worklog-mcp",
      "args": ["serve", "--dir", "/path/to/notes"]
    }
  }
}

{
  "mcpServers": {
    "worklog": {
      "command": "worklog-mcp",
      "args": ["serve", "--dir", "/path/to/notes"]
    }
  }
}

{
  "servers": {
    "worklog": {
      "type": "stdio",
      "command": "worklog-mcp",
      "args": ["serve", "--dir", "/path/to/notes"]
    }
  }
}

{
  "mcpServers": {
    "worklog": {
      "command": "worklog-mcp",
      "args": ["serve", "--dir", "/path/to/notes"]
    }
  }
}

{
  "context_servers": {
    "worklog": {
      "command": "worklog-mcp",
      "args": ["serve", "--dir", "/path/to/notes"],
      "env": {}
    }
  }
}

{
  "mcpServers": {
    "worklog": {
      "command": "worklog-mcp",
      "args": ["serve", "--dir", "/path/to/notes"]
    }
  }
}

[mcp_servers.worklog]
command = "worklog-mcp"
args = ["serve", "--dir", "/path/to/notes"]

{
  "mcpServers": {
    "worklog": {
      "command": "worklog-mcp",
      "args": ["serve", "--dir", "/path/to/notes"]
    }
  }
}

{
  "mcp": {
    "worklog": {
      "type": "local",
      "command": ["worklog-mcp", "serve", "--dir", "/path/to/notes"]
    }
  }
}

How to use it

1. Keep the path out of the config file, if you like. Both options read an environment variable — WORKLOG_DIR and WORKLOG_FILE_PATTERN — so the snippet can carry no path at all:

{
  "mcpServers": {
    "worklog": {
      "command": "worklog-mcp",
      "args": ["serve"],
      "env": { "WORKLOG_DIR": "/path/to/notes" }
    }
  }
}

2. Narrow down which files count, if the directory holds more than logs. --pattern is a regular expression matched against the file name:

worklog-mcp serve --dir ~/notes --pattern '^\d{4}-\d{2}-\d{2}\.md$'

Without a pattern, every non-hidden file in the directory is a candidate, and the newest one wins.

3. Check the setup from a terminal whenever a call reports something missing:

worklog-mcp check --dir ~/notes
# ok: file="2026-09-06.md" items=3

Exit codes are 0 ok, 2 no directory, 3 no log file, 4 no checklist.

Why it's cool

• The path stays out of the conversation. It is a launch argument, read by the local process. Results carry a file name, never a directory.
• It never creates a log file. A missing file or directory is reported and the call stops, so the assistant cannot reorganize your notes. The one thing it does add is a checklist, when today's file has none yet.
• Repeating a call is safe. An item whose text is already in the checklist is not written twice, so a retried workflow does not double a line.
• Your formatting survives. The new item reuses the indent and bullet marker of the checklist's first item, and the file keeps its line endings; the write is atomic, so an editor watching the file never sees it truncated.

Documentation

📖 Full documentation — configuration, ready-made client snippets, exactly how the file and the checklist are picked, the tool contracts and an API reference. Available in English and Russian.

License

MIT — see LICENSE.