Auggie runs commands and tools automatically. Only use integrations and MCP servers from trusted sources, and be aware of the risks of combining multiple tools with external data sources or production systems.
About Integrations and MCP
Auggie can utilize external integrations through native integrations like GitHub, Linear, and Notion and Model Context Protocol (MCP) to access external systems for information and integrate tools to take actions. MCP is an open protocol that provides a standardized way to connect AI models to different data sources and tools.Native Integrations
You’ll need to configure the integration in Augment for VS Code or JetBrains IDEs. Once configured, the integration will be available for use with Auggie automatically. See a full list and examples for native agent integrations.1. Setup in Augment extension
- Visual Studio Code: Click the settings icon in the top right of Augment’s chat window or press Cmd/Ctrl Shift P and select Show Settings Panel
- JetBrains IDEs: Click the Augment icon in the bottom right of your JetBrains IDE and select Tool Settings
2. Connect the integration
Click “Connect” for the integration you want to set up
MCP Integrations
In addition to native integrations, Auggie can also access external systems through Model Context Protocol (MCP) servers. MCP servers enable Auggie to interact with external tools and services through a standardized protocol, such as accessing databases, running browser automation, sending messages to Slack, or integrating with APIs.Configure MCP via settings.json
You can persist MCP servers in the Augment settings file~/.augment/settings.json
, which will initialize on startup and can be checked with /mcp-status
.
Manage MCP servers with the Auggie CLI
You can add and inspect MCP servers is via Auggie subcommands, which will persist the configuration to your~/.augment/settings.json
file:
Usage
Add MCP server:--command <path>
- Executable path (for stdio transport)--args <args>
- Arguments string for command-e, --env <KEY=VAL>
- Environment variable (repeatable)-t, --transport <transport>
- stdio|sse (default: “stdio”)-u, --url <url>
- SSE URL (required for —transport sse)-r, --replace
- Overwrite existing entry without prompt--json
- Output JSON
--json
- Output JSON format
MCP overrides
You can define servers by passing ad‑hoc overrides with--mcp-config
. The structure is the same as settings.json
: