awslabs.lambda-tool-mcp-server 2.0.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (33) hide show
  1. awslabs_lambda_tool_mcp_server-2.0.0/.gitignore +59 -0
  2. awslabs_lambda_tool_mcp_server-2.0.0/.pre-commit-config.yaml +14 -0
  3. awslabs_lambda_tool_mcp_server-2.0.0/.python-version +1 -0
  4. awslabs_lambda_tool_mcp_server-2.0.0/CHANGELOG.md +19 -0
  5. awslabs_lambda_tool_mcp_server-2.0.0/Dockerfile +75 -0
  6. awslabs_lambda_tool_mcp_server-2.0.0/LICENSE +175 -0
  7. awslabs_lambda_tool_mcp_server-2.0.0/NOTICE +2 -0
  8. awslabs_lambda_tool_mcp_server-2.0.0/PKG-INFO +191 -0
  9. awslabs_lambda_tool_mcp_server-2.0.0/README.md +163 -0
  10. awslabs_lambda_tool_mcp_server-2.0.0/awslabs/__init__.py +2 -0
  11. awslabs_lambda_tool_mcp_server-2.0.0/awslabs/lambda_tool_mcp_server/__init__.py +3 -0
  12. awslabs_lambda_tool_mcp_server-2.0.0/awslabs/lambda_tool_mcp_server/server.py +308 -0
  13. awslabs_lambda_tool_mcp_server-2.0.0/docker-healthcheck.sh +12 -0
  14. awslabs_lambda_tool_mcp_server-2.0.0/examples/README.md +80 -0
  15. awslabs_lambda_tool_mcp_server-2.0.0/examples/sample_functions/customer-create/app.py +62 -0
  16. awslabs_lambda_tool_mcp_server-2.0.0/examples/sample_functions/customer-id-from-email/app.py +31 -0
  17. awslabs_lambda_tool_mcp_server-2.0.0/examples/sample_functions/customer-info-from-id/app.py +58 -0
  18. awslabs_lambda_tool_mcp_server-2.0.0/examples/sample_functions/template.yml +154 -0
  19. awslabs_lambda_tool_mcp_server-2.0.0/pyproject.toml +130 -0
  20. awslabs_lambda_tool_mcp_server-2.0.0/run_tests.sh +158 -0
  21. awslabs_lambda_tool_mcp_server-2.0.0/tests/.gitignore +25 -0
  22. awslabs_lambda_tool_mcp_server-2.0.0/tests/README.md +105 -0
  23. awslabs_lambda_tool_mcp_server-2.0.0/tests/__init__.py +1 -0
  24. awslabs_lambda_tool_mcp_server-2.0.0/tests/conftest.py +86 -0
  25. awslabs_lambda_tool_mcp_server-2.0.0/tests/test_format_lambda_response.py +23 -0
  26. awslabs_lambda_tool_mcp_server-2.0.0/tests/test_integration.py +160 -0
  27. awslabs_lambda_tool_mcp_server-2.0.0/tests/test_integration_coverage.py +127 -0
  28. awslabs_lambda_tool_mcp_server-2.0.0/tests/test_register_lambda_functions.py +54 -0
  29. awslabs_lambda_tool_mcp_server-2.0.0/tests/test_schema_integration.py +251 -0
  30. awslabs_lambda_tool_mcp_server-2.0.0/tests/test_server.py +452 -0
  31. awslabs_lambda_tool_mcp_server-2.0.0/tests/test_server_coverage.py +166 -0
  32. awslabs_lambda_tool_mcp_server-2.0.0/tests/test_server_coverage_additional.py +43 -0
  33. awslabs_lambda_tool_mcp_server-2.0.0/uv.lock +1100 -0
