feat: MCP Resources - Expose browsable data via resource:// URIs

[nesquikm]

🦆 Duck Enhancement Proposal

💡 The Problem

MCP defines three primitives: Tools, Prompts, and Resources. We implement Tools and Prompts but not Resources. This means clients can't browse conversation history, provider configs, or usage data without calling a tool.

🚀 Proposed Solution

Implement MCP Resources to expose server data as browsable, read-only content.

Proposed resources:

• resource://providers → list of configured providers with status
• resource://providers/{name} → provider details (model, capabilities, health)
• resource://conversations → list of active conversations
• resource://conversations/{id} → conversation history for a session
• resource://usage/today → today's token/cost stats
• resource://usage/summary → aggregated usage overview

Technical approach:

• Implement ListResourcesRequestSchema and ReadResourceRequestSchema handlers in server.ts
• Resources are read-only projections of existing data (conversations, providers, usage stats)
• Support resource templates for parameterized URIs (e.g., conversations/{id})
• Consider resource subscriptions for live-updating data

📚 References

• MCP Resources Spec