Amp
Amp MCP Setup: amp mcp add, amp.mcpServers and Workspace Approval
How do I add an MCP server to Amp?
Run amp mcp add with a name and either a command or a URL, or add the server to amp.mcpServers in ~/.config/amp/settings.json or .amp/settings.json. Amp recommends bundling MCP servers in skills so tools load only when needed. Servers in workspace settings must be approved with amp mcp approve.
Add a server from the CLI
Terminal
amp mcp add context7 -- npx -y @upstash/context7-mcp amp mcp add linear https://mcp.linear.app/sse
Add servers in settings
Use command, args and env for local servers, and url and headers for remote ones. Reference environment variables with ${VAR_NAME}.
~/.config/amp/settings.json
"amp.mcpServers": {
"playwright": {
"command": "npx",
"args": ["-y", "@playwright/mcp@latest", "--headless"]
},
"linear": {
"url": "https://mcp.linear.app/sse"
},
"sourcegraph": {
"url": "${SRC_ENDPOINT}/.api/mcp/v1",
"headers": { "Authorization": "token ${SRC_ACCESS_TOKEN}" }
}
}Which config wins
- 1. CLI flag --mcp-config
- 2. Workspace config: amp.mcpServers in .amp/settings.json
- 3. User config: amp.mcpServers in ~/.config/amp/settings.json
- 4. Skills
Servers in .amp/settings.json need explicit approval before they run. Servers in your global settings or passed with --mcp-config do not.
Terminal
amp mcp doctor amp mcp approve my-server
Bundle a server in a skill
Put an mcp.json next to a skill's SKILL.md. The tools stay hidden until the skill loads. includeTools limits which tools are exposed.
.agents/skills/browser/mcp.json
{
"chrome-devtools": {
"command": "npx",
"args": ["-y", "chrome-devtools-mcp@latest"],
"includeTools": ["navigate_*", "take_screenshot", "click", "fill*"]
}
}OAuth and remote definitions
For servers with automatic OAuth, Amp opens the browser flow when the TUI starts. For servers that need a manual client, register it with amp mcp oauth login. Remote definitions stored on ampcode.com work across clients and need a scope flag.
Terminal
amp mcp oauth login my-server \ --server-url https://example.com/.api/mcp/v1 \ --client-id your-client-id \ --client-secret your-client-secret \ --scopes "openid,profile,email,user:all" amp mcp remote --personal add Linear https://mcp.linear.app/mcp amp mcp remote --personal list
Get Amp settings changes by email
When a setting, flag or permission rule in this guide changes, it goes in the weekly AgentAtlas update, checked against the vendor docs. One email a week.
Sources
More on Amp
More Amp guides
Other guides
Reviewed Oct 13, 2026. Settings change often; the linked vendor docs are the source of truth.