MCPlet

What is MCPlet?

MCPlet is a constrained, single-intent capability unit built on Model Context Protocol. Each MCPlet packages one business intent, explicit safety boundaries, and optional UI so hosts can expose AI tools in a predictable, reviewable, and secure way. ◈ Single Intent Each MCPlet represents exactly one business intent. No ambiguity, no complexity—just focused, purposeful capability.

What are the three MCPlet types?

MCPlet classifies tools as read, prepare, or action. Read tools are safe and idempotent, prepare tools stage or validate inputs before commitment, and action tools cause side effects and therefore require stronger confirmation and enforcement. read Query & Search Safe, idempotent operations for data retrieval with no side effects.

How does MCPlet handle authentication?

Protected MCPlets declare authentication in code-first `_meta.auth` metadata. For model-visible actions, the host intercepts the call, obtains a Passkey assertion, and the backend verifies it before the business action runs.

How does MCPlet architecture work?

MCPlet sits between an AI-capable host and an MCP server. The host manages state, policy, and orchestration, while each MCPlet keeps one intent, explicit metadata, and a clear execution path for UI or agent-driven flows.

What design principles define MCPlet?

MCPlet is designed to make AI operations predictable: one intent per unit, stateless execution, explicit visibility, progressive enhancement, and security controls that keep side effects reviewable. 01 Single Intent Each MCPlet does one thing well. No Swiss Army knives—just focused, purposeful capability.