Resource Based Context Provisioning

via “resource-based context and knowledge management”

MCP server: agent-zero

Unique: Uses MCP's resources interface to provide agents with a standardized way to access and reference external knowledge, enabling clients to inject context and configuration without modifying agent code or tool definitions

vs others: More flexible than hardcoded knowledge because resources can be updated dynamically; more discoverable than custom APIs because resources are enumerable through MCP; more auditable than in-memory context because resource access is logged

via “static and dynamic resource exposure with provider pattern”

** – A library to build MCP servers in Golang by **[strowk](https://github.com/strowk)**

Unique: Implements provider pattern for resources, allowing dynamic computation of resource content at request time with access to client session context — enables context-aware filtering and per-client data serving without pre-computing all resource variants

vs others: More flexible than static-only resource servers; provider pattern enables runtime data fetching (e.g., database queries) without requiring separate API layers

via “resource-based context provisioning”

MCP server: catchintent

Unique: Implements MCP resource abstraction with URI-based addressing, allowing clients to fetch contextual information on-demand without embedding all data in tool parameters

vs others: More scalable than embedding all context in requests because resources are fetched on-demand, reducing token usage and enabling access to large knowledge bases

via “resource-based-context-injection”

(MCP), as well as references to community-built servers and additional resources.

Unique: Uses a pull-based resource model where clients request specific resources by URI, avoiding the need to serialize all data upfront. Supports MIME type hints and optional descriptions, enabling clients to make intelligent decisions about which resources to fetch and how to present them. Resources are decoupled from tools — a server can expose resources without exposing any callable functions.

vs others: More efficient than embedding all data in prompts because resources are fetched on-demand; more flexible than RAG systems because clients control which resources to fetch rather than relying on semantic search; more secure than uploading data to external APIs because resources stay on the server.