What would you like?
Add support for consuming MCP resources from connected servers, enabling the agent to read external data sources (files, database records, API responses) exposed by MCP servers
Motivation
The MCP protocol defines five client capabilities: tools, resources, prompts, sampling, and roots. Acolyte currently supports tools only. Resources are the natural next step — they let MCP servers expose read-only data that the agent can consume without requiring a tool call
The MCP feature support matrix shows most serious clients support resources (Claude Desktop, Cline, Roo Code, fast-agent). Adding resources brings Acolyte closer to full MCP compliance
Proposed approach
- Extend the MCP client to discover and list resources from connected servers
- Expose resources to the agent via a read-like tool or as context attachments
- Support resource templates (parameterized URIs) for dynamic resources
- Handle resource subscriptions for change notifications if the server supports them
Scope
- MCP client resource discovery and listing
- Resource read by URI
- Resource template support
- Integration with agent context (how the agent discovers and reads resources)
- Tests for resource operations
What would you like?
Add support for consuming MCP resources from connected servers, enabling the agent to read external data sources (files, database records, API responses) exposed by MCP servers
Motivation
The MCP protocol defines five client capabilities: tools, resources, prompts, sampling, and roots. Acolyte currently supports tools only. Resources are the natural next step — they let MCP servers expose read-only data that the agent can consume without requiring a tool call
The MCP feature support matrix shows most serious clients support resources (Claude Desktop, Cline, Roo Code, fast-agent). Adding resources brings Acolyte closer to full MCP compliance
Proposed approach
Scope