ACP adapter for AmpCode

Use Amp from ACP-compatible clients such as Zed or Toad.

Prerequisites

• Node.js 18+ (the adapter will be installed automatically via npx)

Installation

Add to your Zed settings.json (open with cmd+, or ctrl+,):

{
  "agent_servers": {
    "Amp": {
      "command": "npx",
      "args": ["-y", "amp-acp"]
    }
  }
}

That's it! The SDK handles authentication and Amp integration automatically.

First Use

If you don't have Amp CLI installed: Add the AMP_API_KEY environment variable to your Zed config. You can get your API key from https://ampcode.com/settings

{
  "agent_servers": {
    "Amp": {
      "command": "npx",
      "args": ["-y", "amp-acp"],
      "env": {
        "AMP_API_KEY": "your-api-key-here"
      }
    }
  }
}

If you have Amp CLI installed: Run amp login first to authenticate.

How it Works

• Uses the official Amp SDK to communicate with AmpCode
• Streams Amp's responses over the Agent Client Protocol (ACP)
• Renders Amp messages and interactions natively in Zed
• Tool permissions are handled by Amp (no additional configuration needed)
• Supports conversation continuity across multiple prompts
• MCP servers configured in Zed are automatically passed through to Amp

MCP Configuration Passthrough

The adapter supports passing MCP (Model Context Protocol) servers configured in Zed through to Amp. This allows you to use the same MCP tools in both Zed's native AI and Amp.

This implementation is compatible with how other ACP agents like Claude Code and Codex handle MCP servers. See Zed's MCP documentation for more details.

Supported MCP Server Types

| Type | Description | Example | |------|-------------|---------| | stdio | Local command-line MCP servers | @playwright/mcp, @modelcontextprotocol/server-filesystem | | HTTP | Remote HTTP MCP servers | https://mcp.exa.ai/mcp, https://mcp.semgrep.ai/mcp | | SSE | Remote Server-Sent Events MCP servers | https://mcp.monday.com/sse |

Example: Using Exa Search with Amp

Exa provides a powerful web search MCP server. Add both the agent server and context servers to your Zed settings.json:

{
  "agent_servers": {
    "Amp": {
      "command": "npx",
      "args": ["-y", "amp-acp"]
    }
  },
  "context_servers": {
    "exa": {
      "url": "https://mcp.exa.ai/mcp"
    }
  }
}

Example: Multiple MCP Servers

You can configure multiple MCP servers to extend Amp's capabilities:

{
  "agent_servers": {
    "Amp": {
      "command": "npx",
      "args": ["-y", "amp-acp"]
    }
  },
  "context_servers": {
    "playwright": {
      "command": "npx",
      "args": ["-y", "@playwright/mcp@latest", "--headless"]
    },
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/allowed"]
    },
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "your-token"
      }
    }
  }
}

How MCP Passthrough Works

1. When you configure context_servers in Zed's settings.json, Zed passes them to the ACP agent via the mcpServers parameter in the session/new request
2. The amp-acp adapter converts the MCP server configurations from ACP format to Amp SDK format
3. Amp connects to the MCP servers and makes their tools available during the session

For more details, see docs/mcp-passthrough.md.

Using Pre-built Binaries

Pre-built binaries are available on the GitHub Releases page for:

| Platform | Architecture | Binary | |----------|-------------|--------| | Linux | x64 | amp-acp-linux-x64 | | Linux | arm64 | amp-acp-linux-arm64 | | macOS | x64 (Intel) | amp-acp-darwin-x64 | | macOS | arm64 (Apple Silicon) | amp-acp-darwin-arm64 | | Windows | x64 | amp-acp-windows-x64.exe |

Download the binary for your platform, make it executable (chmod +x on Linux/macOS), and configure Zed to use it:

{
  "agent_servers": {
    "Amp": {
      "command": "/path/to/amp-acp-darwin-arm64"
    }
  }
}

These are standalone executables with no runtime dependencies — no Node.js or Bun required.

Troubleshooting

Adapter doesn't start: Make sure you have Node.js 18 or later installed. Run node --version to check.

Connection issues: Restart Zed and try again. The adapter creates a fresh connection each time.

Tool execution problems: Check Zed's output panel for detailed error messages from the Amp SDK.

MCP server not connecting: Ensure the MCP server command is correct and any required environment variables are set. Check Zed's logs for connection errors.