Aws Security Mcp

Created By
groovyBugifya year ago
A Model Context Protocol server that connects AI assistants like Claude to AWS security services, allowing them to autonomously query, inspect, and analyze AWS infrastructure for security issues and misconfigurations.
Overview

What is AWS Security MCP?

AWS Security MCP is a Model Context Protocol server that connects AI assistants like Claude to AWS security services, enabling them to autonomously query, inspect, and analyze AWS infrastructure for security issues and misconfigurations.

How to use AWS Security MCP?

To use AWS Security MCP, clone the repository, set up your AWS credentials, and configure your MCP client (like Claude) to connect to the AWS Security MCP server.

Key features of AWS Security MCP?

  • Natural language querying of AWS infrastructure.
  • Security findings retrieval from GuardDuty, SecurityHub, and IAM Access Analyzer.
  • Inspection of AWS resources for misconfigurations.
  • Analysis of IAM roles, policies, and permissions.
  • Generation of threat modeling reports and contextual security recommendations.
  • Visualization of network maps and blast radius analysis.

Use cases of AWS Security MCP?

  1. Automating security audits of AWS infrastructure.
  2. Assisting security teams in identifying misconfigurations.
  3. Providing real-time security insights and recommendations.

FAQ from AWS Security MCP?

  • Can AWS Security MCP work with any MCP client?

Yes! It is designed to work with any MCP client that supports the Model Context Protocol.

  • What are the prerequisites for using AWS Security MCP?

You need Python 3.11+, an AWS account with proper credentials, and an MCP client like Claude.

  • Is AWS Security MCP free to use?

Yes! AWS Security MCP is open-source and free to use.

Server Config

{
  "mcpServers": {
    "aws-security": {
      "command": "/path/to/aws-security-mcp/run_aws_security.sh"
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
groovyBugify
Star
31
Language
Python
License
Apache-2.0 license
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago