​
About Model Context Protocol servers

Augment Agent can utilize external integrations through 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. MCP servers can be used to access local or remote databases, run automated browser testing, send messages to Slack, or even play music on Spotify.

​
Easy MCP: One-Click Integrations

New: Easy MCP launched on July 30, 2025, making it easier than ever to connect popular developer tools to Augment Code.
Easy MCP is a new feature in the Augment Code extension that transforms complex MCP server setup into a single click. Instead of manually configuring servers, hunting for GitHub repos, or editing JSON files, you can now connect popular developer tools with just an API token or OAuth approval.

​
Available Easy MCP Integrations

Easy MCP provides one-click access to these popular developer tools:

​
CircleCI

  • Context: Build logs, test insights, flaky-test detection
  • Sample prompt: “Find the latest failed pipeline on my branch and surface the failing tests.”
  • Setup: Click ”+”, paste your CircleCI API token, and you’re connected.

​
MongoDB

  • Context: Data exploration, database management, and context-aware code generation
  • Sample prompt: “Analyze my user collection schema and suggest optimizations for our new search feature.”
  • Setup: One-click OAuth connection to your MongoDB instance.

​
Redis

  • Context: Keyspace introspection, TTL audits, and migration helpers
  • Sample prompt: “Generate a migration script to move expiring session keys to the new namespace.”
  • Setup: Connect with your Redis credentials in seconds.

​
Honeycomb

  • Context: Ingest traces, spans, and query results for instant observability in your coding loop
  • Sample prompt: “Show me recent slow traces in production and suggest where to add instrumentation.”
  • Setup: Click Connect under Honeycomb, complete OAuth sign-in and grant required scopes, select organization/environment (if prompted), verify connection by running a quick query from within the IDE.

​
Heroku

  • Context: Pull dyno statuses, release histories, and live logs into your IDE
  • Sample prompt: “Show the most recent release for staging and highlight any errors in the logs.”
  • Setup: Ensure Heroku CLI is installed and you’re logged in locally, click Connect under Heroku, select the app(s) you want to access, verify by fetching recent releases or viewing logs.

​
Render

  • Context: Access build logs, service statuses, and environment details right where you’re coding
  • Sample prompt: “Why did my last staging build fail, and how should I adjust the config?”
  • Setup: Click Connect under Render, paste in your Render API key and confirm, choose the services/environments to surface, validate by loading the latest build logs.

​
Vercel

  • Context: Stream deployment previews, build logs, and analytics for faster iteration on web projects
  • Sample prompt: “What’s in the latest preview deployment of my Next.js app, and are there any build errors?”
  • Setup: Click Connect under Vercel, complete OAuth sign-in and select team/project, grant access to deployments and analytics, verify by asking about the latest preview deployment details.

​
Authentication Methods at a Glance

Authentication Summary:
  • OAuth: Honeycomb, MongoDB, Vercel
  • API Key: CircleCI, Render
  • CLI-based: Heroku (requires Heroku CLI)

​
Getting Started with Easy MCP

  1. Open the Augment Code extension in VS Code
  2. Navigate to the Easy MCP pane in the settings
  3. Click the ”+” button next to your desired integration
  4. Paste an API token or approve OAuth
  5. Start using the integration immediately in your Agent conversations
From that moment on, Augment Code streams your tool’s live context into every suggestion and autonomous Agent run.

​
Advanced MCP Configuration

For developers who need custom MCP server configurations or want to use servers not available through Easy MCP, you can still configure MCP servers manually. There are three ways to configure MCP servers in Augment:
  1. Easy MCP (recommended) - One-click integrations for popular tools
  2. Augment Settings Panel - Manual configuration with a GUI
  3. Import from JSON - Paste a JSON config to quickly add servers
MCP servers configured through the Settings Panel or Import from JSON are managed in the same place. After importing, you can edit or remove servers in the Settings Panel.

​
Configure in the Augment Settings Panel

The easiest way to configure MCP servers is to use the Augment Settings Panel. To access the settings panel, open the options menu in the upper right of the Augment panel and click the Settings option. Once the settings panel is open, you will see a section for MCP servers. Fill in the name and command fields. The name field must be a unique name for the server. The command field is the command to run the server. Environment variables have their own section and no longer need to be specified in the command. To add additional servers, click the + button next to the MCP header. To edit a configuration, or to delete a server, click the ... button next to the server name.

​
Add a Remote MCP server

If your MCP server runs remotely (for example, a hosted service), click the ”+ Add remote MCP” button in the MCP section. Remote MCP connections support both HTTP and SSE (Server‑Sent Events).
  • Connection Type: choose HTTP or SSE
  • Name: a unique display name for the server
  • URL: the base URL to your MCP server (e.g., https://api.example.com)
Remote MCP servers appear alongside your local MCP servers in the list. You can edit or remove them using the ”…” menu next to the server name.

​
Import from JSON

You can quickly add MCP servers by importing a JSON configuration from the Augment Settings Panel:
  1. Open the Settings Panel (gear icon in the Augment panel)
  2. In the MCP section, click Import from JSON
  3. Paste a configuration like the following and click Save
Example: Local command (Context7 via npx) 
{
  "mcpServers": {
    "Context7": {
      "command": "npx",
      "args": ["-y", "@upstash/context7-mcp"]
    }
  }
}
Example: Remote SSE endpoint 
{
  "mcpServers": {
    "test": {
      "url": "http://localhost:3001/sse",
      "type": "sse"
    }
  }
}
After importing, servers appear in the list where you can edit, test, or remove them. Ensure any required dependencies for the server are installed on your machine.

​
Server compatibility

Not all MCP servers are compatible with Augment’s models. The MCP standard, implementation of specific servers, and Augment’s MCP support are frequently being updated, so check compatibility frequently.