Slab5 Guide

Slab5 Guide is the customer-facing knowledge assistant for answering questions about how to use Slab5.

What it does

Guide answers product and workflow questions from approved public docs. It should help customers, developers, support agents, and workspace admins understand Slab5 modules, REST APIs, MCP tools, scopes, billing, usage, AgentGrid workflows, App Studio, and troubleshooting.

Slab5 Guide appears inside the console as a product help panel, answering setup and workflow questions from approved Slab5 documentation.

Knowledge source

Guide uses generated Markdown derived from the public docs website. The knowledge source is curated so Guide answers customer-facing product questions, not private operational or infrastructure questions.

The knowledge corpus includes getting started, concepts, REST API, MCP, modules, and customer-facing examples. It intentionally excludes private infrastructure notes, deployment details, raw secrets, and internal operational runbooks.

Where it appears

Slab5 Guide appears in the console as a floating product-help launcher and right-side drawer. The drawer uses the current console theme so light and dark mode remain consistent.

Guide is also reused inside assistant-style surfaces that need product context. App Studio uses a related ChatKit assistant pattern for app-plane setup, available tools, artifacts, conversations, and approval-gated handoffs.

MCP tool

The MCP tool is:

create_slab5_guide_session

Use it to create a Guide session tied to a workspace and retrieval context.

What you can ask

Use Guide when you want help with:

  • How do I create a contact, task, support ticket, CMS entry, asset, BI dashboard, or Data Agents artifact?
  • Which scopes are required for a REST route or MCP tool?
  • How do workspaces, modules, audit logs, usage events, billing usage, and request IDs work?
  • How do I connect ChatGPT, Claude, Cursor, or LangGraph to Slab5 MCP?
  • How should I start with AgentGrid templates, approvals, run logs, and schedules?
  • How do App Studio, registered apps, artifacts, handoffs, and workspace tool scopes fit together?

Was this page helpful?