MCP on AWS Bedrock
A simple and clear example for implementation and understanding Anthropic MCP (on AWS Bedrock).
For multiple MCP servers management, this tiny project Q-2001 could be referred~
Overview
This project demonstrates how to implement and use Anthropic's Model Context Protocol (MCP) with AWS Bedrock. It provides a client implementation that can interact with MCP-enabled tools through AWS Bedrock's runtime service.
Updates 2025-05-10: Streamable HTTP
- Add support for Streamable HTTP
- Rewrite the URL fetching MCP server
fetch_url_mcp_server.pythat demonstrates different transport types
Usage Instructions
Run the server with default stdio settings (no transport parameter):
uv run fetch_url_mcp_server.py
# client
uv run client_stdio.py
Run with streamable-http transport on default port (8000):
python fetch_url_mcp_server.py --transport streamable-http
# client
uv run client_streamablehttp.py
Run with streamable-http transport on custom port:
python fetch_url_mcp_server.py --transport streamable-http --port 8080
Prerequisites
- Python 3.10 or higher
- AWS account with Bedrock access
- Configured AWS credentials
- UV package manager
Features
- Seamless integration with AWS Bedrock runtime using Converse API
- Tool format conversion for Bedrock compatibility
- Asynchronous communication handling
- Structured logging for debugging
Contributing
Feel free to submit issues and pull requests to improve the implementation.
License
MIT License
References
Metadata
Release files for iflow-mcp_davidshtian-mcp-on-aws-bedrock 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_davidshtian_mcp_on_aws_bedrock-0.1.0.tar.gz | 4.7 kB | Without provenance | Details for iflow_mcp_davidshtian_mcp_on_aws_bedrock-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_davidshtian_mcp_on_aws_bedrock-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_davidshtian_mcp_on_aws_bedrock-0.1.0-py3-none-any.whl |
Total release size: 16.6 kB
Release files / iflow_mcp_davidshtian_mcp_on_aws_bedrock-0.1.0.tar.gz
| Download URL | iflow_mcp_davidshtian_mcp_on_aws_bedrock-0.1.0.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4d279dad60e977fd8e9ed2705880f6040785e2aa2270d07d1db2c8885ff4054f
|
|
BLAKE2b-256 checksum How to use checksums |
9e700b7ba01bddb407bf342a13b02c2a88a388af261799a1ef1d506566eed53b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.0 {"installer":{"name":"uv","version":"0.10.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / iflow_mcp_davidshtian_mcp_on_aws_bedrock-0.1.0-py3-none-any.whl
| Download URL | iflow_mcp_davidshtian_mcp_on_aws_bedrock-0.1.0-py3-none-any.whl |
|---|---|
| Size | 11.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3a679521204ce4b8ad5e1e903b9668e12acd7d87b835af0b19724c2737e3143b
|
|
BLAKE2b-256 checksum How to use checksums |
feaeb94c49c0b6716ec85551a8a121057c8ab9e786670a197b8eb4ee4350f665
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.0 {"installer":{"name":"uv","version":"0.10.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for iflow-mcp_davidshtian-mcp-on-aws-bedrock 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.