Amp — MCP Configs
- File format
- JSON
- Discovery path
-
.amp/settings.json - Syllago install method
- JSON merge
- Symlink support
- No
- Config file
-
.amp/settings.json - Transports
-
stdio,sse
Features
How each feature converts to syllago's canonical format. See format conversion for what these statuses mean.
Fields
Native frontmatter or config fields this provider exposes. The first column is the provider's own field name; the canonical key column links to syllago's cross-provider equivalent.
| Config key | Conversion | Canonical key | Summary |
|---|---|---|---|
amp.mcpServers | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | — | Servers configured under 'amp.mcpServers' with local (command/args/env) or remote (url/headers) modes; supports '$' env-var refs and 'disabled' flag. |
MCP Registry | Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more → | — | Workspace admins enforce an approved-MCP registry (modelcontextprotocol.io schema); unreachable registry blocks all servers. |
Other features
Behaviors, conventions, and capabilities that aren't tied to a single named field — things like path-based activation, discovery rules, and lifecycle behavior.
| Feature | Conversion | Summary |
|---|---|---|
enterprise_management | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | enterprise_registry_allowlist: Amp supports organization-level MCP configuration with an enterprise registry and allowlist |
oauth_support | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | oauth_support: Amp supports OAuth 2.0 authentication for remote MCP servers |
| Per-tool enable/disable | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | Individual tools within a configured MCP server can be disabled (via VS Code UI) without removing the server. |
tool_filtering | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | per_tool_enable_disable: Amp supports per-tool enable/disable configuration to control which MCP tools are exposed to the agent |
| CLI: amp mcp add | Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more → | Add servers via 'amp mcp add <name> -- <command> [args...]' (local) or 'amp mcp add <name> <url>' (remote); writes to user settings. |
| MCP server loading precedence | Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more → | On name collisions, precedence is CLI flags > user/workspace config > skill-bundled servers. |
| OAuth authentication for remote MCP servers | Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more → | OAuth flow auto-starts for self-registering servers; manual setup uses 'amp mcp oauth login'; tokens cached in '~/.amp/oauth/'. |
| Settings file locations by platform | Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more → | Settings live at '%APPDATA%\amp\settings.json' (Windows) or '~/.config/amp/settings.json' (mac/Linux); workspace at '.amp/settings.json'. |
| Skill-bundled MCP servers as preferred approach | Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more → | Official guidance prefers bundling MCP servers in skills via mcp.json over global config to keep tool-lists clean. |
| VS Code extension UI for MCP setup | Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more → | VS Code Amp extension exposes MCP setup via Settings > Extensions > Amp > MCP Servers > Add MCP Server. |
| Workspace MCP server trust approval | Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more → | Workspace-defined servers require 'amp mcp approve <name>' before running; global and CLI-provided servers run without approval. |