Labsco
MCP SERVER

Togello MCP Server

by Toru-Takagi

Read and update Togello tasks, the day's memo and the running activity log, from your assistant.

Project & Task ManagementVerified
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