@@ -0,0 +1,59 @@
1
+ # Python
2
+ __pycache__/
3
+ *.py[cod]
4
+ *$py.class
5
+ *.so
6
+ .Python
7
+ build/
8
+ develop-eggs/
9
+ dist/
10
+ downloads/
11
+ eggs/
12
+ .eggs/
13
+ lib/
14
+ lib64/
15
+ parts/
16
+ sdist/
17
+ var/
18
+ wheels/
19
+ share/python-wheels/
20
+ *.egg-info/
21
+ .installed.cfg
22
+ *.egg
23
+ MANIFEST
24
+
25
+ # Virtual environments
26
+ .venv
27
+ env/
28
+ venv/
29
+ ENV/
30
+
31
+ # IDE
32
+ .idea/
33
+ .vscode/
34
+ *.swp
35
+ *.swo
36
+
37
+ # Testing
38
+ .tox/
39
+ .coverage
40
+ .coverage.*
41
+ htmlcov/
42
+ .pytest_cache/
43
+
44
+ # Ruff
45
+ .ruff_cache/
46
+
47
+ # Build
48
+ *.manifest
49
+ *.spec
50
+ .pybuilder/
51
+ target/
52
+
53
+ # Environments
54
+ .env
55
+ .env.local
56
+ .env.*.local
57
+
58
+ # PyPI
59
+ .pypirc
@@ -0,0 +1,14 @@
1
+ repos:
2
+ - repo: https://github.com/astral-sh/ruff-pre-commit
3
+ rev: v0.9.6
4
+ hooks:
5
+ - id: ruff
6
+ args: [--fix]
7
+ - id: ruff-format
8
+
9
+ - repo: https://github.com/commitizen-tools/commitizen
10
+ rev: v3.13.0
11
+ hooks:
12
+ - id: commitizen
13
+ - id: commitizen-branch
14
+ stages: [push]
@@ -0,0 +1,19 @@
1
+ # Changelog
2
+
3
+ All notable changes to this project will be documented in this file.
4
+
5
+ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
+ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
+
8
+ ## [1.0.0] - 2025-05-26
9
+
10
+ ### Removed
11
+
12
+ - **BREAKING CHANGE:** Server Sent Events (SSE) support has been removed in accordance with the Model Context Protocol specification's [backwards compatibility guidelines](https://modelcontextprotocol.io/specification/2025-03-26/basic/transports#backwards-compatibility)
13
+ - This change prepares for future support of [Streamable HTTP](https://modelcontextprotocol.io/specification/draft/basic/transports#streamable-http) transport
14
+
15
+ ## Unreleased
16
+
17
+ ### Added
18
+
19
+ - Initial project setup
@@ -0,0 +1,75 @@
1
+ # Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
2
+ #
3
+ # Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance
4
+ # with the License. A copy of the License is located at
5
+ #
6
+ # http://www.apache.org/licenses/LICENSE-2.0
7
+ #
8
+ # or in the 'license' file accompanying this file. This file is distributed on an 'AS IS' BASIS, WITHOUT WARRANTIES
9
+ # OR CONDITIONS OF ANY KIND, express or implied. See the License for the specific language governing permissions
10
+ # and limitations under the License.
11
+
12
+ #FROM public.ecr.aws/sam/build-python3.10:1.137.1-20250411084548
13
+ FROM public.ecr.aws/sam/build-python3.10@sha256:e78695db10ca8cb129e59e30f7dc9789b0dbd0181dba195d68419c72bac51ac1 AS uv
14
+
15
+ # Install the project into `/app`
16
+ WORKDIR /app
17
+
18
+ # Enable bytecode compilation
19
+ ENV UV_COMPILE_BYTECODE=1
20
+
21
+ # Copy from the cache instead of linking since it's a mounted volume
22
+ ENV UV_LINK_MODE=copy
23
+
24
+ # Prefer the system python
25
+ ENV UV_PYTHON_PREFERENCE=only-system
26
+
27
+ # Run without updating the uv.lock file like running with `--frozen`
28
+ ENV UV_FROZEN=true
29
+
30
+ # Copy the required files first
31
+ COPY pyproject.toml uv.lock ./
32
+
33
+ # Install the project's dependencies using the lockfile and settings
34
+ RUN --mount=type=cache,target=/root/.cache/uv \
35
+ pip install uv && \
36
+ uv sync --frozen --no-install-project --no-dev --no-editable
37
+
38
+ # Then, add the rest of the project source code and install it
39
+ # Installing separately from its dependencies allows optimal layer caching
40
+ COPY . /app
41
+ RUN --mount=type=cache,target=/root/.cache/uv \
42
+ uv sync --frozen --no-dev --no-editable
43
+
44
+ # Make the directory just in case it doesn't exist
45
+ RUN mkdir -p /root/.local
46
+
47
+ FROM public.ecr.aws/sam/build-python3.10@sha256:e78695db10ca8cb129e59e30f7dc9789b0dbd0181dba195d68419c72bac51ac1
48
+
49
+ # Place executables in the environment at the front of the path and include other binaries
50
+ ENV PATH="/app/.venv/bin:$PATH:/usr/sbin"
51
+
52
+ # Install lsof for the healthcheck
53
+ # Install other tools as needed for the MCP server
54
+ # Add non-root user and ability to change directory into /root
55
+ RUN yum update -y && \
56
+ yum install -y lsof && \
57
+ yum clean all -y && \
58
+ rm -rf /var/cache/yum && \
59
+ groupadd --force --system app && \
60
+ useradd app -g app -d /app && \
61
+ chmod o+x /root
62
+
63
+ # Get the project from the uv layer
64
+ COPY --from=uv --chown=app:app /root/.local /root/.local
65
+ COPY --from=uv --chown=app:app /app/.venv /app/.venv
66
+
67
+ # Get healthcheck script
68
+ COPY ./docker-healthcheck.sh /usr/local/bin/docker-healthcheck.sh
69
+
70
+ # Run as non-root
71
+ USER app
72
+
73
+ # When running the container, add --db-path and a bind mount to the host's db file
74
+ HEALTHCHECK --interval=30s --timeout=30s --start-period=5s --retries=3 CMD [ "docker-healthcheck.sh" ]
75
+ ENTRYPOINT ["awslabs.lambda-tool-mcp-server"]
@@ -0,0 +1,175 @@
1
+
2
+ Apache License
3
+ Version 2.0, January 2004
4
+ http://www.apache.org/licenses/
5
+
6
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7
+
8
+ 1. Definitions.
9
+
10
+ "License" shall mean the terms and conditions for use, reproduction,
11
+ and distribution as defined by Sections 1 through 9 of this document.
12
+
13
+ "Licensor" shall mean the copyright owner or entity authorized by
14
+ the copyright owner that is granting the License.
15
+
16
+ "Legal Entity" shall mean the union of the acting entity and all
17
+ other entities that control, are controlled by, or are under common
18
+ control with that entity. For the purposes of this definition,
19
+ "control" means (i) the power, direct or indirect, to cause the
20
+ direction or management of such entity, whether by contract or
21
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
22
+ outstanding shares, or (iii) beneficial ownership of such entity.
23
+
24
+ "You" (or "Your") shall mean an individual or Legal Entity
25
+ exercising permissions granted by this License.
26
+
27
+ "Source" form shall mean the preferred form for making modifications,
28
+ including but not limited to software source code, documentation
29
+ source, and configuration files.
30
+
31
+ "Object" form shall mean any form resulting from mechanical
32
+ transformation or translation of a Source form, including but
33
+ not limited to compiled object code, generated documentation,
34
+ and conversions to other media types.
35
+
36
+ "Work" shall mean the work of authorship, whether in Source or
37
+ Object form, made available under the License, as indicated by a
38
+ copyright notice that is included in or attached to the work
39
+ (an example is provided in the Appendix below).
40
+
41
+ "Derivative Works" shall mean any work, whether in Source or Object
42
+ form, that is based on (or derived from) the Work and for which the
43
+ editorial revisions, annotations, elaborations, or other modifications
44
+ represent, as a whole, an original work of authorship. For the purposes
45
+ of this License, Derivative Works shall not include works that remain
46
+ separable from, or merely link (or bind by name) to the interfaces of,
47
+ the Work and Derivative Works thereof.
48
+
49
+ "Contribution" shall mean any work of authorship, including
50
+ the original version of the Work and any modifications or additions
51
+ to that Work or Derivative Works thereof, that is intentionally
52
+ submitted to Licensor for inclusion in the Work by the copyright owner
53
+ or by an individual or Legal Entity authorized to submit on behalf of
54
+ the copyright owner. For the purposes of this definition, "submitted"
55
+ means any form of electronic, verbal, or written communication sent
56
+ to the Licensor or its representatives, including but not limited to
57
+ communication on electronic mailing lists, source code control systems,
58
+ and issue tracking systems that are managed by, or on behalf of, the
59
+ Licensor for the purpose of discussing and improving the Work, but
60
+ excluding communication that is conspicuously marked or otherwise
61
+ designated in writing by the copyright owner as "Not a Contribution."
62
+
63
+ "Contributor" shall mean Licensor and any individual or Legal Entity
64
+ on behalf of whom a Contribution has been received by Licensor and
65
+ subsequently incorporated within the Work.
66
+
67
+ 2. Grant of Copyright License. Subject to the terms and conditions of
68
+ this License, each Contributor hereby grants to You a perpetual,
69
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70
+ copyright license to reproduce, prepare Derivative Works of,
71
+ publicly display, publicly perform, sublicense, and distribute the
72
+ Work and such Derivative Works in Source or Object form.
73
+
74
+ 3. Grant of Patent License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ (except as stated in this section) patent license to make, have made,
78
+ use, offer to sell, sell, import, and otherwise transfer the Work,
79
+ where such license applies only to those patent claims licensable
80
+ by such Contributor that are necessarily infringed by their
81
+ Contribution(s) alone or by combination of their Contribution(s)
82
+ with the Work to which such Contribution(s) was submitted. If You
83
+ institute patent litigation against any entity (including a
84
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
85
+ or a Contribution incorporated within the Work constitutes direct
86
+ or contributory patent infringement, then any patent licenses
87
+ granted to You under this License for that Work shall terminate
88
+ as of the date such litigation is filed.
89
+
90
+ 4. Redistribution. You may reproduce and distribute copies of the
91
+ Work or Derivative Works thereof in any medium, with or without
92
+ modifications, and in Source or Object form, provided that You
93
+ meet the following conditions:
94
+
95
+ (a) You must give any other recipients of the Work or
96
+ Derivative Works a copy of this License; and
97
+
98
+ (b) You must cause any modified files to carry prominent notices
99
+ stating that You changed the files; and
100
+
101
+ (c) You must retain, in the Source form of any Derivative Works
102
+ that You distribute, all copyright, patent, trademark, and
103
+ attribution notices from the Source form of the Work,
104
+ excluding those notices that do not pertain to any part of
105
+ the Derivative Works; and
106
+
107
+ (d) If the Work includes a "NOTICE" text file as part of its
108
+ distribution, then any Derivative Works that You distribute must
109
+ include a readable copy of the attribution notices contained
110
+ within such NOTICE file, excluding those notices that do not
111
+ pertain to any part of the Derivative Works, in at least one
112
+ of the following places: within a NOTICE text file distributed
113
+ as part of the Derivative Works; within the Source form or
114
+ documentation, if provided along with the Derivative Works; or,
115
+ within a display generated by the Derivative Works, if and
116
+ wherever such third-party notices normally appear. The contents
117
+ of the NOTICE file are for informational purposes only and
118
+ do not modify the License. You may add Your own attribution
119
+ notices within Derivative Works that You distribute, alongside
120
+ or as an addendum to the NOTICE text from the Work, provided
121
+ that such additional attribution notices cannot be construed
122
+ as modifying the License.
123
+
124
+ You may add Your own copyright statement to Your modifications and
125
+ may provide additional or different license terms and conditions
126
+ for use, reproduction, or distribution of Your modifications, or
127
+ for any such Derivative Works as a whole, provided Your use,
128
+ reproduction, and distribution of the Work otherwise complies with
129
+ the conditions stated in this License.
130
+
131
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
132
+ any Contribution intentionally submitted for inclusion in the Work
133
+ by You to the Licensor shall be under the terms and conditions of
134
+ this License, without any additional terms or conditions.
135
+ Notwithstanding the above, nothing herein shall supersede or modify
136
+ the terms of any separate license agreement you may have executed
137
+ with Licensor regarding such Contributions.
138
+
139
+ 6. Trademarks. This License does not grant permission to use the trade
140
+ names, trademarks, service marks, or product names of the Licensor,
141
+ except as required for reasonable and customary use in describing the
142
+ origin of the Work and reproducing the content of the NOTICE file.
143
+
144
+ 7. Disclaimer of Warranty. Unless required by applicable law or
145
+ agreed to in writing, Licensor provides the Work (and each
146
+ Contributor provides its Contributions) on an "AS IS" BASIS,
147
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148
+ implied, including, without limitation, any warranties or conditions
149
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150
+ PARTICULAR PURPOSE. You are solely responsible for determining the
151
+ appropriateness of using or redistributing the Work and assume any
152
+ risks associated with Your exercise of permissions under this License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor
164
+ has been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf
172
+ of any other Contributor, and only if You agree to indemnify,
173
+ defend, and hold each Contributor harmless for any liability
174
+ incurred by, or claims asserted against, such Contributor by reason
175
+ of your accepting any such warranty or additional liability.
@@ -0,0 +1,2 @@
1
+ awslabs.lambda-tool-mcp-server
2
+ Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
@@ -0,0 +1,191 @@
1
+ Metadata-Version: 2.4
2
+ Name: awslabs.lambda-tool-mcp-server
3
+ Version: 2.0.0
4
+ Summary: An AWS Labs Model Context Protocol (MCP) server for AWS Lambda Tools
5
+ Project-URL: Homepage, https://awslabs.github.io/mcp/
6
+ Project-URL: Documentation, https://awslabs.github.io/mcp/servers/lambda-tool-mcp-server/
7
+ Project-URL: Source, https://github.com/awslabs/mcp.git
8
+ Project-URL: Bug Tracker, https://github.com/awslabs/mcp/issues
9
+ Project-URL: Changelog, https://github.com/awslabs/mcp/blob/main/src/lambda-tool-mcp-server/CHANGELOG.md
10
+ Author: Amazon Web Services
11
+ Author-email: AWSLabs MCP <203918161+awslabs-mcp@users.noreply.github.com>
12
+ License: Apache-2.0
13
+ License-File: LICENSE
14
+ License-File: NOTICE
15
+ Classifier: License :: OSI Approved :: Apache Software License
16
+ Classifier: Operating System :: OS Independent
17
+ Classifier: Programming Language :: Python
18
+ Classifier: Programming Language :: Python :: 3
19
+ Classifier: Programming Language :: Python :: 3.10
20
+ Classifier: Programming Language :: Python :: 3.11
21
+ Classifier: Programming Language :: Python :: 3.12
22
+ Classifier: Programming Language :: Python :: 3.13
23
+ Requires-Python: >=3.10
24
+ Requires-Dist: boto3>=1.37.27
25
+ Requires-Dist: mcp[cli]>=1.6.0
26
+ Requires-Dist: pydantic>=2.10.6
27
+ Description-Content-Type: text/markdown
28
+
29
+ # AWS Lambda Tool MCP Server
30
+
31
+ A Model Context Protocol (MCP) server for AWS Lambda to select and run Lambda function as MCP tools without code changes.
32
+
33
+ ## Features
34
+
35
+ This MCP server acts as a **bridge** between MCP clients and AWS Lambda functions, allowing generative AI models to access and run Lambda functions as tools. This is useful, for example, to access private resources such as internal applications and databases without the need to provide public network access. This approach allows the model to use other AWS services, private networks, and the public internet.
36
+
37
+ ```mermaid
38
+ graph LR
39
+ A[Model] <--> B[MCP Client]
40
+ B <--> C["MCP2Lambda<br>(MCP Server)"]
41
+ C <--> D[Lambda Function]
42
+ D <--> E[Other AWS Services]
43
+ D <--> F[Internet]
44
+ D <--> G[VPC]
45
+
46
+ style A fill:#f9f,stroke:#333,stroke-width:2px
47
+ style B fill:#bbf,stroke:#333,stroke-width:2px
48
+ style C fill:#bfb,stroke:#333,stroke-width:4px
49
+ style D fill:#fbb,stroke:#333,stroke-width:2px
50
+ style E fill:#fbf,stroke:#333,stroke-width:2px
51
+ style F fill:#dff,stroke:#333,stroke-width:2px
52
+ style G fill:#ffd,stroke:#333,stroke-width:2px
53
+ ```
54
+
55
+ From a **security** perspective, this approach implements segregation of duties by allowing the model to invoke the Lambda functions but not to access the other AWS services directly. The client only needs AWS credentials to invoke the Lambda functions. The Lambda functions can then interact with other AWS services (using the function role) and access public or private networks.
56
+
57
+ ## Prerequisites
58
+
59
+ 1. Install `uv` from [Astral](https://docs.astral.sh/uv/getting-started/installation/) or the [GitHub README](https://github.com/astral-sh/uv#installation)
60
+ 2. Install Python using `uv python install 3.10`
61
+
62
+ ## Installation
63
+
64
+ Here are some ways you can work with MCP across AWS, and we'll be adding support to more products including Amazon Q Developer CLI soon: (e.g. for Amazon Q Developer CLI MCP, `~/.aws/amazonq/mcp.json`):
65
+
66
+ ```json
67
+ {
68
+ "mcpServers": {
69
+ "awslabs.lambda-tool-mcp-server": {
70
+ "command": "uvx",
71
+ "args": ["awslabs.lambda-tool-mcp-server@latest"],
72
+ "env": {
73
+ "AWS_PROFILE": "your-aws-profile",
74
+ "AWS_REGION": "us-east-1",
75
+ "FUNCTION_PREFIX": "your-function-prefix",
76
+ "FUNCTION_LIST": "your-first-function, your-second-function",
77
+ "FUNCTION_TAG_KEY": "your-tag-key",
78
+ "FUNCTION_TAG_VALUE": "your-tag-value",
79
+ "FUNCTION_INPUT_SCHEMA_ARN_TAG_KEY": "your-function-tag-for-input-schema"
80
+ }
81
+ }
82
+ }
83
+ }
84
+ ```
85
+
86
+ or docker after a successful `docker build -t awslabs/bedrock-kb-retrieval-mcp-server .`:
87
+
88
+ ```file
89
+ # fictitious `.env` file with AWS temporary credentials
90
+ AWS_ACCESS_KEY_ID=ASIAIOSFODNN7EXAMPLE
91
+ AWS_SECRET_ACCESS_KEY=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
92
+ AWS_SESSION_TOKEN=AQoEXAMPLEH4aoAH0gNCAPy...truncated...zrkuWJOgQs8IZZaIv2BXIa2R4Olgk
93
+ ```
94
+
95
+ ```json
96
+ {
97
+ "mcpServers": {
98
+ "awslabs.lambda-tool-mcp-server": {
99
+ "command": "docker",
100
+ "args": [
101
+ "run",
102
+ "--rm",
103
+ "--interactive",
104
+ "--env",
105
+ "AWS_REGION=us-east-1",
106
+ "--env",
107
+ "FUNCTION_PREFIX=your-function-prefix",
108
+ "--env",
109
+ "FUNCTION_LIST=your-first-function,your-second-function",
110
+ "--env",
111
+ "FUNCTION_TAG_KEY=your-tag-key",
112
+ "--env",
113
+ "FUNCTION_TAG_VALUE=your-tag-value",
114
+ "--env",
115
+ "FUNCTION_INPUT_SCHEMA_ARN_TAG_KEY=your-function-tag-for-input-schema",
116
+ "--env-file",
117
+ "/full/path/to/file/above/.env",
118
+ "awslabs/lambda-tool-mcp-server:latest"
119
+ ],
120
+ "env": {},
121
+ "disabled": false,
122
+ "autoApprove": []
123
+ }
124
+ }
125
+ }
126
+ ```
127
+
128
+ NOTE: Your credentials will need to be kept refreshed from your host
129
+
130
+ The `AWS_PROFILE` and the `AWS_REGION` are optional, their default values are `default` and `us-east-1`.
131
+
132
+ You can specify `FUNCTION_PREFIX`, `FUNCTION_LIST`, or both. If both are empty, all functions pass the name check.
133
+ After the name check, if both `FUNCTION_TAG_KEY` and `FUNCTION_TAG_VALUE` are set, functions are further filtered by tag (with key=value).
134
+ If only one of `FUNCTION_TAG_KEY` and `FUNCTION_TAG_VALUE`, then no function is selected and a warning is displayed.
135
+
136
+ **IMPORTANT**: The function name is used as MCP tool name. The function description in AWS Lambda is used as MCP tool description. The function description should clarify when to use the function (what it provides) and how (which parameters). For example, a function that gives access to an internal Customer Relationship Management (CRM) system can use this description:
137
+ ```plaintext
138
+ Retrieve customer status on the CRM system based on { 'customerId' } or { 'customerEmail' }
139
+ ```
140
+
141
+ The lambda function parameters can also be provided through the EventBridge Schema Registry, which provides formal JSON Schema. See [Schema Support](#schema-support) below.
142
+
143
+ Sample functions that can be deployed via AWS SAM are provided in the `examples` folder.
144
+
145
+ ## Schema Support
146
+
147
+ The Lambda MCP Server supports input schema through AWS EventBridge Schema Registry. This provides formal JSON Schema documentation for your Lambda function inputs.
148
+
149
+ ### Configuration
150
+
151
+ To use schema validation:
152
+
153
+ 1. Create your schema in EventBridge Schema Registry
154
+ 2. Tag your Lambda function with the schema ARN:
155
+ ```plaintext
156
+ Key: FUNCTION_INPUT_SCHEMA_ARN_TAG_KEY (configurable)
157
+ Value: arn:aws:schemas:region:account:schema/registry-name/schema-name
158
+ ```
159
+ 3. Configure the MCP server with the tag key:
160
+ ```json
161
+ {
162
+ "env": {
163
+ "FUNCTION_INPUT_SCHEMA_ARN_TAG_KEY": "your-schema-arn-tag-key"
164
+ }
165
+ }
166
+ ```
167
+
168
+ When a Lambda function has a schema tag, the MCP server will:
169
+ 1. Fetch the schema from EventBridge Schema Registry
170
+ 2. Add the schema to the tool's documentation
171
+
172
+ This provides better documentation compared to describing parameters in the function description.
173
+
174
+ ## Best practices
175
+
176
+ - Use the `FUNCTION_LIST` to specify the functions that are available as MCP tools.
177
+ - Use the `FUNCTION_PREFIX` to specify the prefix of the functions that are available as MCP tools.
178
+ - Use the `FUNCTION_TAG_KEY` and `FUNCTION_TAG_VALUE` to specify the tag key and value of the functions that are available as MCP tools.
179
+ - AWS Lambda `Description` property: the description of the function is used as MCP tool description, so it should be very detailed to help the model understand when and how to use the function
180
+ - Use EventBridge Schema Registry to provide formal input validation:
181
+ - Create JSON Schema definitions for your function inputs
182
+ - Tag functions with their schema ARNs
183
+ - Configure `FUNCTION_INPUT_SCHEMA_ARN_TAG_KEY` in the MCP server
184
+
185
+ ## Security Considerations
186
+
187
+ When using this MCP server, you should consider:
188
+
189
+ - Only Lambda functions that are in the provided list or with a name starting with the prefix are imported as MCP tools.
190
+ - The MCP server needs permissions to invoke the Lambda functions.
191
+ - Each Lambda function has its own permissions to optionally access other AWS resources.