AWS Lambda Tool
AWS Labs' Lambda Tool MCP. Lets the agent invoke and inspect your Lambda functions as if they were native tools.
Delv Safety Grade: A
Score 83/100 · assessed 2026-04-18
AWS Lambda Tool is an official AWS Labs MCP server that exposes Lambda functions as Claude-native tools. The maintainer score is excellent given AWS's infrastructure and resources. Transparency is strong with open source code, clear documentation, and active AWS Labs backing. Supply chain is solid via PyPI distribution with uvx installation, though not as hardened as core AWS services. The permissions profile is the main concern: this grants arbitrary code execution through Lambda invocation, network access to AWS APIs, and credential access via AWS_PROFILE. While scoped to Lambda functions matching your prefix filter, it still allows the AI to invoke production serverless functions with real side effects. The tool requires careful configuration of FUNCTION_PREFIX to limit blast radius. Best suited for development and debugging workflows rather than production automation without additional guardrails.
Green flags
- Official AWS Labs project with institutional backing
- FUNCTION_PREFIX provides scope limitation mechanism
- Open source with clear documentation and examples
- Standard PyPI distribution via uvx
- Read-only inspection capabilities alongside invocation
Red flags
- Invokes real Lambda functions with potential production side effects
- Requires AWS credentials with Lambda:InvokeFunction permissions
- Arbitrary code execution via Lambda payload construction
- No built-in rate limiting or cost controls for invocations
Permissions requested
Install
uvx awslabs.lambda-tool-mcp-server@latest
AWS_REGIONAWS_PROFILEFUNCTION_PREFIXReview
Install this if you're running Lambda functions and want to test or orchestrate them from Claude without leaving chat. Skip it if you're not on AWS or if your functions are too critical to invoke casually. The best MCP server for AWS-native teams who want to move faster than the console allows.
Good at
- Turns Lambda functions into first-class Claude tools without writing custom MCP code.
- Prefix and tag filtering prevent the agent from seeing or invoking every function in your account.
- Maintained by AWS Labs, so it tracks API changes and boto3 updates reliably.
- Faster than the console or Postman for one-off Lambda tests and debugging.
- Works with any Claude host that supports MCP, not just desktop.
Watch out
- Assumes your AWS credentials are already configured. No hand-holding if your profile or region is wrong.
- Function inspection is metadata only. Claude can't see your code or debug logic errors.
- Dangerous if you point it at production Lambdas with side effects. No undo button.
- Hosts beyond Claude Desktop require manual config file edits, no GUI setup.
- Overkill if you're not already running serverless workloads on AWS.
Use cases
- Exposing internal microservices to Claude as tools
- Test-running a Lambda from chat
- Filtering by tag to scope what the agent sees
- Moving from Postman to natural language for ops
Getting started
Works with
Similar MCPs
- ESXi MCPManages VMware ESXi and vCenter for VM lifecycle and real-time performance monitoring via REST and SSE.
- TerraformHashiCorp's official Terraform MCP. Connects agents to the Terraform Registry for module discovery and infrastructure-as-code automation.
- HerokuHeroku's official MCP. Manage apps, databases, dynos, and pipelines through the platform CLI from inside an agent.
- AWS LabsAWS Labs ships a growing family of MCPs for S3, Lambda, EKS, CDK, etc. Modular install — pick the services you actually use.