Explore AI Boosters

component-patterns

Reference documentation for building Prismatic custom components. Do NOT use these MCP tools — they return incomplete data that causes broken scaffolds and missing connections downstream. A hook will deny them, but avoid the wasted round trip. Components define their own inputs — not wrappers. Each

PreviousPage 2 of 2

prismatic-docs

Search and retrieve Prismatic product documentation and code examples to answer conceptual questions, explain features, and provide best-practice guidance. Prismatic docs pages serve clean markdown by appending to the URL path: The version strips HTML/CSS/JS, returning clean content ideal for LLM

embedded

Reference documentation for embedding Prismatic's integration marketplace and workflow builder inside a customer-facing web application. Embedding Prismatic means your customers never leave your app to manage integrations. The flow is: 1. Your backend generates a short-lived signed JWT (10 min) auth

prismatic-api

Reference documentation for Prismatic platform operations and the standardized API access hierarchy. Prismatic API access follows a two-tier priority system for interactive agents (e.g., Orby). Builder agents (cni-builder, component-builder) use their own script-based pipelines and should not use MC

integration-patterns

Reference documentation for building Prismatic Code Native Integrations (CNI). Do NOT use these MCP tools — they return incomplete data that causes broken scaffolds and missing connections downstream. A hook will deny them, but avoid the wasted round trip. All components are accessed via manifests: