[FEATURE]:Resource subscription #8500

Open
opened 2026-02-16 18:10:08 -05:00 by yindo · 5 comments
Owner

Originally created by @Solido on GitHub (Feb 4, 2026).

Originally assigned to: @thdxr on GitHub.

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

Originally created by @Solido on GitHub (Feb 4, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] 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
yindo added the discussion label 2026-02-16 18:10:08 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 4, 2026):

This feature request is related to other MCP resource features in development. Please check these related issues:

  • #8928: model-invoked MCP resources (allowing the model to discover and read resources automatically)
  • #7510: Resource templates support

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.

@github-actions[bot] commented on GitHub (Feb 4, 2026): This feature request is related to other MCP resource features in development. Please check these related issues: - #8928: model-invoked MCP resources (allowing the model to discover and read resources automatically) - #7510: Resource templates support 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.
Author
Owner

@paoloricciuti commented on GitHub (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?

@paoloricciuti commented on GitHub (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?
Author
Owner

@Solido commented on GitHub (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.

@Solido commented on GitHub (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](https://github.com/anomalyco/opencode/issues/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.
Author
Owner

@paoloricciuti commented on GitHub (Feb 4, 2026):

Sorry I didn't get wdym with your last sentence

@paoloricciuti commented on GitHub (Feb 4, 2026): Sorry I didn't get wdym with your last sentence
Author
Owner

@Solido commented on GitHub (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.

@Solido commented on GitHub (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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8500