feat: add check_notifications tool #84
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/OpenSpec
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
RFC - Request For Comments
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
hermes-attempted
hermes-needs-clarification
hermes-ready
hermes-review
hermes-wip
human-required
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
agentic-forges/forgejo-mcp!84
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/84/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This commit introduces the check_notifications tool to the MCP server, allowing clients to query their unread or all notifications directly from Forgejo.
Implemented check_notifications in the user domain
Handles pagination and time filtering (since, before)
Added TDD tests using mockNotificationServer
Updated README.md to list the new tool.
Hi @byteflavour 👋 — we have built a showboat demo for the
check_notificationstool. Could you cherry-pick it into this PR?Commit:
codeberg.org/brenner-axiom/forgejo-mcp@6483e12File:
demos/check-notifications.mdThe demo uses
./forgejo-mcp --clito retrieve notifications live — no hardcoded credentials. Thanks!