QuickApps version
latest
What is the problem this feature will solve?
QuickApps' MCP integration consumes only the tools capability. MCP servers also expose resources (and prompts) that could serve as context sources, but QuickApps ignores them, and nothing negotiates capabilities with the server before use.
What is the feature you are proposing to solve the problem?
Extend the MCP toolset beyond tool calls, starting with resources (Phase 1, per the design doc drafted in PR #384):
- Config extension to opt an MCP toolset into loading server resources as context, with URI filtering.
- Capability negotiation so only server-advertised capabilities are loaded.
- Secondary fixes: independent error handling per capability, pagination for resource/prompt listings.
Existing configs remain unchanged by default.
What alternatives have you considered?
No response
Additional information
Design doc: PR #384 (draft). This issue adopts that work as its tracking issue.
QuickApps version
latest
What is the problem this feature will solve?
QuickApps' MCP integration consumes only the
toolscapability. MCP servers also expose resources (and prompts) that could serve as context sources, but QuickApps ignores them, and nothing negotiates capabilities with the server before use.What is the feature you are proposing to solve the problem?
Extend the MCP toolset beyond tool calls, starting with resources (Phase 1, per the design doc drafted in PR #384):
Existing configs remain unchanged by default.
What alternatives have you considered?
No response
Additional information
Design doc: PR #384 (draft). This issue adopts that work as its tracking issue.