AWS MCP Servers

Created By
awslabsa year ago
AWS MCP Servers — helping you get the most out of AWS, wherever you use MCP.
Overview

What is AWS MCP Servers?

AWS MCP Servers is a suite of specialized servers designed to integrate AWS best practices directly into your development workflow, enhancing productivity and efficiency.

How to use AWS MCP Servers?

To use AWS MCP Servers, install the required server packages, configure your AWS credentials, and add the server to your MCP client configuration. Detailed installation instructions are provided for each server.

Key features of AWS MCP Servers?

  • Bedrock Knowledge Bases Retrieval MCP Server for querying knowledge bases with natural language.
  • CDK MCP Server for AWS CDK project analysis and best practices.
  • Cost Analysis MCP Server for visualizing and analyzing AWS costs.
  • Nova Canvas MCP Server for generating images using text-based prompts.

Use cases of AWS MCP Servers?

  1. Accessing and querying knowledge bases for information retrieval.
  2. Assisting in AWS CDK project development and infrastructure management.
  3. Analyzing AWS costs and generating insightful reports.
  4. Creating images based on textual descriptions for various applications.

FAQ from AWS MCP Servers?

  • What programming language is used?

The servers are primarily developed in Python.

  • Is there documentation available?

Yes, comprehensive documentation is available on the documentation website.

  • What license is the project under?

The project is licensed under the Apache-2.0 License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
awslabs
Star
3651
Language
Python
License
Apache-2.0 license
Tags

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)

11 hours ago