timemanager-mcp

# timemanager-mcp A standalone stdio MCP server exposing your TimeManager tasks to a coding assistant. It uses the official MCP Python SDK (stable v1), Python 3.11+, and HTTPS requests to your hosted TimeManager API. It imports no TimeManager application code and needs no access to the private application repository. ## Availability Published to PyPI as `timemanager-mcp`; `uvx timemanager-mcp` works as shown below. This directory is still the package's source of truth — it has not yet been extracted into its own public repository (see "Independent development and release"). ## Configure 1. Open your TimeManager bot and run `/dev_token`. Generate a token and save it immediately; it is shown once. Rotation invalidates the previous token. 2. Set `TIMEMANAGER_API_URL` to the API origin (for example, `https://your-timemanager.example`) or its `/api/v1` root. 3. Set `TIMEMANAGER_TOKEN` to your `tm_pat_...` token in the environment inherited by the MCP process. Keep it out of version-controlled files. 4. Register the command `uvx` with arguments `["timemanager-mcp"]` in your assistant's MCP server configuration. There is no required task category: point the assistant at any task by ID and use your own judgment about which ones make sense to hand off. A generic `mcpServers` configuration for clients using that format: ```json { "mcpServers": { "timemanager": { "command": "uvx", "args": ["timemanager-mcp"] } } } ``` The parent process must pass both environment variables to this server. If a client uses its own `env` settings, place credentials only in its private local configuration. Variable interpolation syntax depends on the MCP client. ## Tools | Tool | Arguments | Behavior | |---|---|---| | `list_tasks` | optional `status`, `category` | List up to 100 tasks | | `get_task` | `task_id` | Read full task detail | | `fetch_task_attachment` | `task_id`, `attachment_id` | Fetch one listed image or file, up to 20 MiB | | `start_t…