What go-vikunja/vikunja shipped
Generated by FoxPlug from public activity — not affiliated with Vikunja.
Week of September 14, 2026
What shipped
- Expose Vikunja's v2 REST API actions to MCP clients through `/api/v2/mcp`, deriving 24 typed tools from the OpenAPI document including projects, tasks, labels, comments, assignees, and user search. Pull request #3860
- Users can now discover the MCP endpoint in Settings → MCP, create a token with suitable permissions, and follow connection instructions for their client. Pull request #3864
- Replace the useTaskActions facade with direct mutations, breaking up the deleted Pinia task store into a quick-add composable and direct mutation calls. Pull request #3950
- Activate query-owned tasks and boards with navigation query scopes, date/form boundaries, and quick-add orchestration. Pull request #3941
- Gantt bars narrower than their title now show a tooltip with the full task name on hover. Pull request #3917
- About dialog now shows 'Pro active' when the server advertises enabled pro features via `/info`. Pull request #3925
- Fix atom feed returning 500 on task assigned notifications by setting Target to feed owner instead of dereferencing nil. Pull request #3916
- Store queued import uploads in the file storage backend (local or S3) instead of temp directory, allowing any instance to run the import job. Pull request #3889
- Parse Z-suffixed timestamps as UTC in caldav instead of server timezone. Pull request #3883
- Add `/.well-known/change-password` redirect to password change page for password manager support. Pull request #3897
Why it matters
MCP support opens Vikunja to external tools and clients, while the v2 API refactor continues consolidating the frontend onto a modern data layer. Multiple bug fixes resolve issues with feeds, migrations, caldav, and UI stacking.
Changelog entry
- feat(mcp): expose v2 API tools over streamable HTTP Pull request #3860
- feat(settings): add MCP connection setup Pull request #3864
- refactor(tasks): replace the useTaskActions facade with direct mutations Pull request #3950
- refactor(tasks): activate query-owned tasks and boards Pull request #3941
- feat(gantt): show full title tooltip on bars too narrow for their label Pull request #3917
- feat(frontend): show pro license status in about dialog Pull request #3925
- fix(feeds): don't panic on task assigned notifications in atom feed Pull request #3916
- feat(migration): store queued import uploads in the file storage Pull request #3889
- fix(caldav): parse Z-suffixed timestamps as UTC Pull request #3883
- feat: add /.well-known/change-password redirect Pull request #3897
- fix(admin): show project owner with user component Pull request #3955
- fix(frontend): bucket dropdown stacking and close-on-select in task detail Pull request #3947
- fix(user)!: give colliding TOTP and account-locked error codes unique values Pull request #3901
- fix(migration): stop file imports from timing out and locking the migration slot Pull request #3827
- fix(restore): convert numeric bools when restoring into postgres Pull request #3898
- fix(restore): restore empty json column values as NULL Pull request #3896
MCP tools now available via /api/v2/mcp. Set up in Settings → MCP with a token. Vikunja tasks, projects, labels, and more are now discoverable and callable from MCP clients.
Vikunja now supports Model Context Protocol (MCP), allowing external tools and clients to interact with tasks, projects, labels, comments, and more through typed REST actions. Users can set up MCP connections in Settings and generate tokens with suitable permissions. The v2 API continues its frontend migration with query-owned tasks and direct mutations, while fixes address feeds, caldav timestamps, and import reliability.