Studio in Claude Desktop: the local MCP server

Praeko Studio is normally operated by an agent with a terminal. @praeko/studio-mcp is an MCP server that runs on your machine and exposes the same steps as tools, so an agent without a terminal (Claude Desktop, for example) can create the episode, write the script, make the voice, render, make the cover and upload the video to Praeko. It runs the Studio CLI underneath, over stdio: no port is opened.

Two servers, two roles

The names do not collide: the client prefixes each tool with the server name. You can keep both on at the same time.

The flow without a terminal

Install

Create the project once (npx @praeko/studio init my-channel: the command ends by printing the two install lines of this server with the right folder). Then point the server at the project folder, the one with brand.json; use the absolute path.

claude mcp add praeko-studio -- npx -y @praeko/studio-mcp --project <folder>

{
  "command": "npx",
  "args": [
    "-y",
    "@praeko/studio-mcp",
    "--project",
    "<folder>"
  ]
}

One block per client

The formats below were checked on the vendors' pages on 08/11/2026; where that was not possible, the page says so.

Claude Code

One command registers the server (the -- separates Claude's own options from the server command). By default it is saved for you only, in this project; --scope user applies to every project.

claude mcp add praeko-studio -- npx -y @praeko/studio-mcp --project <folder>

{
  "mcpServers": {
    "praeko-studio": {
      "command": "npx",
      "args": [
        "-y",
        "@praeko/studio-mcp",
        "--project",
        "<folder>"
      ]
    }
  }
}

Claude Desktop

In Settings, Developer tab, click Edit Config. The file is ~/Library/Application Support/Claude/claude_desktop_config.json (macOS), %APPDATA%\Claude\claude_desktop_config.json (Windows) or ~/.config/Claude/claude_desktop_config.json (Linux). Paste the block, quit Claude Desktop completely and open it again. Use the absolute path of the folder.

{
  "mcpServers": {
    "praeko-studio": {
      "command": "npx",
      "args": [
        "-y",
        "@praeko/studio-mcp",
        "--project",
        "<folder>"
      ]
    }
  }
}

Cursor

In the project's .cursor/mcp.json, or in ~/.cursor/mcp.json for every project. A local server takes type: stdio.

{
  "mcpServers": {
    "praeko-studio": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@praeko/studio-mcp",
        "--project",
        "<folder>"
      ]
    }
  }
}

Codex

One command (the -- separates the server command) or the [mcp_servers.<name>] table in ~/.codex/config.toml (or .codex/config.toml of a trusted project).

codex mcp add praeko-studio -- npx -y @praeko/studio-mcp --project <folder>

[mcp_servers.praeko-studio]
command = "npx"
args = ["-y","@praeko/studio-mcp","--project","<folder>"]

Gemini CLI

In the project's .gemini/settings.json, or in ~/.gemini/settings.json for every project.

{
  "mcpServers": {
    "praeko-studio": {
      "command": "npx",
      "args": [
        "-y",
        "@praeko/studio-mcp",
        "--project",
        "<folder>"
      ]
    }
  }
}

opencode

In opencode.json (or opencode.jsonc); a local server uses type: local and the whole command as a list.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "servers": {
      "praeko-studio": {
        "type": "local",
        "command": [
          "npx",
          "-y",
          "@praeko/studio-mcp",
          "--project",
          "<folder>"
        ]
      }
    }
  }
}

Other client (generic)

Any client that runs a local MCP server over stdio takes the same trio: command, arguments and (if needed) environment variables. Field names vary by client: check the client's documentation.

{
  "mcpServers": {
    "praeko-studio": {
      "command": "npx",
      "args": [
        "-y",
        "@praeko/studio-mcp",
        "--project",
        "<folder>"
      ]
    }
  }
}

command: npx
args:    ["-y","@praeko/studio-mcp","--project","<folder>"]
server:  stdio (no port, no URL)

The 14 tools

Safety

Troubleshooting