Awslabs Core Mcp Server

Created By
awslabsa year ago
Overview

What is Awslabs Core MCP Server?

Awslabs Core MCP Server is a suite of specialized servers designed to integrate AWS best practices into your development workflow, providing tools for managing and coordinating various AWS Labs MCP servers.

How to use Awslabs Core MCP Server?

To use the Core MCP Server, install the required dependencies, configure your AWS credentials, and add the server to your MCP client configuration. Detailed installation instructions are provided in the documentation.

Key features of Awslabs Core MCP Server?

  • Automatic management of MCP servers
  • Planning and guidance for orchestrating AWS Labs MCP Servers
  • Centralized configuration management
  • Support for UVX installation

Use cases of Awslabs Core MCP Server?

  1. Managing multiple AWS Labs MCP servers efficiently.
  2. Coordinating server operations and configurations in a development environment.
  3. Implementing AWS best practices in server management.

FAQ from Awslabs Core MCP Server?

  • What is the purpose of the Core MCP Server?

The Core MCP Server helps manage and coordinate other AWS Labs MCP servers, ensuring best practices are followed in your development workflow.

  • 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.

Server Config

{
  "mcpServers": {
    "awslabs-core-mcp-server": {
      "command": "uvx",
      "args": [
        "awslabs.core-mcp-server@latest"
      ],
      "env": {
        "FASTMCP_LOG_LEVEL": "ERROR",
        "MCP_SETTINGS_PATH": "path to your mcp server settings"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
awslabs
Star
-
Language
-
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