AWS CloudTrail MCP Server

Query CloudTrail events and Lake for audit investigations.

By defaultRead-only
With our presetSame: read-only is built in

Labels are provisional (from the project README/docs, checked Oct 27, 2026). Not yet tested in our sandbox.

Read-only switch

Event lookup and query tools only.

Preset

Read-onlyThe docs say it only reads, so there's no flag to add. Not sandbox-tested yet.
  • Matched by name only. AWS CloudTrail MCP Server is documented as read-only, but a fork or another server with the same name might not be. So Codex still prompts and Claude Code asks.

Claude Code

.mcp.json
{
  "mcpServers": {
    "cloudtrail": {
      "command": "uvx",
      "args": ["awslabs.cloudtrail-mcp-server@latest"]
    }
  }
}
.claude/settings.json
{
  "permissions": {
    "ask": ["mcp__cloudtrail"]
  }
}

ask makes Claude Code prompt before every tool from this server.

Codex

~/.codex/config.toml
# Generated by redpresets.dev on 2026-11-03. Unverified preset. Also use a read-only credential. Not a security guarantee.

[mcp_servers.cloudtrail]
command = "uvx"
args = ["awslabs.cloudtrail-mcp-server@latest"]
default_tools_approval_mode = "prompt"

default_tools_approval_mode = "prompt" asks before every tool call.

Cursor

.cursor/mcp.json
{
  "mcpServers": {
    "cloudtrail": {
      "type": "stdio",
      "command": "uvx",
      "args": ["awslabs.cloudtrail-mcp-server@latest"]
    }
  }
}

Don't add write tools to mcpAllowlist in .cursor/permissions.json. Leave them on approval. Cursor's docs say the allowlist is not a security boundary.

Credential layer

IAM AWSCloudTrail_ReadOnlyAccess.

Facts

Vendor
AWS Labs official
Source
awslabs/mcp
License
Apache-2.0
GitHub stars
9.8k
Latest release
2026.10.20261027104512 (Oct 27, 2026)
Last push
Oct 27, 2026
Status
Active
Last checked
Oct 27, 2026

Sources

  • README · checked Oct 27, 2026

Spotted something wrong? Labels change when vendors change. Suggest a correction

Read-only alternatives in Cloud