Auggie (Augment Code)

Auggie (Augment Code)

saharmor

Integrates Augment Code's Auggie CLI to answer questions about your codebase and implement code changes through an MCP interface.

Run Augment Code as a coding agent via the Auggie CLI

11,515 views1Local (stdio)

What it does

  • Ask questions about repository code using Auggie's context engine
  • Implement code changes with dry-run mode by default
  • Query codebase through natural language
  • Generate code modifications based on descriptions

Best for

Developers wanting AI-powered code understandingCode review and exploration workflowsAutomated code implementation tasks
Requires Auggie CLI installationUses repository context for accurate responses

About Auggie (Augment Code)

Auggie (Augment Code) is a community-built MCP server published by saharmor that provides AI assistants with tools and capabilities via the Model Context Protocol. Run Augment Code with Auggie CLI—your AI powered coding assistant and AI code helper for smarter, faster coding. It is categorized under developer tools.

How to install

You can install Auggie (Augment Code) in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

License

Auggie (Augment Code) is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

Auggie MCP Server

Minimal MCP server exposing Auggie CLI as tools for Q&A and code implementation.

Tools

  • ask_question: Repository Q&A via Auggie’s context engine.
  • implement: Implement a change in the repo; dry-run by default.

Requirements

  • Node.js 18+
  • Python 3.10+ available on the system (used internally; no manual setup needed)
  • Auggie CLI installed (check by running auggie --version) - see installation guide

Authentication (AUGMENT_API_TOKEN)

Retrieve your token via the Auggie CLI:

# Ensure Auggie CLI is installed and on PATH
auggie --version

# Sign in (opens browser flow)
auggie login

# Print your token
auggie --print-augment-token

Provide the token in either of these ways:

  • Cursor/Claude config (recommended): set it under env for the server
{
  "mcpServers": {
    "auggie-mcp": {
      "command": "npx",
      "args": ["-y", "auggie-mcp@latest"],
      "env": { "AUGMENT_API_TOKEN": "YOUR_TOKEN" }
    }
  }
}
  • Shell environment (macOS/Linux)

One-off for a single command:

AUGMENT_API_TOKEN=YOUR_TOKEN npx -y auggie-mcp --setup-only

Persist for future shells (zsh):

echo 'export AUGMENT_API_TOKEN=YOUR_TOKEN' >> ~/.zshrc
source ~/.zshrc

Security tip: never commit tokens to source control. Prefer per-machine environment variables or your client's secure config store.

Configure Clients

Cursor via npx

Use this MCP config in Cursor (global or per-project):

{
  "mcpServers": {
    "auggie-mcp": {
      "command": "npx",
      "args": ["-y", "auggie-mcp@latest"],
      "env": { "AUGMENT_API_TOKEN": "YOUR_TOKEN" }
    }
  }
}

This will:

  • download the wrapper package,
  • create a local Python venv inside the package,
  • install requirements.txt, and
  • launch the Python server in stdio mode.

Quick test via npx (terminal)

# Install deps into the package's local venv (no global installs)
npx -y auggie-mcp --setup-only

# Run the server (stdio). Useful for quick smoke-tests.
npx -y auggie-mcp

# Optional: start HTTP mode for manual debugging
npx -y auggie-mcp -- --http

Claude Desktop (macOS)

Edit ~/Library/Application Support/Claude/claude_desktop_config.json and add:

{
  "mcpServers": {
    "auggie-mcp": {
      "command": "npx",
      "args": ["-y", "auggie-mcp@latest"],
      "env": { "AUGMENT_API_TOKEN": "YOUR_TOKEN" }
    }
  }
}

Security and permissions

  • Default: implement runs in dry‑run mode. No files are written, no shell runs; you get a proposed diff.
  • Enable writes: set dry_run: false.
  • Recommendation: use a feature branch and review the diff before merging.

Alternatives

Related Skills

Browse all skills
godot

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

732
finance-skills

Production-ready financial analyst skill with ratio analysis, DCF valuation, budget variance analysis, and rolling forecast construction. 4 Python tools (all stdlib-only). Works with Claude Code, Codex CLI, and OpenClaw.

55
python-expert

Senior Python developer expertise for writing clean, efficient, and well-documented code. Use when: writing Python code, optimizing Python scripts, reviewing Python code for best practices, debugging Python issues, implementing type hints, or when user mentions Python, PEP 8, or needs help with Python data structures and algorithms.

40
ui-design-system

UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.

18
elegant-design

Create world-class, accessible, responsive interfaces with sophisticated interactive elements including chat, terminals, code display, and streaming content. Use when building user interfaces that need professional polish and developer-focused features.

17
code-review-excellence

Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.

13