Connect Cursor

One command if you have the Daslab CLI, or a claude mcp add line if you don't.

With the Daslab CLI — writes the MCP entry and the /daslab skill:

daslab install claude

Or add it by hand:

claude mcp add --scope user --transport http daslab https://daslab.run/mcp \
  --header "Authorization: Bearer dk_xxxxxxxxxxxx"

claude mcp list

Pin one world/scene instead of all of them:

claude mcp add --scope user --transport http daslab-acme https://daslab.run/mcp/acme/q4-launch \
  --header "Authorization: Bearer dk_xxxxxxxxxxxx"

Bare /mcp gives Claude Code every world you can access, and it switches scenes with daslab_use_scene. Adding /acme/q4-launch pins it to one.

The terminal client: call tools, run agent turns, and install the other clients from one place.

macOS and Linux. Installs to ~/.local/bin/daslab:

curl -fsSL https://releases.daslab.dev/install.sh | sh

Sign in — or set a key for scripts and CI:

daslab login

# or, scriptable
export DASLAB_API_KEY=dk_xxxxxxxxxxxx

Find your way around:

daslab docs        # the full surface, LLM-readable
daslab tools       # every tool in the current scope
daslab ask "..."   # one agent turn

Full command reference below, and at daslab.run/docs/cli.md for LLM clients.

Discover what you have

# 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 world
• daslab 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 scope
• daslab call <tool> k=vInvoke one tool directly
• daslab ask "…"Run a full agent turn
• daslab chatInteractive REPL
• daslab docsPrint the full docs
• daslab --helpAll commands

Cursor reads MCP servers from mcp.json — global or per project.

~/.cursor/mcp.json for every project, or .cursor/mcp.json for one:

{
  "mcpServers": {
    "daslab": {
      "url": "https://daslab.run/mcp",
      "headers": {
        "Authorization": "Bearer dk_xxxxxxxxxxxx"
      }
    }
  }
}

1. 1Create the file above (Cursor also opens it from Settings -> MCP -> Add).
2. 2Reopen Settings -> MCP and check that daslab shows up with a green dot.
3. 3In a chat, the Daslab tools are now available to the agent.

Remote servers in Cursor take url with no type field. To pin one scene, use /mcp/acme/q4-launch as the URL.

opencode takes remote MCP servers in its JSON config.

~/.config/opencode/opencode.json — or opencode.json in a project root:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "daslab": {
      "type": "remote",
      "url": "https://daslab.run/mcp",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer dk_xxxxxxxxxxxx"
      }
    }
  }
}

Check that opencode picked it up:

opencode mcp list

A project opencode.json overrides the global one, so a repo can pin its own scene: /mcp/acme/q4-launch.

The ChatGPT desktop app, Codex CLI, and Codex IDE extension share one MCP config and one login.

Add Daslab as a Streamable HTTP server:

codex mcp add daslab --url https://daslab.run/mcp

Then sign in through the browser:

codex mcp login daslab

1. 1Run the add command once.
2. 2Run the login command, sign into Daslab in the browser, approve access.
3. 3Restart Codex, open a task, and type /mcp to confirm Daslab is connected.

Prefer the UI? Settings -> MCP servers -> Add server, choose Streamable HTTP, paste the URL, save, authenticate, restart.

Use Claude's custom connector flow — not the claude mcp add command, which is Claude Code only.

The connector URL:

https://daslab.run/mcp

1. 1In Claude, open Customize -> Connectors, click +, choose Add custom connector, paste the URL.
2. 2Click Connect, sign into Daslab, approve access.
3. 3In a conversation, enable Daslab from + -> Connectors.

On Team or Enterprise plans an Owner adds the connector from organization settings. Leave the advanced OAuth client fields blank unless your workspace has a dedicated OAuth client.

If your workspace exposes custom MCP connectors, add Daslab as a remote connector.

The connector URL:

https://daslab.run/mcp

Daslab advertises hosted MCP OAuth at that endpoint, so the client should open Daslab sign-in and store a connector token. If yours asks for JSON or static headers instead, use Any MCP client.

The generic shape for Cline, Windsurf, and anything else that accepts MCP server JSON with static headers.

{
  "mcpServers": {
    "daslab": {
      "type": "http",
      "url": "https://daslab.run/mcp",
      "headers": {
        "Authorization": "Bearer dk_xxxxxxxxxxxx"
      }
    }
  }
}

World/scene endpoints use the same shape with a readable path: https://daslab.run/mcp/acme/q4-launch.