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.
@rmavuluri
Basic information
No overview available yet
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
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.
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.
get_time, get_weather, count_s3_buckets.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.
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.
Session state is stored in a DynamoDB table against a `sessionId` key. This persistence is automatically managed across tool invocations within the same conversation.
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.
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).
Find, price and rent GPUs on Lium from Claude, ChatGPT, Codex or any MCP client. Search live GPU availability and prices (H100, H200, B200, RTX 4090 and more), estimate provider earnings, and with Sign in with Lium or a
Query MCP enables end-to-end management of Supabase via chat interface: read & write query executions, management API support, automatic migration versioning, access to logs and much more.
An MCP server for Azure DevOps
MCP server for Backblaze B2 Cloud Storage: a focused, safe 40-tool surface (17 native B2 SDK, 19 S3 data-plane, 4 analytics) for any MCP-compatible AI client, currently incubating in Backblaze-Labs
Connect Supabase to your AI assistants
Comments