MCP.so
登录

MCP Lambda SAM

@markvp

基本信息

分类

云与基础设施

许可证

MIT

传输方式

stdio

作者

markvp

关于 MCP Lambda SAM

An AWS Serverless Application Model that operates as an MCP server via serverless AWS resources

MCP Lambda SAM 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "mcp-lambda-sam": {
      "command": "npx",
      "args": [
        "@markvp/mcp-lambda-sam",
        "deploy"
      ]
    }
  }
}

MCP Lambda SAM 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。

点击上方按钮,在临时沙箱中运行此服务器并实时获取工具列表。

概览

What is MCP Lambda SAM?

MCP Lambda SAM is a serverless implementation of the Model Context Protocol (MCP) using AWS Lambda and the Serverless Application Model (SAM). It provides two interfaces: an administrative interface for registering MCP tools, resources, and prompts, and a client interface for establishing SSE connections, sending commands, and receiving streaming responses.

How to use MCP Lambda SAM?

Deploy via npx @markvp/mcp-lambda-sam deploy, the AWS Serverless Application Repository, or programmatic install. After deployment, administrators register tools through a dedicated Lambda function URL with IAM authentication. Clients connect using AWS Signature V4 signed SSE requests, obtain a session ID, and then send JSON-RPC commands to the message endpoint.

Key features of MCP Lambda SAM

  • Serverless MCP implementation using AWS Lambda and SAM
  • Two interfaces: system administration and client usage
  • SSE streaming for real-time communication
  • DynamoDB tables for session and registration persistence
  • IAM-based authentication via Lambda Function URLs
  • Supports registration, update, deletion, and listing of tools/resources/prompts
  • Deploy via npx CLI, SAR, or local SAM commands

Use cases of MCP Lambda SAM

  • Administrators registering new MCP tools, resources, or prompts via the registration API
  • Clients establishing SSE connections to receive streaming responses from registered tools
  • Managing multiple server instances by providing different stack names
  • Deploying in a VPC for secure internal access

常见问题

1

What are the runtime requirements?

AWS CLI, AWS SAM CLI, Node.js 20.x or later, and an AWS account with permissions to create Lambda functions, DynamoDB tables, IAM roles, and SQS queues.

2

How do I deploy MCP Lambda SAM?

You can deploy using `npx @markvp/mcp-lambda-sam deploy`, from the AWS Serverless Application Repository (search “mcp-lambda-sam”), programmatically by installing the npm package, or locally with `sam build` and `sam deploy --guided`.

3

How does authentication work?

All MCP endpoints are IAM-protected via Lambda Function URLs with `AWS_IAM` auth type. Administrators need permission to invoke the registration function URL; clients need permission to invoke the MCP function URL. Permissions are granted using IAM policies or `aws lambda add-permission` commands.

4

How do I register a tool or resource?

Send an HTTP POST request to the registration function URL with JSON body containing `type`, `name`, `description`, `lambdaArn`, and `parameters`. Use `awscurl` or any client capable of AWS Signature V4 signing.

5

What common errors can occur?

401 (invalid/missing credentials), 403 (insufficient permissions), 404 (invalid session ID), and 429 (rate limit exceeded). Troubleshooting includes verifying credentials, IAM permissions, session ID validity, and command format.

评论

云与基础设施 分类下的更多 MCP 服务器