Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Worklog is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Work log for AI agents: record, search and report finished work, with web view and timesheet.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'WORKLOG_OWNER=${WORKLOG_OWNER}' --transport stdio worklog-mcp '--' docker run -i --rm -v worklog-data:/data -e WORKLOG_OWNER ghcr.io/axute/worklog-mcp:1.1.1 worklog-server --stdio
# 2 — ask your agent for something these tools do
# log_entry, log_entries, update_entry and 4 more
It needs WORKLOG_OWNER: this reads it from your environment, so export it first.
Worklog costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Worklog as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It has not been scanned here, so read the surface, and its source, before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Docker installed and running. Only the required variables are passed into the container. To set an optional one (WORKLOG_AGENT, TZ), add -e NAME before the image name and give it a value in the entry’s env: an unset -e would clear the default the image sets. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads WORKLOG_OWNER (Your user name; all entries belong to this user) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx WORKLOG_OWNER … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'WORKLOG_OWNER=${WORKLOG_OWNER}' --transport stdio worklog-mcp '--' docker run -i --rm -v worklog-data:/data -e WORKLOG_OWNER ghcr.io/axute/worklog-mcp:1.1.1 worklog-server --stdioReconnect, or start a new session, and the tools appear in the model’s tool list.
It reaches a system of yours, so it needs settings only you can give it: WORKLOG_OWNER — Your user name; all entries belong to this user. You set it in your own client’s config, on your machine — this marketplace never holds it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Record a finished unit of work in the work log.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Project or topic, e.g. the repository name ('website', 'backup-scripts'). |
| summary | string | yes | One sentence: what was done. Max. {SUMMARY_MAX} characters. |
| details | string | no | Optional: important commands, changed files, decisions. No secrets. |
| tags | array | no | Optional short tags, e.g. ['update', 'docker']. |
| duration_min | integer | no | Optional estimated duration in minutes. |
| session_id | string | no | Optional id that groups the entries of one session. |
| ts | string | no | Optional: when the work was done, for entries logged afterwards. ISO date ('2025-03-14', counted as noon) or datetime ('2025-03-14T16:30'); without an offset in the server's time zone. Default: now. N |
Record several units of work at once, typically the history of a project logged afterwards (each with its own ts). Check first with list_entries / search_entries what is already logged, so nothing is entered twice. All entries are checked before any is written.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entries | array | yes | Up to {LOG_MANY_MAX} entries. |
Correct an entry this agent logged earlier, e.g. a wrong project name or a typo.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entry_id | integer | yes | Id of the entry, as returned by log_entry or list_entries. |
| project | string | no | New project name. |
| summary | string | no | New summary, max. {SUMMARY_MAX} characters. |
| details | string | no | New details (replaces the old text). |
| tags | array | no | New tags (replace the old ones). |
| duration_min | integer | no | New duration in minutes. |
List work log entries, newest first. Times are shown in the server's time zone.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | no | Only this project. |
| agent | string | no | Only entries of this agent. |
| since | string | no | ISO date or datetime, inclusive, e.g. '2026-11-01'. |
| until | string | no | ISO date or datetime, exclusive. |
| limit | integer | no | Maximum number of entries (1-500). |
Full text search in the work log, best matches first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Words to search for in summary, details, project and tags. All words must match; word beginnings are enough ('deploy' finds 'deployment'). |
| project | string | no | Only this project. |
| limit | integer | no | Maximum number of results (1-500). |
Entries of a period grouped by day and project, with durations and totals.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | yes | Start, ISO date or datetime, inclusive, e.g. '2026-11-09'. |
| until | string | yes | End, ISO date or datetime, exclusive, e.g. '2026-11-16' for a full week. |
| project | string | no | Only this project. |
Known projects with number of entries, total logged minutes, last entry and the user's notes (description, customer, archived), most recent first. Use the exact project names from here when logging, so entries end up in the same project. Archived projects are finished: log to them only if the work…
Takes no parameters.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Worklog or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing ships as a container image. The scanner reads packages on npm and PyPI and public source; an image is neither, so there is no grade here — not a withheld one, an unmeasured one.
Release history
It installs from a container image rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 1.1.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Worklog can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.