MCP Quickstart

early access

One plugin install gets you the AudioScape MCP server, browser sign-in with a short code, and self-updating audio skills. Your AI assistant guides the rest.

Early access: anyone can install the plugin (the agent-skills repo is public), but approving sign-in at /activate requires an enrolled account — contact the AudioScape team for an invite.

Prerequisites

Claude Code v2.1.195 or later
Roblox Studio installed (latest version — the Studio MCP server is built in)
A Roblox account

Step 1 — Prepare your terminal

Install Claude Code if you haven't, and make sure the skills folder exists before it starts so the AudioScape skills load without a restart.

macOS / Linux

curl -fsSL https://claude.ai/install.sh | bash
mkdir -p ~/.claude/skills
claude

Windows (PowerShell)

irm https://claude.ai/install.ps1 | iex
New-Item -ItemType Directory -Force "$env:USERPROFILE\.claude\skills" | Out-Null
claude

Step 2 — Install the plugin and sign in

Inside Claude Code, run these three commands. Sign-in shows you a short code to enter at developer.audioscape.ai/activate in your browser — nothing to copy out of the terminal, and it works over SSH.

Claude Code

/plugin marketplace add AudioScapeInc/agent-skills
/plugin install audioscape@audioscape
/audioscape:login

Step 3 — Paste the setup prompt

Copy the whole block below and paste it into Claude Code.

Setup prompt

You are setting me up with the AudioScape skills for Claude Code (early access). Work through the phases below in order, one at a time. Before each phase, check whether it is already done and skip it if so — I may have pasted this prompt before; resume where things left off instead of repeating completed work. When a step needs something only I can do, ask me one question at a time and wait for my answer. Never ask me to paste an API key or any other secret into this chat — all key handling happens in my browser.

Phase 1 — Connect. Confirm the "audioscape" MCP server is connected and authenticated by calling its validate_setup tool. If it reports an auth error, run the /audioscape:login command from the AudioScape plugin: it shows me a short code to enter at developer.audioscape.ai/activate in my browser (sign-in with my Roblox account; a scoped API key is provisioned automatically when I approve). Never open OAuth URLs via shell commands.
Phase 2 — Runbook. Read the MCP resource audioscape://docs/quickstart-runbook and follow it for everything below.
Phase 3 — Skills. The plugin installs and updates the AudioScape skills automatically (its kit-sync hook runs at session start and before every audio-* skill). Confirm ~/.claude/skills/audioscape-quickstart/KIT_VERSION exists; if it does not, tell me to restart Claude Code so the hook runs, then resume from here.
Phase 4 — Studio. Connect Studio's built-in MCP server, following the runbook. Once it is configured, tell me to restart Claude Code and paste this same prompt again — you will resume from here.
Phase 5 — Verify. Run the runbook's verification with my test place open in Roblox Studio: validate_setup, then verify_studio_setup for Catalog SDK/HttpService/Secret setup, then verify_mixer_setup for the Mixer SDK at ReplicatedStorage.AudioScape.AudioScape. If verify_mixer_setup reports missing or outdated, ask my permission, call get_mixer_sdk, apply the returned installer via the Roblox Studio MCP, then rerun verify_mixer_setup. Finish with the audible check, which I confirm by ear.
Phase 6 — Hand-off. Interview me briefly per the runbook and submit my onboarding report with submit_feedback. Then suggest the first guided session.

Step 4 — What happens next

Your assistant verifies the connection, sets up the Roblox Studio side — expect exactly one Claude Code restart; paste the same prompt again and it resumes — verifies everything end to end, and offers a first guided session. Takes about 15 minutes.

Good to know

Where the skills live — ~/.claude/skills/
Updating — automatic. The plugin checks for a new skills kit at session start and before every AudioScape skill runs; previous versions are kept as *.bak.
Signing in again later — /audioscape:login any time a tool reports an auth error.
Giving feedback — just tell Claude; it submits it for you.