@aws/run-mcp-servers-with-aws-lambda 0.3.3 → 0.3.5

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 (2) hide show
  1. package/README.md +4 -4
  2. package/package.json +11 -11
package/README.md CHANGED
@@ -49,7 +49,7 @@ This library supports connecting to Lambda-based MCP servers in three ways:
49
49
  2. A custom Streamable HTTP transport with support for SigV4, using a Lambda function URL. Authenticated with AWS IAM.
50
50
  3. A custom Lambda invocation transport, using the Lambda Invoke API directly. Authenticated with AWS IAM.
51
51
 
52
- ## Using API Gateway
52
+ ## Use API Gateway
53
53
 
54
54
  ```mermaid
55
55
  flowchart LR
@@ -206,7 +206,7 @@ See a full example as part of the sample chatbot [here](examples/chatbots/typesc
206
206
 
207
207
  </details>
208
208
 
209
- ## Using a Lambda function URL
209
+ ## Use a Lambda function URL
210
210
 
211
211
  ```mermaid
212
212
  flowchart LR
@@ -358,7 +358,7 @@ See a full example as part of the sample chatbot [here](examples/chatbots/typesc
358
358
 
359
359
  </details>
360
360
 
361
- ## Using the Lambda Invoke API
361
+ ## Use the Lambda Invoke API
362
362
 
363
363
  ```mermaid
364
364
  flowchart LR
@@ -506,7 +506,7 @@ See a full example as part of the sample chatbot [here](examples/chatbots/typesc
506
506
  Other languages such as Kotlin are not supported.
507
507
  - This library only adapts stdio MCP servers for Lambda, not servers written for other protocols such as SSE.
508
508
  - This library does not maintain any MCP server state or sessions across Lambda function invocations.
509
- Only stateless MCP servers are a good fit for using this adapter. For example, MCP servers
509
+ Only stateless MCP servers are a good fit for using this library. For example, MCP servers
510
510
  that invoke stateless tools like the [time MCP server](https://github.com/modelcontextprotocol/servers/tree/main/src/time)
511
511
  or make stateless web requests like the [fetch MCP server](https://github.com/modelcontextprotocol/servers/tree/main/src/fetch).
512
512
  Stateful MCP servers are not a good fit, because they will lose their state on every request.
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@aws/run-mcp-servers-with-aws-lambda",
3
3
  "description": "Run Model Context Protocol (MCP) servers with AWS Lambda",
4
- "version": "0.3.3",
4
+ "version": "0.3.5",
5
5
  "type": "module",
6
6
  "license": "Apache-2.0",
7
7
  "author": {
@@ -39,29 +39,29 @@
39
39
  "dist"
40
40
  ],
41
41
  "devDependencies": {
42
- "@eslint/js": "^9.30.1",
42
+ "@eslint/js": "^9.32.0",
43
43
  "@tsconfig/recommended": "^1.0.10",
44
+ "@types/aws-lambda": "^8.10.152",
44
45
  "@types/jest": "^30.0.0",
45
- "@types/node": "^24.0.10",
46
+ "@types/node": "^24.1.0",
46
47
  "aws-sdk-client-mock": "^4.1.0",
47
48
  "aws-sdk-client-mock-jest": "^4.1.0",
48
49
  "eslint": "^9.30.1",
49
50
  "eslint-plugin-check-file": "^3.3.0",
50
- "jest": "^30.0.4",
51
+ "jest": "^30.0.5",
51
52
  "ts-jest": "^29.4.0",
52
53
  "tsx": "^4.20.3",
53
- "typescript": "^5.8.3",
54
- "typescript-eslint": "^8.35.1"
54
+ "typescript": "^5.9.2",
55
+ "typescript-eslint": "^8.39.0"
55
56
  },
56
57
  "dependencies": {
57
58
  "@aws-crypto/sha256-js": "^5.2.0",
58
- "@aws-sdk/client-lambda": "^3.840.0",
59
- "@aws-sdk/credential-provider-node": "^3.840.0",
60
- "@aws-sdk/protocol-http": "^3.370.0",
59
+ "@aws-sdk/client-lambda": "^3.859.0",
60
+ "@aws-sdk/credential-provider-node": "^3.859.0",
61
+ "@aws-sdk/protocol-http": "^3.374.0",
61
62
  "@aws-sdk/types": "^3.840.0",
62
- "@modelcontextprotocol/sdk": "^1.16.0",
63
+ "@modelcontextprotocol/sdk": "^1.17.1",
63
64
  "@smithy/signature-v4": "^5.1.2",
64
- "@types/aws-lambda": "^8.10.149",
65
65
  "winston": "^3.17.0"
66
66
  }
67
67
  }