Install
$ agentstack add mcp-saharmor-auggie-mcp ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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 (AUGMENTAPITOKEN)
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
envfor 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
stdiomode.
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:
implementruns 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.
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: saharmor
- Source: saharmor/auggie-mcp
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.