Getting Started
Scenario MCP gives AI agents — Claude, Cursor, VS Code, or any MCP-compatible client — full access to the Scenario creative AI platform. 22 tools covering image, video, 3D, and audio generation across 550+ models (+ your own), with an intelligence layer that handles model selection, parameter discovery, and prompt enhancement automatically.
Prerequisites
- Scenario account — Sign up at app.scenario.com
- API credentials (API key auth) — app.scenario.com/team
- MCP-compatible client — Claude Code, Cursor, VS Code, Windsurf, Claude Desktop, and more
Installation
Connect the Scenario MCP server to your preferred MCP-compatible client. OAuth is the recommended method — it handles authentication automatically on first use.
Multiple teams or projects
As a reminder, teams are shared workspaces for members, projects organize the assets and work inside that team. Please see Teams (also labeled as "Organizations") and Projects for more information.
If your Scenario account has access to multiple teams or projects, the Scenario MCP won't assume a default context. Instead, it instructs your AI agent to ask you which team and project to use.
- If multiple teams or projects are available, your agent should ask which workspace to use.
- Once selected, the agent can reuse that team and project context for later tool calls that need it.
- If your client does not prompt automatically, ask your agent to list your teams and projects, then choose one explicitly.
Client-specific instructions
Claude Code
claude mcp add --transport http scenario https://mcp.scenario.com/mcpOAuth authentication triggers automatically. Authenticate manually via /mcp if needed.
Claude Desktop
Open Settings → Developer → Edit Config and add this config to your claude_desktop_config.json file:
{
"mcpServers": {
"scenario": {
"url": "https://mcp.scenario.com/mcp"
}
}
}Native Streamable HTTP + OAuth — no mcp-remote bridge required.
Quit and restart Claude Desktop so the MCP configuration is loaded. OAuth triggers automatically on first use.
Claude.ai
Open claude.ai → Settings → Connectors → Add custom connector, and paste:
https://mcp.scenario.com/mcpComplete OAuth in the browser. Custom Connectors are available on paid plans (Pro / Max / Team / Enterprise) — free plan users can use Claude Desktop or Claude Code instead.
Cursor
Cursor 1.0+ supports native OAuth and Streamable HTTP. Open Settings → MCP and add:
{
"mcpServers": {
"scenario": {
"url": "https://mcp.scenario.com/mcp"
}
}
}OAuth triggers on first use.
VS Code
Press Cmd+Shift+P, type MCP: Add Server, select HTTP, and enter the URL. Or add to your settings:
{
"mcpServers": {
"scenario": {
"type": "http",
"url": "https://mcp.scenario.com/mcp"
}
}
}Activate via MCP: List Servers if not auto-enabled.
Windsurf
Open Cascade (Cmd+L) → Configure MCP and add:
{
"mcpServers": {
"scenario": {
"url": "https://mcp.scenario.com/mcp"
}
}
}OAuth triggers on first use.
Zed
Open settings (Cmd+,) and add:
{
"context_servers": {
"scenario": {
"url": "https://mcp.scenario.com/mcp"
}
}
}Zed prompts the OAuth flow on first use when no Authorization header is configured.
Codex
codex mcp add scenario --url https://mcp.scenario.com/mcpOAuth triggers on first use.
Gemini CLI
Edit ~/.gemini/settings.json:
{
"mcpServers": {
"scenario": {
"url": "https://mcp.scenario.com/mcp"
}
}
}Run /mcp auth scenario to authenticate.
Amp
amp mcp add scenario https://mcp.scenario.com/mcpOAuth authentication via Dynamic Client Registration.
OpenCode
Edit ~/.config/opencode/opencode.json:
{
"mcp": {
"scenario": {
"type": "remote",
"url": "https://mcp.scenario.com/mcp",
"oauth": {}
}
}
}Run opencode mcp auth scenario to authenticate.
Warp
Open Settings → AI → Manage MCP servers → + Add → JSON. Paste:
{
"scenario": {
"url": "https://mcp.scenario.com/mcp"
}
}OAuth triggers on first use.
Vercel v0
In v0.app open Account Settings → Integrations. Under MCP Connections click Add MCP and paste:
https://mcp.scenario.com/mcpComplete OAuth in the browser.
Other Clients
Any MCP client that supports OAuth and Streamable HTTP can connect directly to:
https://mcp.scenario.com/mcpFor clients that only support stdio, use npx mcp-remote@latest https://mcp.scenario.com/mcp as a bridge.
Using an API Key
If you prefer API key authentication instead of OAuth:
- Get your API key and secret from app.scenario.com
- Base64-encode your credentials:
echo -n 'KEY:SECRET' | base64 - Add the
Authorizationheader to your config
CLI clients (Claude Code, Codex)
claude mcp add --transport http scenario \
https://mcp.scenario.com/mcp \
--header "Authorization: Basic $(echo -n 'KEY:SECRET' | base64)"codex mcp add scenario --url https://mcp.scenario.com/mcp \
--header "Authorization: Basic $(echo -n 'KEY:SECRET' | base64)"URL-config clients (Cursor, VS Code, Windsurf, Gemini CLI, OpenCode)
{
"mcpServers": {
"scenario": {
"url": "https://mcp.scenario.com/mcp",
"headers": {
"Authorization": "Basic <YOUR_BASE64_ENCODED_KEY:SECRET>"
}
}
}
}Zed
{
"context_servers": {
"scenario": {
"url": "https://mcp.scenario.com/mcp",
"headers": {
"Authorization": "Basic <YOUR_BASE64_ENCODED_KEY:SECRET>"
}
}
}
}Warp
{
"scenario": {
"url": "https://mcp.scenario.com/mcp",
"headers": {
"Authorization": "Basic <YOUR_BASE64_ENCODED_KEY:SECRET>"
}
}
}Claude Desktop
Claude Desktop's native URL form does not accept custom headers, so the API key path still uses mcp-remote as a bridge:
{
"mcpServers": {
"scenario": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.scenario.com/mcp",
"--header",
"Authorization: Basic <YOUR_BASE64_ENCODED_KEY:SECRET>"
]
}
}
}Test the Connection
Try these prompts to verify everything works:
- "List my Scenario teams"
- "Show available models for image generation"
- "Generate an image of a sunset over mountains"
Having trouble? See troubleshooting.
First Steps
Once connected, try these prompts in your AI Agent:
"Generate a pixel art knight with a red cape""What's the best model for YouTube thumbnails?""Show me my recent assets"