forge-mcp-resource

What problem does it solve?

It prevents AI agents from using MCP resources incorrectly by clarifying when content should be exposed as addressable, side-effect-free resources instead of tools.

Core Features & Use Cases

• Resource-vs-tool boundary: Enforces the model’s mental model where resources are nouns the agent reads and tools are verbs the agent calls.
• URI and listing correctness: Specifies stable, hierarchical, case-consistent URI schemes and requires deterministic, paginated resources/list with description and mimeType on every entry.
• Safe read semantics and binary handling: Requires idempotent, side-effect-free resources/read, supports ranged reads, and mandates using the protocol’s binary blob field instead of base64-in-text.
• Mutability and scoping guidance: Defines how mutable resources must implement subscribe plus caching metadata (lastModified, etag), and how resources must be scoped to the authenticated identity.
• Use case: When building an MCP server for a knowledge base or document store, expose documents as resources and use tools only for searches and actions.

Quick Start

Ask your MCP server design question as: "Design the MCP resources surface for my knowledge base, including URI scheme, paginated resources/list, resources/read (with mimeType and optional ranged reads), and tenancy scoping, and tell me what must be a tool instead."