{"id":"awslabs-run-model-context-protocol-servers-with-aws-lambda","name":"run-model-context-protocol-servers-with-aws-lambda","af_score":54.8,"security_score":62.2,"reliability_score":27.5,"what_it_does":"Wraps existing Model Context Protocol (MCP) stdio-based servers so they can run inside AWS Lambda and be exposed to MCP clients via streamable HTTP (e.g., API Gateway or Bedrock AgentCore Gateway) or via Lambda function URL / direct Lambda invocation using AWS IAM authentication.","best_when":"You already have stdio-based MCP servers and want to operationalize them on AWS using short-lived Lambda execution while keeping compatibility with MCP streamable HTTP clients.","avoid_when":"You need extremely high throughput/very low latency per request (Lambda cold starts, process startup cost), or you cannot control/validate the subprocess command-line/runtime configuration.","last_evaluated":"2026-03-30T13:32:58.880339+00:00","has_mcp":true,"has_api":false,"auth_methods":["OAuth (via API Gateway / Bedrock AgentCore Gateway)","AWS IAM (via Lambda function URL with SigV4, or direct Lambda Invoke API)"],"has_free_tier":false,"known_gotchas":["Subprocess lifecycle is per invocation (startup/shutdown cost; cold starts may impact reliability/latency)","The wrapped MCP server will not automatically inherit Lambda role credentials; credentials must be passed via environment variables or credentials file when needed","Secrets/API keys are not managed by the library; misuse (broad IAM permissions or overly permissive invoke access) can expose third-party credentials","Packaging parameters for MCP stdio servers may require trial-and-error (command/args differ by server)"],"error_quality":0.0}