home / mcp / powertools for aws mcp server

Powertools for AWS MCP Server

Powertools for AWS's official MCP Server

Installation
Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "aws-powertools-powertools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "powertools-for-aws-mcp"
      ]
    }
  }
}

Powertools for AWS MCP provides a Model Context Protocol (MCP) server that enables fast, cross-runtime searching of Powertools for AWS Lambda documentation and examples. You can query the server from your MCP-enabled clients to find relevant guidance and usage examples to accelerate development with Powertools for AWS Lambda.

How to use

You connect your MCP-enabled client to the Powertools for AWS MCP server to search documentation and examples across runtimes. Use the server to quickly locate topics you’re exploring, then feed the results into your conversations with LLMs or agents to improve understanding and implementation without leaving your toolchain.

How to install

Prerequisites: ensure you have Node.js and npm installed on your machine.

Install and run the MCP server locally using the standard package manager flow shown below.

# Install dependencies and set up hooks for development
npm ci
npm run setup:hooks

# Start the MCP server for development
npm run dev
```,

Configure the MCP server for a client by using the following local STDIO configuration. This runs the server via the Node.js package and communicates over STDIO.

{
  "mcpServers": {
    "powertools": {
      "command": "npx",
      "args": ["-y", "powertools-for-aws-mcp"]
    }
  }
}

Additional setup details

The server is designed to be consumed by MCP-enabled clients such as command-line tools, IDE integrations, or chat assistants that support the MCP. Start it with the command shown above and connect your client using the same tool name (powertools) to access the search capabilities.

Notes

This MCP server is intended for experimentation and active development. APIs and features may evolve rapidly, so expect changes over time. If you need to adjust how the server runs locally, you can modify the start script or the npx invocation to point to a local build or a specific version of the package.