AWS MCP Server

Created By
Rupeebwa year ago
Overview

what is AWS MCP Server?

AWS MCP Server is a server application that connects to AWS accounts, providing a similar experience to the AWS Command Line Interface (CLI).

how to use AWS MCP Server?

To use the AWS MCP Server, install the dependencies, configure your AWS credentials, and start the server. You can then interact with AWS services through REST APIs.

key features of AWS MCP Server?

  • Connects to AWS accounts using various credential management methods.
  • Supports multiple AWS services including EC2, S3, and Lambda.
  • Provides a profile-based configuration for easier management.
  • Includes security measures to prevent accidental exposure of credentials.

use cases of AWS MCP Server?

  1. Managing AWS S3 buckets and objects.
  2. Starting and stopping EC2 instances.
  3. Invoking AWS Lambda functions.
  4. Building frontend applications that interact with AWS services.

FAQ from AWS MCP Server?

  • How do I configure my AWS credentials?

You can configure your AWS credentials using environment variables, AWS credentials file, or instance profiles when running on EC2.

  • Is there a way to prevent committing sensitive information?

Yes! The project includes a .gitignore file and Git hooks to help prevent committing secrets.

  • Can I use temporary AWS credentials?

Yes, but make sure to include the session token in your configuration.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Rupeebw
Star
0
Language
JavaScript
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)

a day ago