Background

A recurring theme in this IG is that clients have been slow to implement support for resources. Before recommending skills-as-resources as a convention, we need to know which clients actually support resources/list, resources/read, resources/subscribe, and resource templates.

"Clients have been slow to implement support for resources. Had some parallel primitive 'skills' been implemented, I'm not sure clients would have implemented them any faster. Basically they all went for 'tools' and have slowly been getting around to implementing other primitives." — Cliff Hall

Scope

Survey the following MCP clients and document their resource support:

For each client, note:

• Whether resources are auto-loaded or require user action
• Whether the model can interact with resources directly (or if it's application-controlled only)
• Any known limitations or quirks

Acceptance Criteria

• Completed table for at least 5 major MCP clients
• Each entry verified by testing or by referencing official documentation
• Added to docs/experimental-findings.md as a new section
• Implications for the skills-as-resources approach discussed (1-2 paragraphs)

References

• Open Question 5
• Open Question 12 — "Why not just resources?"
• Feb 26 office hours notes — discussion on client resource support gaps