DaVinci Resolve MCP Server

# Slash commands > Control Claude's behavior during an interactive session with slash commands. ## Built-in slash commands | Command | Purpose | | :------------------------ | :----------------------------------------------------------------------------- | | `/add-dir` | Add additional working directories | | `/agents` | Manage custom AI subagents for specialized tasks | | `/bug` | Report bugs (sends conversation to Anthropic) | | `/clear` | Clear conversation history | | `/compact [instructions]` | Compact conversation with optional focus instructions | | `/config` | View/modify configuration | | `/cost` | Show token usage statistics | | `/doctor` | Checks the health of your Claude Code installation | | `/help` | Get usage help | | `/init` | Initialize project with CLAUDE.md guide | | `/login` | Switch Anthropic accounts | | `/logout` | Sign out from your Anthropic account | | `/mcp` | Manage MCP server connections and OAuth authentication | | `/memory` | Edit CLAUDE.md memory files | | `/model` | Select or change the AI model | | `/permissions` | View or update [permissions](/en/docs/claude-code/iam#configuring-permissions) | | `/pr_comments` | View pull request comments | | `/review` | Request code review | | `/status` | View account and system statuses | | `/terminal-setup` | Install Shift+Enter key binding for newlines (iTerm2 and VSCode only) | | `/vim` | Enter vim mode for alternating insert and command modes | ## Custom slash commands Custom slash commands allow you to define frequently-used prompts as Markdown files that Claude Code can execute. Commands are organized by scope (project-specific or personal) and support namespacing through directory structures. ### Syntax ``` /<command-name> [arguments] ``` #### Parameters | Parameter | Description | | :--------------- | :---------------------------------------------------------------- | | `<command-name>` | Name derived from the Markdown filename (without `.md` extension) | | `[arguments]` | Optional arguments passed to the command | ### Command types #### Project commands Commands stored in your repository and shared with your team. When listed in `/help`, these commands show "(project)" after their description. **Location**: `.claude/commands/` In the following example, we create the `/optimize` command: ```bash # Create a project command mkdir -p .claude/commands echo "Analyze this code for performance issues and suggest optimizations:" > .claude/commands/optimize.md ``` #### Personal commands Commands available across all your projects. When listed in `/help`, these commands show "(user)" after their description. **Location**: `~/.claude/commands/` In the following example, we create the `/security-review` command: ```bash # Create a personal command mkdir -p ~/.claude/commands echo "Review this code for security vulnerabilities:" > ~/.claude/commands/security-review.md ``` ### Features #### Namespacing Organize commands in subdirectories. The subdirectories determine the command's full name. The description will show whether the command comes from the project directory (`.claude/commands`) or the user-level directory (`~/.claude/commands`). Conflicts between user and project level commands are not supported. Otherwise, multiple commands with the same base file name can coexist. For example, a file at `.claude/commands/frontend/component.md` creates the command `/frontend:component` with description showing "(project)". Meanwhile, a file at `~/.claude/commands/component.md` creates the command `/component` with description showing "(user)". #### Arguments Pass dynamic values to commands using the `$ARGUMENTS` placeholder. For example: ```bash # Command definition echo 'Fix issue #$ARGUMENTS following our coding standards' > .claude/commands/fix-issue.md # Usage > /fix-issue 123 ``` #### Bash command execution Execute bash commands before the slash command runs using the `!` prefix. The output is included in the command context. You *must* include `allowed-tools` with the `Bash` tool, but you can choose the specific bash commands to allow. For example: ```markdown --- allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*) description: Create a git commit --- ## Context - Current git status: !`git status` - Current git diff (staged and unstaged changes): !`git diff HEAD` - Current branch: !`git branch --show-current` - Recent commits: !`git log --oneline -10` ## Your task Based on the above changes, create a single git commit. ``` #### File references Include file contents in commands using the `@` prefix to [reference files](/en/docs/claude-code/common-workflows#reference-files-and-directories). For example: ```markdown # Reference a specific file Review the implementation in @src/utils/helpers.js # Reference multiple files Compare @src/old-version.js with @src/new-version.js ``` #### Thinking mode Slash commands can trigger extended thinking by including [extended thinking keywords](/en/docs/claude-code/common-workflows#use-extended-thinking). ### Frontmatter Command files support frontmatter, useful for specifying metadata about the command: \| Frontmatter | Purpose | Default | \| :-------------- | :--------------------------------------------------------------------------------- | :---------------------------------- | ----------------------------------------------------------------------------- | ---- | \| `allowed-tools` | List of tools the command can use | Inherits from the conversation | \| `argument-hint` | The arguments expected for the slash command. Example: `argument-hint: add [tagId] | remove [tagId] | list`. This hint is shown to the user when auto-completing the slash command. | None | \| `description` | Brief description of the command | Uses the first line from the prompt | \| `model` | `opus`, `sonnet`, `haiku`, or a specific model string | Inherits from the conversation | For example: ```markdown --- allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*) argument-hint: [message] description: Create a git commit model: haiku --- An example command ``` ## MCP slash commands MCP servers can expose prompts as slash commands that become available in Claude Code. These commands are dynamically discovered from connected MCP servers. ### Command format MCP commands follow the pattern: ``` /mcp__<server-name>__<prompt-name> [arguments] ``` ### Features #### Dynamic discovery MCP commands are automatically available when: * An MCP server is connected and active * The server exposes prompts through the MCP protocol * The prompts are successfully retrieved during connection #### Arguments MCP prompts can accept arguments defined by the server: ``` # Without arguments > /mcp__github__list_prs # With arguments > /mcp__github__pr_review 456 > /mcp__jira__create_issue "Bug title" high ``` #### Naming conventions * Server and prompt names are normalized * Spaces and special characters become underscores * Names are lowercased for consistency ### Managing MCP connections Use the `/mcp` command to: * View all configured MCP servers * Check connection status * Authenticate with OAuth-enabled servers * Clear authentication tokens * View available tools and prompts from each server ## See also * [Interactive mode](/en/docs/claude-code/interactive-mode) - Shortcuts, input modes, and interactive features * [CLI reference](/en/docs/claude-code/cli-reference) - Command-line flags and options * [Settings](/en/docs/claude-code/settings) - Configuration options * [Memory management](/en/docs/claude-code/memory) - Managing Claude's memory across sessions