AWS Resources MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is AWS Resources MCP Server?

AWS Resources MCP Server is a Model Context Protocol (MCP) server implementation that allows users to run generated Python code to query AWS resources using the boto3 library.

How to use AWS Resources MCP Server?

To use the server, you need to set up AWS credentials and run the server via Docker. You can execute Python code snippets to query AWS resources directly.

Key features of AWS Resources MCP Server?

  • Executes Python code to query AWS resources using boto3.
  • Supports dynamic resource querying through a Docker container.
  • Allows management operations beyond read-only access, depending on user permissions.

Use cases of AWS Resources MCP Server?

  1. Querying S3 buckets and their contents.
  2. Retrieving the latest deployment from AWS CodePipeline.
  3. Managing AWS resources programmatically with Python.

FAQ from AWS Resources MCP Server?

  • What permissions do I need to use this server?

You need AWS credentials with appropriate permissions to query the resources you want.

  • Is there a limit on the number of queries?

No, the server does not impose a limit, but your AWS user role will dictate the permissions for what you can do.

  • Can I run this server locally?

Yes, you can build the Docker image locally or pull it from Docker Hub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
MIT license

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