Repository navigation
[FEATURE]:Resource subscription #12092
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Since @paoloricciuti has pushed for Resources, part already supported my nearly all MCP server is subscription. Server can push the update value to the client for up to date ops.
3.5 Subscription
https://modelcontextprotocol.io/specification/2025-11-25/server/resources#subscriptions
5.2.4 URI subscription
https://modelcontextprotocol.io/specification/2025-11-25/server/tools#resource-links
Activity
github-actions commentedon Feb 4, 2026
This feature request is related to other MCP resource features in development. Please check these related issues:
While these are related MCP resource capabilities, your subscription feature request appears to be distinct (server push notifications for resource updates). Feel free to ignore if your use case is specifically about subscriptions and not covered by the above.
paoloricciuti commentedon Feb 4, 2026
That's an interesting request... I don't think any client right now supports resource subscriptions, which likely means very few server implements them but could be good to have regardless, like automatic fetching of resources returned from tools. I'll try to see if I can do something about it, even though for subscription resources it would be interesting to figure out the right flow...what should happen, for example, if the model is generating and a new resource notification comes from an MCP server?
Solido commentedon Feb 4, 2026
Many clients do but we need to differentiate lib from software.
It open SO much doors... the trick is this only available on the resource not tool
and surely the best way to use it is with #7510
If a new resource is generated then it will be exposed by the resource:uri/all but not uri{id} who will only send update.
paoloricciuti commentedon Feb 4, 2026
Sorry I didn't get wdym with your last sentence
Solido commentedon Feb 4, 2026
NP!
You can only subscribe to resource and resource can be defined in many ways!
you can say ticker/all so when you create a new entry, your question, the whole list is send.
You can also use the template form of resource, you register to an specific id using the template form {id} so ticker/{id}. When it update only that ticker is send back. Opencode send a tool request asking for ticker with id 22 let's say, he know register to it only.
#7510 is the ticket for template impl that is missing currently.
github-actions commentedon Apr 6, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.