2e5d62bdbc- Use instead of hardcoded token in demo - Return proper error on invalid RFC3339 time parse for since/before/last_read_at - Return the updated thread in MarkNotificationReadFn - Add new tools to minimalArgs in race test suite
1.9 KiB
1.9 KiB
Demo: notifications-management
2026-03-08T09:35:00Z by Showboat 0.6.1
What these tools do
The new notification management tools expand the Forgejo-MCP server to cover 100% of the notification API. They allow autonomous agents to:
- Retrieve individual notification threads (
get_notification_thread) - Mark notifications as read (
mark_notification_read) - Acknowledge all notifications at once (
mark_all_notifications_read) - Filter notifications scoped to a single repository (
list_repo_notifications) - Mark all notifications in a specific repo as read (
mark_repo_notifications_read)
This completes the autonomous feedback loop without relying on web GUIs.
Setup
Set FORGEJO_URL and FORGEJO_ACCESS_TOKEN environment variables, then invoke via the CLI.
FORGEJO_URL=https://codeberg.org FORGEJO_ACCESS_TOKEN=$CODEBERG_TOKEN forgejo-mcp --cli list_repo_notifications --help 2>/dev/null
Tool: list_repo_notifications
Description: Filter notifications scoped to a single repository
Parameters:
all boolean optional Include read notifications (default: false)
before string optional Before time (RFC3339)
limit number optional Page size
owner string required Repository owner
page number optional Page number (1-based)
repo string required Repository name
since string optional After time (RFC3339)
FORGEJO_URL=https://codeberg.org FORGEJO_ACCESS_TOKEN=$CODEBERG_TOKEN forgejo-mcp --cli get_notification_thread --help 2>/dev/null
Tool: get_notification_thread
Description: Get detailed info on a single notification thread
Parameters:
id number required Notification ID