Lambda MCP Server Demo (Streamable HTTP)

@rmavuluri

リポジトリ

基本情報

カテゴリ

クラウドとインフラ

ライセンス

MIT-0 license

トランスポート

stdio

作者

rmavuluri

Lambda MCP Server Demo について

概要はまだありません

#lambda-mcp-server#serverless #aws-lambda

Lambda MCP Server Demo の設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

Lambda MCP Server Demo のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Lambda MCP Server Demo (Streamable HTTP)?

This project demonstrates a developer-friendly way to create serverless MCP (Model Context Protocol) tools using AWS Lambda. It showcases a stateless, serverless MCP server with minimal boilerplate, and includes a TypeScript client that integrates with Amazon Bedrock Converse API using Amazon Nova Pro. It is designed for developers who want to deploy cloud-hosted MCP tools via Streamable HTTP.

How to use Lambda MCP Server Demo (Streamable HTTP)?

Install prerequisites (AWS account, AWS SAM CLI, Node.js, Docker, Python 3.9+, Amazon Bedrock access). Deploy the server with sam build then sam deploy --guided, providing an McpAuthToken. Navigate to the client directory and run run-client.sh. Add new tools using the @mcp_server.tool() decorator in server/app.py.

Key features of Lambda MCP Server Demo (Streamable HTTP)

Uses Streamable HTTP transport (not SSE).
Minimal boilerplate with decorator-based tool creation.
Built-in session state management via DynamoDB.
Bearer token authentication compliant with MCP standard.
Example tools: get_time, get_weather, count_s3_buckets.
Client integration with Amazon Bedrock Converse API.

Use cases of Lambda MCP Server Demo (Streamable HTTP)

Deploying serverless MCP agents with AWS Lambda.
Building stateless, session-aware MCP tools for cloud environments.
Demonstrating Streamable HTTP MCP communication with Bedrock.
Rapid prototyping of MCP tools with minimal setup and infrastructure.

よくある質問

What MCP clients support Streamable HTTP?

Very few MCP clients currently support Streamable HTTP. The included TypeScript client uses the TypeScript MCP SDK, which does support Streamable HTTP. For other clients, check compatibility.

What are the runtime dependencies and requirements?

Requires an AWS account, AWS SAM CLI, Node.js and npm, Docker, Python 3.9+, and access to Amazon Bedrock with Amazon Nova Pro enabled. The server is deployed via SAM; the client runs in Docker.

Where does session data live?

Session state is stored in a DynamoDB table against a `sessionId` key. This persistence is automatically managed across tool invocations within the same conversation.

Is this production ready?

No, this is a proof-of-concept implementation. The bearer token authentication is primarily for demonstration and development. For production, consider adding IAM roles, OAuth 2.0, or Amazon Cognito.

How does authentication work?

The server uses Bearer token authentication via an `Authorization` header. A custom authorizer in API Gateway validates the token. The client automatically includes the token when provided. The token is stored locally in `.mcp-api-token` (for convenience only, not production secure).

「クラウドとインフラ」の他のコンテンツ

Nippy

Nippy is drag-and-drop hosting (nippy.host) with an MCP server: connect it and your assistant can publish HTML, folders of photos, or file downloads to a live *.nippy.site URL — and keep editing the site in place at the

Dockhold

dockhold

Put the project you are working on online. Deploys the current folder or a GitHub repo to a live HTTPS URL on Dockhold; reads status and logs, sets variables, resizes apps and databases...

Terraform MCP Server

hashicorp

The Terraform MCP Server provides seamless integration with Terraform ecosystem, enabling advanced automation and interaction capabilities for Infrastructure as Code (IaC) development.

1.5K