{
  "@context": "https://schema.org",
  "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2025-11-04-workspace-settings/#webpage",
  "@type": [
    "WebPage",
    "ArchiveComponent"
  ],
  "articleBody": "The Amp CLI now supports workspace-specific settings via `.amp/settings.json` files in your project directory.\n\nThis allows you to configure the Amp CLI differently for each project, with settings like permissions, MCP servers, and other preferences automatically picked up when you run `amp` in that workspace.\n\nFor example, here's how you can configure the Amp CLI to use a specific MCP server in a given project:\n\n```\n$ cd my-project\n$ amp mcp add --workspace playwright -- npx -y @playwright/mcp@latest\n```\n\nDue to the `--workspace` flag, the setting was added in the `.amp/settings.json` file in `my-project`:\n\n```\n$ cat .amp/settings.json\n{\n  \"amp.mcpServers\": {\n    \"playwright\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@playwright/mcp@latest\"\n      ]\n    }\n  }\n}\n```\n\nWhen you then run `amp` in `my-project`, the settings in `.amp/settings.json` will be merged with your global Amp settings.\n\nSee the [manual](https://ampcode.com/manual#configuration) for details on how settings are resolved.\n",
  "authors": [],
  "captured_at": "2026-10-03T23:09:50.514863041+00:00",
  "category": "programming",
  "content_html": "<p>The Amp CLI now supports workspace-specific settings via <code>.amp/settings.json</code> files in your project directory.</p>\n<p>This allows you to configure the Amp CLI differently for each project, with settings like permissions, MCP servers, and other preferences automatically picked up when you run <code>amp</code> in that workspace.</p>\n<p>For example, here's how you can configure the Amp CLI to use a specific MCP server in a given project:</p>\n<pre><code><span class=\"code-snippet\" data-language=\"Shell\"><span class=\"syntax-source syntax-shell syntax-bash\"><span class=\"syntax-meta syntax-function-call syntax-shell\"><span class=\"syntax-variable syntax-function syntax-shell\">$</span></span><span class=\"syntax-meta syntax-function-call syntax-arguments syntax-shell\"> cd my-project</span>\n<span class=\"syntax-meta syntax-function-call syntax-shell\"><span class=\"syntax-variable syntax-function syntax-shell\">$</span></span><span class=\"syntax-meta syntax-function-call syntax-arguments syntax-shell\"> amp mcp add<span class=\"syntax-variable syntax-parameter syntax-option syntax-shell\"><span class=\"syntax-punctuation syntax-definition syntax-parameter syntax-shell\"> --</span>workspace</span> playwright<span class=\"syntax-keyword syntax-operator syntax-end-of-options syntax-shell\"> --</span></span><span class=\"syntax-meta syntax-function-call syntax-arguments syntax-shell\"> npx -y @playwright/mcp@latest</span>\n</span></span></code></pre>\n<p>Due to the <code>--workspace</code> flag, the setting was added in the <code>.amp/settings.json</code> file in <code>my-project</code>:</p>\n<pre><code><span class=\"code-snippet\" data-language=\"Shell\"><span class=\"syntax-source syntax-shell syntax-bash\"><span class=\"syntax-meta syntax-function-call syntax-shell\"><span class=\"syntax-variable syntax-function syntax-shell\">$</span></span><span class=\"syntax-meta syntax-function-call syntax-arguments syntax-shell\"> cat .amp/settings.json</span>\n<span class=\"syntax-punctuation syntax-definition syntax-compound syntax-braces syntax-begin syntax-shell\">{</span>\n  <span class=\"syntax-meta syntax-function-call syntax-shell\"><span class=\"syntax-variable syntax-function syntax-shell\"><span class=\"syntax-string syntax-quoted syntax-double syntax-shell\"><span class=\"syntax-punctuation syntax-definition syntax-string syntax-begin syntax-shell\">&quot;</span>amp.mcpServers<span class=\"syntax-punctuation syntax-definition syntax-string syntax-end syntax-shell\">&quot;</span></span>:</span></span><span class=\"syntax-meta syntax-function-call syntax-arguments syntax-shell\"> <span class=\"syntax-meta syntax-group syntax-expansion syntax-brace syntax-shell\"><span class=\"syntax-punctuation syntax-section syntax-expansion syntax-brace syntax-begin syntax-shell\">{</span>\n    <span class=\"syntax-string syntax-quoted syntax-double syntax-shell\"><span class=\"syntax-punctuation syntax-definition syntax-string syntax-begin syntax-shell\">&quot;</span>playwright<span class=\"syntax-punctuation syntax-definition syntax-string syntax-end syntax-shell\">&quot;</span></span>: <span class=\"syntax-meta syntax-group syntax-expansion syntax-brace syntax-shell\"><span class=\"syntax-punctuation syntax-section syntax-expansion syntax-brace syntax-begin syntax-shell\">{</span>\n      <span class=\"syntax-string syntax-quoted syntax-double syntax-shell\"><span class=\"syntax-punctuation syntax-definition syntax-string syntax-begin syntax-shell\">&quot;</span>command<span class=\"syntax-punctuation syntax-definition syntax-string syntax-end syntax-shell\">&quot;</span></span>: <span class=\"syntax-string syntax-quoted syntax-double syntax-shell\"><span class=\"syntax-punctuation syntax-definition syntax-string syntax-begin syntax-shell\">&quot;</span>npx<span class=\"syntax-punctuation syntax-definition syntax-string syntax-end syntax-shell\">&quot;</span></span><span class=\"syntax-punctuation syntax-separator syntax-shell\">,</span>\n      <span class=\"syntax-string syntax-quoted syntax-double syntax-shell\"><span class=\"syntax-punctuation syntax-definition syntax-string syntax-begin syntax-shell\">&quot;</span>args<span class=\"syntax-punctuation syntax-definition syntax-string syntax-end syntax-shell\">&quot;</span></span>: <span class=\"syntax-keyword syntax-control syntax-regexp syntax-set syntax-begin syntax-shell\">[</span>\n        <span class=\"syntax-string syntax-quoted syntax-double syntax-shell\"><span class=\"syntax-punctuation syntax-definition syntax-string syntax-begin syntax-shell\">&quot;</span>-y<span class=\"syntax-punctuation syntax-definition syntax-string syntax-end syntax-shell\">&quot;</span></span>,\n        <span class=\"syntax-string syntax-quoted syntax-double syntax-shell\"><span class=\"syntax-punctuation syntax-definition syntax-string syntax-begin syntax-shell\">&quot;</span>@playwright/mcp@latest<span class=\"syntax-punctuation syntax-definition syntax-string syntax-end syntax-shell\">&quot;</span></span>\n      <span class=\"syntax-keyword syntax-control syntax-regexp syntax-set syntax-end syntax-shell\">]</span>\n    <span class=\"syntax-punctuation syntax-section syntax-expansion syntax-brace syntax-end syntax-shell\">}</span></span>\n  <span class=\"syntax-punctuation syntax-section syntax-expansion syntax-brace syntax-end syntax-shell\">}</span></span></span>\n<span class=\"syntax-punctuation syntax-definition syntax-compound syntax-braces syntax-end syntax-shell\">}</span>\n</span></span></code></pre>\n<p>When you then run <code>amp</code> in <code>my-project</code>, the settings in <code>.amp/settings.json</code> will be merged with your global Amp settings.</p>\n<p>See the <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://ampcode.com/manual#configuration\">manual</a> for details on how settings are resolved.</p>\n",
  "content_markdown": "The Amp CLI now supports workspace-specific settings via `.amp/settings.json` files in your project directory.\n\nThis allows you to configure the Amp CLI differently for each project, with settings like permissions, MCP servers, and other preferences automatically picked up when you run `amp` in that workspace.\n\nFor example, here's how you can configure the Amp CLI to use a specific MCP server in a given project:\n\n```\n$ cd my-project\n$ amp mcp add --workspace playwright -- npx -y @playwright/mcp@latest\n```\n\nDue to the `--workspace` flag, the setting was added in the `.amp/settings.json` file in `my-project`:\n\n```\n$ cat .amp/settings.json\n{\n  \"amp.mcpServers\": {\n    \"playwright\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@playwright/mcp@latest\"\n      ]\n    }\n  }\n}\n```\n\nWhen you then run `amp` in `my-project`, the settings in `.amp/settings.json` will be merged with your global Amp settings.\n\nSee the [manual](https://ampcode.com/manual#configuration) for details on how settings are resolved.\n",
  "dateCreated": "2026-10-03T23:09:50.514863041+00:00",
  "date_created": "2025-11-04T00:00:00+00:00",
  "date_modified": "2025-11-04T00:00:00+00:00",
  "date_published": "2025-11-04T00:00:00+00:00",
  "description": "The Amp CLI now supports workspace-specific settings via .amp/settings.json files in your project directory. This allows you to configure the Amp CLI differently for each project, with settings like permissions, MCP servers, and other…",
  "external_url": "https://ampcode.com/news/cli-workspace-settings",
  "git": {
    "commit": "ebb0941c5c06a2ab2377342d607535262a3e969e",
    "path": "items/ampcode-com/2025/11/2025-11-04-workspace-settings.md",
    "permalink": "https://github.com/aymericbeaumet/aggr-instance/blob/ebb0941c5c06a2ab2377342d607535262a3e969e/items/ampcode-com/2025/11/2025-11-04-workspace-settings.md"
  },
  "id": "urn:aggr:item:c491bdfaa1bcb89b4efe2dcdcaa59f56a68d5f61",
  "isBasedOn": {
    "@id": "https://ampcode.com/news/cli-workspace-settings"
  },
  "mainEntity": {
    "@id": "https://ampcode.com/news/cli-workspace-settings",
    "@type": "CreativeWork",
    "archivedAt": {
      "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2025-11-04-workspace-settings/#webpage"
    },
    "dateModified": "2025-11-04T00:00:00+00:00",
    "datePublished": "2025-11-04T00:00:00+00:00",
    "headline": "Workspace Settings",
    "timeRequired": "PT1M",
    "url": "https://ampcode.com/news/cli-workspace-settings",
    "wordCount": 140
  },
  "name": "Archived snapshot: Workspace Settings",
  "preview": null,
  "reading_minutes": 1,
  "replicated_at": null,
  "source": "ampcode-com",
  "source_name": "Amp News",
  "summary": "The Amp CLI now supports workspace-specific settings via .amp/settings.json files in your project directory. This allows you to configure the Amp CLI differently for each project, with settings like permissions, MCP servers, and other preferences automatically picked up when you run amp in that workspace. For example, here's how you can configure the Amp CLI to use a specific MCP server in a given project: $ cd my-project $ amp mcp add --workspace playwright -- npx -y @playwright/mcp@latest Due to the --workspace flag, the setting was added in the .amp/settings.json file in my-project: $ cat .amp/settings.json { \"amp.mcpServers\": { \"playwright\": { \"command\": \"npx\", \"args\": [ \"-y\", \"@playwright/mcp@latest\" ] } } } When you then run amp in my-project, the settings in .amp/settings.json will be merged with your global Amp settings. See the manual for details on how settings are resolved.",
  "tags": [],
  "temporalCoverage": "2026-10-03T23:09:50.514863041+00:00",
  "title": "Workspace Settings",
  "url": "https://aggr.aymericbeaumet.com/items/ampcode-com/2025-11-04-workspace-settings/",
  "word_count": 140
}