Use Scenaro docs as context for AI coding assistants — the same pattern used by LiveKit, Retell, and Vapi.
Scenaro’s SDK abstracts its realtime engine behind a Transport boundary — LiveKit is the current implementation. Generated code should prefer the portable useScenaroSession contract over engine-specific APIs unless the task explicitly needs Transport extensions.
ResourceURL
Documentation indexhttps://docs.scenaro.io/llms.txt
Full documentationhttps://docs.scenaro.io/llms-full.txt
MCP serverhttps://docs.scenaro.io/mcp
Markdown exportAppend .md to any page URL

​
Instructions for AI agents

Fetch the complete documentation index at: https://docs.scenaro.io/llms.txt Use this file to discover all available pages before exploring further. For clean Markdown of any page, append .md to the page URL. For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.scenaro.io/mcp

​
Install the Scenaro skill

Install Scenaro documentation for your AI assistant

Open in Cursor

​
Contextual menu

Every documentation page includes a contextual menu (top-right) with:
  • Copy page — copies the current page as Markdown
  • View as Markdown — opens the .md version
  • Open in ChatGPT / Claude / Cursor — starts a conversation with page context
  • MCP — copies the MCP server URL
Press Cmd+C (Mac) or Ctrl+C (Windows) on any page to copy it as Markdown.

​
Cursor setup

1

Add MCP server

In Cursor Settings → MCP, add the Scenaro docs server:
Or use the contextual menu Cursor option on any page.
2

Use llms.txt for broad context

Paste https://docs.scenaro.io/llms.txt when you need the agent to discover all pages before drilling into specifics.
3

Use llms-full.txt for deep tasks

For large implementation tasks (full SDK integration, protocol work), provide https://docs.scenaro.io/llms-full.txt as a single context file.
When implementing a Scenaro integration, read these pages in order:
  1. Implement an experience — full journey map
  2. Quickstart — minimal working embed
  3. Tools and features — session tools vs FeatureProvider
  4. Authentication — identify → session flow
  5. Protocol topics — data-channel contract
  6. SDK reference — useScenaroSession API
  7. Transport — only if the task touches engine-specific code

​
Key facts for code generation

  • Package: @scenaro/sdk@0.3.0 on npm
  • Legacy APIs (useScenarioSession, AgentListener, getScenario) were removed in 0.3.0
  • Auth is two-hop: identifyUser then startSession — never a single token call
  • Transport is abstracted (LiveKit today) — see Transport. Only install livekit-client >=2.0.0 and @livekit/components-react >=2.0.0 for Transport extensions
  • Storage keys: scenaro_session:app:{applicationId} + scenaro_scenario_uuid
  • Business features are not in the SDK — inject via FeatureProvider registry
  • Protocol source of truth: packages/sdk/src/protocol/ in the monorepo

​
Scenaro repositories

RepoPurpose
scenaro/projectsMonorepo — @scenaro/sdk, experiences
scenaro/platform-apiPublic and admin HTTP API
scenaro/voice-agentPython voice agent (LiveKit Agents today)
scenaro/platform-spaCockpit and embed SPA