Amp

Amp reads ~/.config/amp/settings.json for your account and .amp/settings.json for a workspace. MCP servers live under the amp.mcpServers key. A remote server is a url; a local one is command with args and env.

Without a key

{
  "amp.mcpServers": {
    "wellworn": {
      "url": "https://mcp.wellworn.dev/mcp"
    }
  }
}

amp mcp add writes the same entry:

amp mcp add wellworn https://mcp.wellworn.dev/mcp

With a key

headers expands environment variables in its values, so the file can be committed while the key stays in your shell.

{
  "amp.mcpServers": {
    "wellworn": {
      "url": "https://mcp.wellworn.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${WELLWORN_KEY}"
      }
    }
  }
}

Confirm it works

Amp exposes the server's tools to the agent once the entry loads. Wellworn contributes eight: recommend, compare, alternatives, traps, skill, design, docs, submit_trap.

What breaks

A URL entry in settings.json is still local configuration, in Amp's words, even though the URL points at another machine. Sharing the server with a team means the amp mcp remote commands, which store the definition on ampcode.com against your workspace, not the settings file.

Verified 2026-09-08 against ampcode.com