complete-activity-log
Completes an activity log.
LABSCO SUMMARY
Tasks, calendar and time tracking answer in one conversation.
What am I meant to be doing today and start the clock on this belong to the same session here, because the to-do list, the day's memo, the linked calendar and the activity log are all reachable. Per-request tokens are what make a shared remote deployment sane.
What it is
A Togello client covering its TODO tasks and categories, calendar date memos, the linked Google Calendar, and the activity items and logs that record what you are working on right now.
What you get
- Tasks read — incomplete by default, or the ones completed inside a period you give as RFC3339 timestamps — and filtered by category
- Tasks created and updated with name, detail, status, URL, scheduled start and end, deadline, and category assigned or removed
- The TODO categories listed with their names and UUIDs, which is what the filters take
- A calendar memo for a given date read, updated or cleared
- Yesterday, today and tomorrow from the linked Google Calendar, alongside the scheduled tasks
- Activity items listed, a log started against one and completed when the work stops — and because at most one log has no end time, reading the list tells you whether the person is doing something now
- The current time in Japan, so relative dates resolve against a real clock
- Annotations on every tool: read-only tools declare it, and only the ones that can overwrite existing private data are marked destructive
- Stable JSON in both structuredContent and text for the read tools, and failures returned as JSON marked isError rather than as prose
Requirements
Node.js 22 or later and a Togello API token. Locally that is TOGELLO_API_TOKEN with the server run over stdio from npm as togello-mcp-server. Remote mode serves streamable HTTP at /mcp, keeps the older SSE and message endpoints for legacy clients, and publishes OAuth authorization-server and protected-resource metadata at the well-known paths. Passthrough auth expects each client to send its own token and is the mode for a published server; the single shared-token mode needs TOGELLO_MCP_ALLOW_ENV_AUTH=true before it will bind to a non-local host.
Setup effort
One command plus a key — npx -y togello-mcp-server, then supply credentials
USE CASES
01
Planning the day out loud
Pull today's calendar events beside the open tasks, anchored to the current time, and decide the order.
02
Capturing a task as it comes up
Create it with its category, scheduled window and deadline in the same call, rather than writing it down to file later.
03
Tracking what you are actually working on
Start a log against an activity item when you begin and close it when you stop; an open log with no end time is what says you are still in it.
04
Reporting what got done last week
Ask for tasks completed between two dates and read the activity logs from the same period alongside them.
05
Keeping notes against a date
Read the memo for the day, add to it, or clear it — the note stays attached to the date rather than to a task.
12 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create-task
Creates a new task in the TODO feature.
get-activity-item-list
Retrieves the list of activity items from the integration feature. Recognizes activity item UUID / item name
get-activity-log-list
Retrieves the list of activity logs from the integration feature. Since it is a record of what the person has done, if all the end dates are filled in, this person is not doing anything now. If there is one with a null end date, there should be at most one, and if there is one, it means that the person is doing it now. Recognizes activity log UUID / start date and time / end date and time / item name.
get-calendar-date-memo
Retrieves a calendar date memo for the specified date. Recognizes target date and memo content.
get-japan-current-time
Returns the current time in Japan (JST).
get-tasks-list
Retrieves tasks from the TODO feature. By default it returns incomplete tasks. For tasks completed yesterday or during another period, set completionStatus to COMPLETED and pass completedStartDate and completedEndDate as RFC3339 date-times. Recognizes task uuid / task name / status / detail / completed date and time / scheduled start date and time / scheduled end date and time / deadline date and time / priority / category
get-today-calendar
Retrieves scheduled events for yesterday/today/tomorrow from the linked Google Calendar. Recognizes event name / start date and time / end date and time.
get-todo-category-list
Retrieves the list of categories from the TODO feature. Recognizes category name / category UUID
start-activity-log
Starts an activity log.
update-calendar-date-memo
Updates a calendar date memo for the specified date.
update-task
Updates a task in the TODO feature.
BEFORE YOU INSTALL
What to know first
Tools you get
12 tools when we connected. Five tools write: create-task, update-task, update-calendar-date-memo, start-activity-log and complete-activity-log. get-tasks-list returns incomplete tasks unless you pass completionStatus COMPLETED with completedStartDate and completedEndDate, and get-japan-current-time uses Japan time.
Requires
- npx on PATH
- Node.js 22 or later
- TOGELLO_API_TOKEN in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 12 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y togello-mcp-serverMCP Clients
Any MCP client — npx
ANY MCP CLIENT — NPX · JSON
{
"mcpServers": {
"togello": {
"command": "npx",
"args": [
"-y",
"togello-mcp-server"
],
"env": {
"TOGELLO_API_TOKEN": "<YOUR_TOGELLO_API_TOKEN>"
}
}
}
}Remote server — self-hosted
Remote mode runs from a clone of the repository:
REMOTE SERVER — SELF-HOSTED · TERMINAL
git clone https://github.com/Toru-Takagi/togello-mcp-server
cd togello-mcp-server
npm install
npm run buildStart it in remote mode, on a host your clients can reach:
REMOTE SERVER — SELF-HOSTED · TERMINAL
TOGELLO_MCP_MODE=remote \
TOGELLO_MCP_AUTH_MODE=passthrough \
TOGELLO_MCP_HOST=0.0.0.0 \
TOGELLO_MCP_PORT=8081 \
npm startClients then connect to https://your-domain.example/mcp on that host (the older /sse endpoint is kept for clients such as ChatGPT developer mode), and each one sends its own Togello API token as an Authorization: Bearer header.
