Auggie

You can run the Auggie MCP Server locally to expose Auggie CLI tools as MCP endpoints. This server lets you answer questions via a context engine and implement changes in your repository, with a secure, token-based authentication flow. It leverages Node.js and Python environments under the hood and is designed to be easy to integrate with common MCP clients.

How to use

Use the MCP server with your MCP client to access Auggie’s Q&A and code-implementation tools. The server wraps the Auggie CLI tools so you can run repository knowledge queries and perform code changes through a consistent, automated interface. You’ll configure an MCP client to connect to the server, provide authentication tokens, and then execute the available tools as normal MCP operations.

How to install

Prerequisites you must have installed on your system before starting the server.

• Ensure Node.js is available by running node -v and you should see a version that starts with 18 or higher.

• Check Python with python3 --version to confirm it is 3.10 or newer. No manual setup is required beyond having Python available.

• Verify by running auggie --version. If needed, follow the Auggie CLI installation steps you typically use for your environment.

Security and authentication

This server requires an authentication token to access Auggie’s API. Retrieve your token through the Auggie CLI and supply it to the MCP client configuration.

Configure your MCP client

Cursor via npx is a straightforward way to connect the MCP client to the Auggie MCP Server. Use the following configuration to download the wrapper package, create a local Python venv, install dependencies, and run the server in stdio mode.

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

Quick test via npx (terminal)

Run a quick smoke-test to ensure the server starts in stdio mode and is reachable.

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

# Run the server (stdio). This starts the server for immediate testing
npx -y auggie-mcp

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

Security and permissions details

• Default: implement runs in dry-run mode. No files are written, no shell runs; you get a proposed diff. - Enable writes: set dry_run to false in your configuration. - Use a feature branch and review the diff before applying changes.

Notes and tips

• Never share your AUGMENT_API_TOKEN publicly and avoid committing tokens to source control. - Keep tokens in your secure client config store or per-machine environment variables. - The server requires the Auggie CLI to be installed and reachable on the host where the MCP server runs.

Available tools

ask_question

Query the Auggie context engine to get repository Q&A responses.

implement

Apply a change to the repository; runs in a dry-run by default and can be enabled to write changes.