An AWS Serverless Application Model that operates as an MCP server via serverless AWS resources
MCP Lambda SAM MCP server exists for a simple reason — assistants are far more useful when they can act on MCP Lambda SAM directly instead of describing what you should do. An AWS Serverless Application Model that operates as an MCP server via serverless AWS resources.
Model Context Protocol (MCP) implementation using AWS Lambda and SAM.
This project provides a serverless implementation of the Model Context Protocol, with two distinct interfaces:
Once MCP Lambda SAM is connected, these are the calls the assistant has available:
Deployment — The command will interactively prompt for administrative configuration: - Stack name (for multiple instances) - AWS Region - VPC configurationTroubleshooting — 1. Connection Issues: - Verify AWS credentials - Check IAM permissions - Ensure network connectivityYou will need one environment variable: REGISTRATION_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
@markvp/mcp-lambda-sam on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Lambda SAM's toolset — Deployment, Troubleshooting — is a fair guide to whether it matches your workflow. It is maintained by markvp; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Deployment | The command will interactively prompt for administrative configuration: - Stack name (for multiple instances) - AWS Region - VPC configuration (optional) |
| Troubleshooting | 1. **Connection Issues**: - Verify AWS credentials - Check IAM permissions - Ensure network connectivity |
{
"mcpServers": {
"lambda-sam": {
"command": "npx",
"args": ["-y", "@markvp/mcp-lambda-sam"],
"env": {
"REGISTRATION_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| REGISTRATION_URL | Endpoint or connection string the server talks to. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.