Amp CLI adds workspace-specific settings
Amp's CLI now supports workspace-specific configuration via .amp/settings.json files placed in project directories. This enables per-project preferences—such as permissions and MCP servers—to be recorded alongside a project's source, and automatically applied when running amp inside that workspace.
How it works
A workspace-level settings file is read and merged with global Amp settings whenever amp runs in that directory. This merge means project-specific overrides or additions can coexist with broader user-level configuration without manual switching.
The new behavior is surfaced through existing CLI commands with a --workspace flag. For example, adding an MCP server for a single project can be done with a single command and will update the project’s settings file rather than the global config.
Example
The example command from the update:
amp mcp add --workspace playwright -- npx -y @playwright/mcp@latest
Because of the --workspace flag, the addition is stored in the project at .amp/settings.json. The settings produced by that command can be represented compactly as:
{"amp.mcpServers":{"playwright":{"command":"npx","args":["-y","@playwright/mcp@latest"]}}}
When running amp in that project directory, the CLI will merge the contents of .amp/settings.json with the global settings so the newly defined playwright MCP server becomes available for commands run in that workspace.
Where to find details
For the full resolution rules and additional configuration options, consult the manual: manual
Original source: https://ampcode.com/news/cli-workspace-settings
