The Powertools for AWS Model Context Protocol (MCP) is an MCP implementation that provides search functionality for the Powertools for AWS Lambda documentation across multiple runtimes. It allows your LLM agents to search for documentation and examples related to the toolkit, helping you to quickly find the information you need to use Powertools for AWS Lambda effectively.
Warning
This project is experimental and under active development. APIs and features may change frequently without notice.
We're actively seeking community feedback and feature suggestions join our Discord or open an issue to share your thoughts.
Most clients that support MCP can use this server out of the box using a configuration similar to the following:
Note
If you are using an older version of the MCP, make sure to update your configuration to use the new package name powertools-for-aws-mcp.
{
"mcpServers": {
"powertools": {
"command": "npx",
"args": ["-y", "powertools-for-aws-mcp"]
}
}
}
This setup uses the Node.js package manager to run the MCP server locally and communicate with it using the STDIO interface.
Client-Specific Setup InstructionsFor detailed setup instructions for specific clients, see the configurations below:
Getting Started with Amazon Q Developer CLI Use in Amazon Q Developer CLISee Amazon Q Developer CLI documentation for details.
Add MCP Server using CLI commands:
qchat mcp add powertools npx -y powertools-for-aws-mcp
Manual Configuration: If you select global scope, the MCP server configuration is stored in ~/.aws/amazonq/mcp.json and available across all your projects. If you select local scope, the configuration is stored in .amazonq/mcp.json within your current project.
{
"mcpServers": {
"powertools": {
"command": "npx",
"args": ["-y", "powertools-for-aws-mcp"]
}
}
} Getting Started with Kiro Use in Kiro
See Kiro Model Context Protocol Documentation for details.
Kiro > MCP Servers+ Add button.For macOS/Linux:
{
"mcpServers": {
"powertools": {
"command": "npx",
"args": ["-y", "powertools-for-aws-mcp"]
}
}
}
For Windows:
{
"mcpServers": {
"powertools": {
"disabled": false,
"timeout": 60,
"type": "stdio",
"command": "npx",
"args": ["-y", "powertools-for-aws-mcp"]
}
}
} Getting Started with Cursor Getting Started with Cursor
A. Project Configuration - For tools specific to a project, create a .cursor/mcp.json file in your project directory. - This allows you to define MCP servers that are only available within that specific project.
B. Global Configuration - For tools that you want to use across all projects, create a ~/.cursor/mcp.json file in your home directory. - This makes MCP servers available in all your Cursor workspaces.
{
"mcpServers": {
"powertools": {
"command": "npx",
"args": ["-y", "powertools-for-aws-mcp"]
}
}
}
Using MCP in Chat: The Composer Agent will automatically use any MCP tools that are listed under Available Tools on the MCP settings page if it determines them to be relevant. To prompt tool usage intentionally, please prompt Cursor to use the desired MCP Server you wish to use. For example, Using the Powertools MCP Server, do...
Tool Approval: By default, when the Agent wants to use an MCP tool, it will display a message asking for your approval. You can use the arrow next to the tool name to expand the message and see what arguments the Agent is calling the tool with.
Access MCP Settings
Add MCP Servers
Manual Configuration
~/.codeium/windsurf/mcp_config.json~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"powertools": {
"command": "npx",
"args": ["-y", "powertools-for-aws-mcp"]
}
}
} Getting Started with VS Code Install in VS Code
Configure MCP servers in VS Code settings or in .vscode/mcp.json (see VS Code MCP docs for more info.):
{
"mcpServers": {
"powertools": {
"command": "npx",
"args": ["-y", "powertools-for-aws-mcp"]
}
}
} Getting Started with Claude Code Use in Claude Code
Add MCP Server using CLI commands:
claude mcp add powertools
Manual Configuration (Recommended): You can directly edit the configuration file located at ~/.claude.json. This approach is more flexible and allows you to see all configurations at once.
{
"mcpServers": {
"powertools": {
"type": "stdio",
"command": "npx",
"args": ["-y", "powertools-for-aws-mcp"]
}
}
}
Restart Claude Code: After editing the config file, restart Claude Code for the changes to take effect.
After cloning the repository, you can set up your development environment by running:
npm ci npm run setup:hooks
After that you can run tests using npm t or npm run test:unit:coverage for coverage reports.
You can also run the server locally using: npm run dev, this will start an inspector server that lets you interact with the MCP server using a browser UI.
If you want, you can also configure the server to run with Amazon Q, Claude Desktop, or other LLM clients that support the Model Context Protocol (MCP) by using node as command and passing the --experimental-transform-types flag and the path to the src/index.ts file of this project.
For example, with Claude Code, you can add the server by running:
claude mcp add pt-dev node -- --experimental-transform-types /path/to/project/powertools-mcp/src/index.ts
Michael Walmsley at ServerlessDNA.com for creating the initial implementation of this MCP server and donating it to the Powertools for AWS team at Amazon Web Services.
This library is licensed under the MIT License. See the LICENSE file.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4