Daslab CLI
Install the CLI, authenticate from the terminal, and teach Claude Code to work with your Daslab scenes.
Using Claude, Claude Cowork, ChatGPT, Cursor, or another MCP client?
MCP connector setup
Set up
Install the CLI
curl -fsSL https://releases.daslab.dev/install.sh | sh
macOS & Linux. Installs to ~/.local/bin/daslab.
daslab login # or, scriptable export DASLAB_API_KEY=dk_xxxxxxxxxxxx
daslab install claude
daslab install claude writes the MCP entry and installs the Claude Code /daslab skill. For static-header setup, get a key from Account → API key.
Connect Claude Code
Use /mcp for all worlds you can access. Add /acme/q4-launch after /mcp to pin one readable world/scene URL.
claude mcp add --scope user --transport http daslab https://daslab.run/mcp \ --header "Authorization: Bearer dk_xxxxxxxxxxxx" claude mcp list
claude mcp add --scope user --transport http daslab-acme https://daslab.run/mcp/acme/q4-launch \ --header "Authorization: Bearer dk_xxxxxxxxxxxx"
Use a Daslab API key that starts with dk_. Get one from Account → API key.
Discover what you have
Three steps to orient yourself in a scene:
# 1. list scenes in your home world daslab --world call daslab_list_scenes # 2. paste an id, see what's inside SCENE=<paste-id-from-step-1> daslab --scene-id $SCENE call daslab_get_scene_assets scene_id=$SCENE # 3. list every tool that scene exposes (usually 100+) daslab --scene-id $SCENE tools
Switch worlds & scenes
daslab world use <world>Persistent switch to another worlddaslab scenes use <scene>Persistent switch to another scene--scene-id <id>One-shot override on any command--worldOne-shot — your home world
Quick reference
daslab toolsList MCP tools in the current scopedaslab call <tool> k=vInvoke one tool directlydaslab ask "…"Run a full agent turndaslab chatInteractive REPLdaslab docsPrint the full docsdaslab --helpAll commands
Full LLM-readable docs at
daslab.run/cli.md
·
Source on GitHub.