Time Management

What time-management MCP server does

The time-management MCP server connects an AI client to a Pyunto Time Management account. It provides access to schedule information and supports logging time through the MCP interface. The underlying service is a time-management and project-planning application with end-to-end encryption.

The repository contains the client-side integration rather than the Pyunto service itself. Its MCP package uses the documented public REST API. The repository also includes a TypeScript SDK, which handles API requests and local decryption for encrypted account data.

Schedule-related dates, durations, and aggregates can be accessed without providing key material. Project and task names, along with memos, are encrypted. To read those values in decrypted form, the integration uses the account password locally to unwrap the private key.

How it works

The time-management MCP server runs as the published @pyunto/tm-mcp npm package. An MCP-compatible client starts the package with npx, and the package authenticates API requests with a Pyunto API key. The key is created in the Pyunto application under Settings → Account → API keys.

API key scopes determine which operations the integration may perform. A key can be revoked from the account, so access can be removed without changing the client configuration permanently.

When encrypted names or memos must be read, the password is used in the local process to unwrap the private key. According to the repository documentation, the password is not transmitted. The published code includes the SDK crypto implementation and the MCP entry point for inspection.

Setup and configuration

Add the published package to an MCP client and provide PYUNTO_TM_API_KEY. The repository shows this setup for Claude:

claude mcp add pyunto-tm \
  --env PYUNTO_TM_API_KEY=ptm_your_key \
  -- npx -y @pyunto/tm-mcp

Full instructions are available for Claude Desktop, Codex CLI, and Cursor in the Pyunto MCP documentation. No repository clone is required for normal use because the package runs directly from npm.

For local development, the repository uses npm workspaces and requires Node 18 or newer. npm install, npm run build, and npm test are the documented development commands. The tests cover SDK crypto round trips and MCP tools against a stub API.

Tools and capabilities

This time-management MCP server supports the following documented capabilities:

• Read a Pyunto Time Management schedule.
• Log time from an AI assistant.
• Access dates, durations, and aggregate service records without decryption keys.
• Decrypt project and task names locally after unlocking the account.
• Read encrypted memos when the account is unlocked.
• Use API key scopes to limit permitted reads and writes.

The repository excerpt does not specify individual MCP tool names or provide a complete operation list, so integrations should not depend on undocumented names.

Limitations and notes

The Pyunto service is not open source; this repository publishes only the client libraries, API calls, and local cryptographic code. The integration does not directly access the service database, manage billing, or retain a private key.

The time-management MCP server needs a valid API key to connect. Decrypted project and task data additionally requires the account password, and only data that the API key's scopes permit can be read or changed. Review the scopes before creating a key and revoke it when access is no longer needed.

The repository is licensed under MIT. Security issues should be reported privately to support@pyunto.com rather than posted as public issues.