worklog-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@worklog-mcpAdd 'Deployed v2.3 to staging' to my worklog"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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-mcpRequires 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.
Related MCP server: @dwsm/changelog-mcp
Add it to your agent
claude mcp add worklog -- worklog-mcp serve --dir /path/to/notesAdd --scope user to make it available in every project.
{
"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"]Or: codex mcp add worklog -- worklog-mcp 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=3Exit 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.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Manage tasks, Focus Zone, notes, projects, and task history from compatible AI assistants.
AI-native task management: list, create, update and archive tasks with rich context for AI agents
Manage Superlist tasks and lists in plain language from any MCP-compatible AI agent.
Create and manage MeisterTask projects, tasks, and notes from your AI assistant.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables natural language todo list management through Claude Desktop with YAML-based persistence. Supports creating, completing, deleting, and listing todo items with automatic timestamp tracking and secure file permissions.-
- AlicenseAqualityDmaintenanceEnables safe changelog management for AI assistants with append-only entries, automatic versioning, and backups to prevent accidental deletion or formatting inconsistencies.815MIT
- FlicenseAqualityDmaintenanceEnables AI assistants to manage tasks across multiple projects with structured Markdown files, supporting creation, updates, completion, and organization with metadata and dependencies.7-
- AlicenseNot gradedqualityDmaintenanceEnables Claude to read your Obsidian vault and retrieve outstanding tasks from daily notes by parsing checkboxes.5,361Apache 2.0
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/feodor-ra/worklog-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server