Name: Auggie MCP

npx -y @dccxx/auggie-shell-mcp

Or

bunx @dccxx/auggie-shell-mcp

MCP Server Configuration

To use this MCP server with AI assistants like Claude Desktop or other MCP-compatible clients, you need to add it to your MCP configuration file.

Configuration Format

Add the following configuration to your MCP settings:

{
  "auggie-mcp-server": {
    "command": "bunx",
    "args": ["@dccxx/auggie-shell-mcp"],
    "env": {}
  }
}

Configuration for Claude Desktop

For Claude Desktop, add the configuration to your claude_desktop_config.json file:

Location:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/Claude/claude_desktop_config.json

Example configuration:

{
  "mcpServers": {
    "auggie-mcp-server": {
      "command": "bunx",
      "args": ["@dccxx/auggie-shell-mcp"],
      "env": {}
    }
  }
}

With environment variables (optional - to use temp directory instead of CWD):

{
  "mcpServers": {
    "auggie-mcp-server": {
      "command": "bunx",
      "args": ["@dccxx/auggie-shell-mcp"],
      "env": {
        "ALLOW_CWD_SHELL": "false"
      }
    }
  }
}

After adding the configuration, restart Claude Desktop for the changes to take effect.

Environment Variables

AUTO_FETCH_AUTH

Automatically runs auggiegw fetch --auth-only at the beginning of the generated shell script to fetch authentication credentials before executing the main Auggie command. This is useful when you need to ensure authentication is refreshed before running commands.

Behavior:

• When AUTO_FETCH_AUTH=true and the continue flag is false, the command auggiegw fetch --auth-only will be added at the start of the shell script (after changing to the working directory but before the main auggie command)
• When AUTO_FETCH_AUTH is not set or set to any value other than "true", no auth fetch command is added
• The auth fetch command is NOT added when using the --continue flag, as continuing a conversation doesn't require re-authentication

Default: Not enabled (no auth fetch command is added)

Example usage:

# Linux/macOS
export AUTO_FETCH_AUTH=true
npx -y @dccxx/auggie-shell-mcp

# Windows PowerShell
$env:AUTO_FETCH_AUTH="true"
npx -y @dccxx/auggie-shell-mcp

Example configuration in Claude Desktop:

{
  "mcpServers": {
    "auggie-mcp-server": {
      "command": "bunx",
      "args": ["@dccxx/auggie-shell-mcp"],
      "env": {
        "AUTO_FETCH_AUTH": "true"
      }
    }
  }
}

COMPACT_MODE

Controls whether the --compact flag is passed to auggie CLI commands. The compact flag affects the output format of auggie commands, making them more concise.

Behavior:

• When COMPACT_MODE is not set, the --compact flag is added to auggie commands (default behavior)
• When COMPACT_MODE is set to "false", "0", or "disable" (case-insensitive), the --compact flag is NOT added
• Any other value will keep the compact mode enabled

Default: Enabled (compact flag is added)

Example usage to disable compact mode:

# Linux/macOS
export COMPACT_MODE=false
npx -y @dccxx/auggie-shell-mcp

# Windows PowerShell
$env:COMPACT_MODE="false"
npx -y @dccxx/auggie-shell-mcp

Example configuration in Claude Desktop:

{
  "mcpServers": {
    "auggie-mcp-server": {
      "command": "bunx",
      "args": ["@dccxx/auggie-shell-mcp"],
      "env": {
        "COMPACT_MODE": "false"
      }
    }
  }
}

Alternative values to disable:

# All of these will disable compact mode
export COMPACT_MODE=false
export COMPACT_MODE=0
export COMPACT_MODE=disable
export COMPACT_MODE=DISABLE  # Case-insensitive

ALLOW_CWD_SHELL

By default, Auggie MCP creates shell scripts in the current working directory with a simple filename. If you prefer to have scripts created in the system's temporary directory with unique filenames to prevent conflicts, you can set the ALLOW_CWD_SHELL environment variable to false.

Default behavior (ALLOW_CWD_SHELL not set or set to any value other than "false"):

• Scripts are created in the current working directory
• Filename is always: auggie_shell.sh or auggie_shell.ps1

When ALLOW_CWD_SHELL=false:

• Scripts are created in the system temp directory
• Filenames use a unique identifier: auggie_shell_<random_id>.sh or auggie_shell_<random_id>.ps1

Example usage to disable CWD shell scripts:

# Linux/macOS
export ALLOW_CWD_SHELL=false
npx -y @dccxx/auggie-shell-mcp

# Windows PowerShell
$env:ALLOW_CWD_SHELL="false"
npx -y @dccxx/auggie-shell-mcp

Note: With the default behavior, the script file will be overwritten on each execution. Make sure to add auggie_shell.sh and auggie_shell.ps1 to your .gitignore file if you don't want these files tracked in version control.

AUGGIE_POWERSHELL_EXECUTABLE

Allows you to specify a custom PowerShell executable instead of the default powershell. This is useful if you want to use PowerShell Core (pwsh) or a custom shell on Windows.

Default: powershell

Example usage with PowerShell Core:

# Windows PowerShell
$env:AUGGIE_POWERSHELL_EXECUTABLE="pwsh"
npx -y @dccxx/auggie-shell-mcp

Example configuration in Claude Desktop:

{
  "mcpServers": {
    "auggie-mcp-server": {
      "command": "bunx",
      "args": ["@dccxx/auggie-shell-mcp"],
      "env": {
        "AUGGIE_POWERSHELL_EXECUTABLE": "pwsh"
      }
    }
  }
}

AUGGIE_BASH_EXECUTABLE

Allows you to specify a custom bash-compatible shell executable instead of the default bash. This is useful if you want to use zsh, fish, or other custom shells on Unix-like systems.

Default: bash

Example usage with zsh:

# Linux/macOS
export AUGGIE_BASH_EXECUTABLE=zsh
npx -y @dccxx/auggie-shell-mcp

Example configuration in Claude Desktop:

{
  "mcpServers": {
    "auggie-mcp-server": {
      "command": "bunx",
      "args": ["@dccxx/auggie-shell-mcp"],
      "env": {
        "AUGGIE_BASH_EXECUTABLE": "zsh"
      }
    }
  }
}