Really Him

@electrocucaracha cool, yeah I agree, I think this idea is already gaining momentum. To be clear though, I'm not a maintainer or anything, I just visit this repo a lot...

can you, like, at least add a title or something? this provides no info about your issue.

umm, doesn't the stack trace say it right here: > \"tools.49.custom.name: String should have at most 64 characters\"}} different providers/clients etc. have different constraints on how long a tool name...

so, (i) this capability is not mandatory - servers may or may not declare `resources: {listChanged: true}` when announcing their capabilities to the client in response to `initialize`, a la:...

**CORRECTION** My mistake, I was reading my code again, and I am actually sending the `resource/updated` manually when a subscribed resource is changed, via `session.send_notification`, so my reply above is...

Yeah so I just added some code to send the `list_updated` notification to all sessions when resource list changes, and it's coming through, but I had to do it manually,...

@salman-khandu i think you need to pass it in to InitializationOptions, see this snippet on python-sdk readme ``` async def run(): async with mcp.server.stdio.stdio_server() as (read_stream, write_stream): await server.run( read_stream,...

you might have to create the server using a different method, in the end I had to use lowlevel server :(

@salman-khandu this would depend on the client, I don't think the spec says what the client is supposed to do if it gets a resource-update or a list-changed notification. E.g....

This is a nuanced discussion involving https://github.com/modelcontextprotocol/python-sdk/pull/800 as well, I commented there that it's already permitted (from a model POV) for Notifications to include arbitrary extra data (models have `ConfigDict(extra="allow")`...