GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Allow injecting a notifier factory for notification filtering and checks · Issue #1197 · modelcontextprotocol/java-sdk

Allow injecting a notifier factory for notification filtering and checks #1197

New issue
Copy link
New issue
Copy link
Open
Enhancement
Open
Allow injecting a notifier factory for notification filtering and checks#1197
Enhancement
Copy link
Labels
P2Moderate issues affecting some users, edge cases, potentially valuable featureModerate issues affecting some users, edge cases, potentially valuable featurearea/serverenhancementNew feature or requestNew feature or request
Milestone
2.2.0-M3

Description

@chemicL
chemicL
opened on Oct 20, 2026
Issue body actions

Spec: Logging: Per-request log level

The server MUST NOT emit notifications/message for a request that does not include this field. […] notifications/message is request-scoped: the server MUST NOT deliver it on a subscriptions/listen stream or on any stream other than the one carrying the response to the request that set the log level.

Current behavior

McpAsyncNotifier.notify(method, params) sends any notification without checks. A handler can send notifications/message without a logLevel (or below the requested level), or notification types that don't belong to the request.

Proposal

Let users inject a notifier factory, so the policy is the user's choice and the framework doesn't hard-code one. A factory could:

  • drop or reject notifications by method
  • gate log messages on logLevel and the requested threshold
  • check extension-specific rules

The default stays permissive – the factory is the place to add stricter rules.

Activity

  1. chemicL
    added this to the 2.2.0-M2 milestone on Oct 20, 2026
  2. chemicL
    added
    enhancementNew feature or requestNew feature or request
    on Oct 20, 2026
  3. chemicL
    added the
    Enhancement
    issue type on Oct 20, 2026
  4. chemicL
    added
    area/server
    P2Moderate issues affecting some users, edge cases, potentially valuable featureModerate issues affecting some users, edge cases, potentially valuable feature
    on Oct 20, 2026
  5. tzolov
    modified the milestones: 2.2.0-M2, 2.2.0-M3 on Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Moderate issues affecting some users, edge cases, potentially valuable featureModerate issues affecting some users, edge cases, potentially valuable featurearea/serverenhancementNew feature or requestNew feature or request

    Type

    Enhancement

    Projects

    No projects

      Milestone

      • 2.2.0-M3No due date

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.