PlugWiki
AWS Serverless MCP Server logo

AWS Serverless MCP Server: Setup for Claude, Cursor and Other Apps

OfficialLocal
GetPyPIawslabs.aws-serverless-mcp-serverawslabs/mcp/tree/main/src/aws-serverless-mcp-serverDocs

Lets Claude and Cursor build, test and deploy AWS Lambda and SAM apps, read-only until you switch on writes.

This is an AWS Labs server for serverless work. It runs on your computer with your own AWS credentials. It can start and build SAM projects, test Lambda functions locally, read logs and metrics, and deploy web apps to Lambda.

It starts read-only. You add one flag to allow deploys and another to allow log access. You also need the AWS SAM CLI, the AWS CLI, and Docker for local tests.

Good for

  • Developers building Lambda and SAM apps
  • Teams who want the assistant to deploy a web app to AWS Lambda
  • Engineers debugging a failing Lambda with logs and metrics

Works in

12 should work

Tap an app to see how to set it up and any known problems.

Install AWS Serverless MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the AWS Serverless MCP server to Claude Code. Run this command:
    
    claude mcp add aws-serverless -- uvx awslabs.aws-serverless-mcp-server
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires uv (Python).

Built from the package data we hold. Not yet tested by us.

Tools

  • Creates a new SAM project

    Starts a serverless project with the AWS SAM command line tool, with a template, runtime and folder layout.

    Try: “Create a Python SAM project called my-todo-app.”

    Write · sam_init

  • Builds a SAM app

    Compiles the Lambda code and prepares deployment files for a SAM project. It can build inside a container.

    Try: “Build the SAM app in this folder.”

    Runs code · sam_build

  • Deploys a SAM app to AWS

    Deploys the app to your AWS account through CloudFormation. It needs the write flag to be switched on.

    Try: “Deploy my-todo-app to us-east-1.”

    Write · sam_deploy

  • Fetches CloudWatch logs

    Returns logs for the resources in a SAM app to help debug failures. It is off until you allow sensitive data access.

    Try: “Show the last 30 minutes of logs for the API function.”

    Network · sam_logs

  • Runs a Lambda function locally

    Runs a function in a local Docker container that mimics Lambda, so you can test before deploying.

    Try: “Invoke the hello function locally with this event.”

    Runs code · sam_local_invoke

  • Helps choose SAM, CDK or CloudFormation

    Explains how to pick an infrastructure-as-code tool for a serverless deployment, with examples.

    Try: “Should I use SAM or CDK for this project?”

    Read · get_iac_guidance

  • Says whether Lambda fits your use case

    Returns a guide on when to choose Lambda, with pros, cons and decision criteria for your use case.

    Try: “Is Lambda a good fit for a nightly batch job?”

    Read · get_lambda_guidance

  • Gets Lambda event types by source and language

    Returns the event schema for a source such as S3, SQS or API Gateway, with types for your language.

    Try: “Give me the Python event type for an S3 trigger.”

    Read · get_lambda_event_schemas

  • Gets example SAM templates

    Returns example SAM templates from the Serverless Land GitHub repo.

    Try: “Show a SAM template for an SQS-triggered Lambda.”

    Network · get_serverless_templates

  • Explains how to deploy a Lambda app

    Gives the steps for deploying a Lambda application: templates, build, package and deploy.

    Try: “How do I deploy this Lambda app?”

    Read · deploy_serverless_app_help

  • Deploys a web app on Lambda

    Deploys a frontend, backend or full-stack web app on Lambda, API Gateway and CloudFront. It can create public resources and DNS records, and needs the write flag.

    Try: “Deploy my Node.js app as a full-stack site on AWS.”

    Write · deploy_webapp

  • Uploads new frontend files

    Uploads built frontend files to S3 and can clear the CloudFront cache. It needs the write flag.

    Try: “Push the new build to my deployed web app.”

    Write · update_webapp_frontend

From the official docs

Permissions

medium risk · 4 things to watch

Medium risk

With the write flag on, it can deploy stacks, create public resources such as CloudFront and DNS records, and run up AWS costs. Leave the flag off until you need it, and use an AWS role limited to what the task needs.

What it can do

Watch out for

  • Write mode can deploy and create public resources

    Deploys go through CloudFormation and can create CloudFront distributions and Route 53 records. Switch the write flag on only for a task, and review each deploy. raw.githubusercontent.com

  • Default mode still runs local commands and reads your AWS account

    Without the write flag the server cannot deploy, but sam_init writes project files, sam_build and sam_local_invoke run on your machine (local invoke uses Docker), and the schema and metrics tools read from your AWS account. raw.githubusercontent.com

  • It uses your AWS credentials

    Anything your profile can do, the deploy tools can attempt. The README advises a dedicated least-privilege role, tagging and CloudTrail. raw.githubusercontent.com

  • Logs can contain sensitive data

    The log tool is off by default and returns your Lambda and API Gateway logs when allowed. The server says it scrubs credentials and personal data, but check what you share. raw.githubusercontent.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details
Turning on read-onlyRead-only is the default. Add --allow-write to allow deploys and the ESM tools, and --allow-sensitive-data-access to allow logs. Both flags are in the README and the server source.
Talks toYour AWS account. Serverless Land (templates)
Sign-in and keysYour AWS credentials from a profile, or temporary keys, set as environment variables on your machine.

Questions

Is the AWS Serverless MCP server official?

Yes. It is published by AWS Labs, in the awslabs/mcp repository.

Can it run read-only?

Yes, and it does by default. It only changes AWS resources if you add the write flag, and only reads logs if you add the sensitive data flag.

What do I need installed?

An AWS account with credentials, uv, Python 3.10 or newer, the SAM CLI and the AWS CLI. Local function tests also need Docker. The install box covers the server itself.

Which AWS credentials does it use?

The default AWS profile, unless you set a profile name or temporary keys in the config. You can also set the AWS region, which defaults to us-east-1.

Can it deploy to production?

It can, with the write flag on. AWS says it can be used in production with read-only default, separate roles for read and write, and a human approving each tool call.

How many tools does it have?

25. The README documents 21 of them. The source also registers four IAM policy tools (secure_esm_msk_policy, secure_esm_sqs_policy, secure_esm_kinesis_policy, secure_esm_dynamodb_policy). The README also names esm_validate_configs and two other helpers, but those are actions inside esm_optimize, not separate tools.

Information

updated Nov 2, 2026

Publisher
Official
Package
awslabs.aws-serverless-mcp-server
Registry
PyPI
Transport
stdio
Auth
token in env
License
Apache-2.0
Last commit
Oct 30, 2026

DocsGitHubPyPI

Other AWS MCP servers

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 3
  1. raw.githubusercontent.com · raw.githubusercontent.com
  2. github.com · github.com
  3. github.com · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.