Time Management

Read your Pyunto Time Management schedule and log time from an AI assistant.

Connector by pyunto.com · Domain verified by the MCP Registry

IndexedMITLocal (stdio)

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/pyunto-com-time-management

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Read your Pyunto Time Management schedule and log time from an AI assistant. E2EE project planning.

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools: 5 read · 3 write · 1 delete · 1 not yet classified
Secrets: 3 (API keys, tokens or passwords)
Install scripts: Not scanned yet
Runs as: Node.js package

Tools by what they do 10

Read from the source code; the running server may list different tools.

Read 5 · Look things up without changing anything.

list_deleted_time_blocks
list_projects
list_tasks
list_time_blocks
whoami

Write 3 · Create, change, send or run things.

log_time
restore_time_block
update_time_block

Delete 1 · Delete, drop, revoke or wipe things.

delete_time_block

Not yet classified 1 · We could not tell from the name and description.

time_summary

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

PYUNTO_TM_API_KEY
PYUNTO_TM_PASSWORD
PYUNTO_TM_PASSWORD_FILE

Other settings (environment variables or headers).

PYUNTO_TM_BASE_URL

Tools (10)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

delete_time_block
Permanently delete ONE recorded time block, along with any files attached to it. Before calling it you MUST show the user the block you are about to delete (date, start and end time, project, task and memo, from list_time_blocks) and get an explicit yes for that specific block. Never infer the block from a vague instruction, and never delete several blocks because the user described a range — confirm and delete them one at a time. A deleted block can be put back with restore_time_block for 14 days, after which it and its attachments are purged for good and cannot be recovered; say so when you …
list_deleted_time_blocks
Time blocks that were deleted but can still be restored, newest first, each with the date it was deleted and the deadline for putting it back. Use it to find the block_id for restore_time_block when the user says they deleted something by mistake. Requires the blocks:read scope.
list_projects
List every project the account can see, with id, name, colour and role (owner/editor/viewer). Use it to resolve a project name the user typed into the project_id other tools need. Requires the projects:read scope.
list_tasks
List Gantt tasks (and subtasks) with their id, project, name and date range. Filter to one project with project_id. Use it to resolve a task name into the task_id that log_time takes. Requires the projects:read scope.
list_time_blocks
The individual time blocks logged between two dates (inclusive, max 92 days), with start/end times, duration, project, task and memo. This is the detailed schedule; use time_summary when you only need totals. Requires blocks:read.
log_time
Record a block of worked time on the calendar. Writes to the user's real schedule, so confirm the project, date and times with them before calling it. Requires the blocks:write scope; for an end-to-end-encrypted project a memo additionally needs PYUNTO_TM_PASSWORD so it can be encrypted locally.
restore_time_block
Put a deleted time block back on the calendar, along with any files that were attached to it. Get block_id from list_deleted_time_blocks. Works only within the 14-day recovery window; after that the block is gone for good. Requires the blocks:write scope.
time_summary
Total hours logged between two dates (inclusive, max 92 days), grouped by project, by task, or by day. This is the tool to answer 'how much time did I spend on X' and to write a work log or diary entry. Requires record:read.
update_time_block
Change an already-recorded time block: its date, start/end times, memo, or the task it counts towards. Get block_id from list_time_blocks. Only the fields you pass change. Tell the user what the block currently says and what it will say before calling this. Requires the blocks:write scope; changing a memo on an end-to-end-encrypted project also needs PYUNTO_TM_PASSWORD, and project_id so the memo is encrypted under the right key.
whoami
Who this MCP server is connected as: account email, API key name, granted scopes, server URL, and whether end-to-end-encrypted names can be decrypted. Call this first when a tool fails, to see which scopes are missing.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Oct 18, 2026 (11 days ago)
Last release: Oct 18, 2026 (11 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name: com.pyunto/time-management
Version: 0.3.6
Auth: API key
Packages: npm @pyunto/tm-mcp
License: MIT
Repository: github.com/pyunto/tm-integrations
Website: tm.pyunto.com/docs/mcp.en.md
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: Official MCP Registry github-graphql