Amazon Web Services · Codex
Add the AWS MCP server to Codex
Managed AWS server: search AWS docs, call AWS APIs and run guided SOP workflows.
1. Add the server
Run in your terminal
# ~/.codex/config.toml [mcp_servers.aws] command = "uvx" args = ["mcp-proxy-for-aws", "https://aws-mcp.us-east-1.api.aws/mcp"]
Scopes, env vars, OAuth and limits: Codex MCP config guide
2. Sign in
Run codex mcp login <name> to complete OAuth for a remote server. AWS runs locally; set any credentials Amazon Web Services asks for before starting Codex.
3. Try it
Ask Codex for something AWS can do. Managed AWS server: search AWS docs, call AWS APIs and run guided SOP workflows. Approve the first tool call and check the result before allowing write actions automatically.
- · Each server is a [mcp_servers.<name>] table in config.toml.
- · Use enabled_tools or disabled_tools to keep the tool list short.
Get the weekly agent stack update
New official MCP servers, spec changes and harness releases, checked against the source. One email a week, no fluff.
FAQ
- How do I add the AWS MCP server to Codex?
- Run: # ~/.codex/config.toml …. Run codex mcp login <name> to complete OAuth for a remote server.
- Is this the official AWS MCP server?
- Yes. It is published by Amazon Web Services as io.github.aws/aws-mcp in the official MCP registry.
- Does the AWS MCP server need an API key?
- It runs locally from a package. See Amazon Web Services's docs for any credentials it needs.
Links
AWS in other clients
More cloud & infrastructure for Codex
Work at Amazon Web Services?
Feature AWS across the directory and its category from $49/month.
Reviewed Oct 5, 2026. Command generated from the registry record and checked against Codex's documented syntax.