Skip to content

Notification on Capabilities #353

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
m-paternostro opened this issue Apr 16, 2025 · 0 comments
Open

Notification on Capabilities #353

m-paternostro opened this issue Apr 16, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@m-paternostro
Copy link

Is your feature request related to a problem? Please describe.
Hi there 👋

I think it would be really valuable for developers to receive notifications from MCP Server instances when capabilities are added, removed, updated, or (most importantly) invoked — including the result of the invocation.

Right now, there’s no built-in way to observe what the server is doing in real time, which makes it hard to monitor, debug, or track performance effectively.

Describe the solution you'd like
I’ve opened a PR that adds support for this kind of notification: #334

It wires up the McpServer to emit detailed lifecycle events for capabilities. I think this can be a powerful addition for observability and tooling integration.

Describe alternatives you've considered
In my own project, I’ve subclassed McpServer and wrapped capability callbacks to emit 'invoked', 'completed', and 'error' events manually. That approach works to an extent, but it’s far less robust than having this behavior built into McpServer itself.

Additional context
Happy to expand on anything in the PR — let me know if I missed a use case or if there’s something worth clarifying!

@m-paternostro m-paternostro added the enhancement New feature or request label Apr 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant