by aws-powertools
Provides searchable access to Powertools for AWS Lambda documentation, enabling LLM agents to retrieve relevant examples and guidance directly from the toolkit's reference material.
A Model Context Protocol (MCP) server that indexes Powertools for AWS Lambda documentation across multiple runtimes and exposes a search interface for LLM agents.
{
"mcpServers": {
"powertools": {
"command": "npx",
"args": ["-y", "powertools-for-aws-mcp"]
}
}
}
npx.Q: Do I need a special version of MCP?
A: Use the latest MCP client; ensure the configuration points to powertools-for-aws-mcp.
Q: Can I run the server locally?
A: Yes—npx -y powertools-for-aws-mcp starts a local STDIO server that client tools connect to.
Q: Is the project stable? A: It is marked Experimental and Evolving; APIs may change.
Q: How do I contribute? A: Join the Discord community or open an issue on GitHub.
Q: What environment variables are required?
A: No mandatory variables; optional keys (e.g., API keys for custom back‑ends) can be added under env.
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.
| Cursor | VS Code |
|---|---|
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.
For detailed setup instructions for specific clients, see the configurations below:
See Amazon Q Developer CLI documentation for details.
Add MCP Server using CLI commands:
qchat mcp add --name powertools --command "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.
~/.aws/amazonq/mcp.json{
"mcpServers": {
"powertools": {
"command": "npx",
"args": ["-y", "powertools-for-aws-mcp"]
}
}
}
See Kiro Model Context Protocol Documentation for details.
Kiro > MCP Servers+ Add button.kiro_mcp_settings.jsonFor 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"]
}
}
}
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.
.cursor/mcp.json{
"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"]
}
}
}
Configure MCP servers in VS Code settings or in .vscode/mcp.json (see VS Code MCP docs for more info.):
.vscode/mcp.json{
"mcpServers": {
"powertools": {
"command": "npx",
"args": ["-y", "powertools-for-aws-mcp"]
}
}
}
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.
~/.claude.json{
"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.
Please log in to share your review and rating for this MCP.
Explore related MCPs that share similar capabilities and solve comparable challenges
by exa-labs
Provides real-time web search capabilities to AI assistants via a Model Context Protocol server, enabling safe and controlled access to the Exa AI Search API.
by perplexityai
Enables Claude and other MCP‑compatible applications to perform real‑time web searches through the Perplexity (Sonar) API without leaving the MCP ecosystem.
by MicrosoftDocs
Provides semantic search and fetch capabilities for Microsoft official documentation, returning content in markdown format via a lightweight streamable HTTP transport for AI agents and development tools.
by elastic
Enables natural‑language interaction with Elasticsearch indices via the Model Context Protocol, exposing tools for listing indices, fetching mappings, performing searches, running ES|QL queries, and retrieving shard information.
by graphlit
Enables integration between MCP clients and the Graphlit platform, providing ingestion, extraction, retrieval, and RAG capabilities across a wide range of data sources and connectors.
by ihor-sokoliuk
Provides web search capabilities via the SearXNG API, exposing them through an MCP server for seamless integration with AI agents and tools.
by mamertofabian
Fast cross‑platform file searching leveraging the Everything SDK on Windows, Spotlight on macOS, and locate/plocate on Linux.
by spences10
Provides unified access to multiple search engines, AI response tools, and content processing services through a single Model Context Protocol server.
by cr7258
Provides Elasticsearch and OpenSearch interaction via Model Context Protocol, enabling document search, index management, cluster monitoring, and alias operations.
{
"mcpServers": {
"powertools": {
"command": "npx",
"args": [
"-y",
"powertools-for-aws-mcp"
],
"env": {}
}
}
}claude mcp add powertools npx -y powertools-for-aws-mcp