.html) - [NodeJS](https://nodejs.org/en/download) >= 22.x Build project ```bash sam build ``` Deploy the stack ```bash sam deploy --profile --guided ``` ## Usage Once the solution is installed, you can extend the MCP server with resources, prompts or tools using SSM parameters and Lambda functions. The SSM parameters must begin with the prefix `///`, for example `/mcp/dev/tools/echo`. As an example of integration you can take inspiration from the template: [template.integration.yaml](./template.integration.yaml). ### Resources The SSM parameters must begin with prefix `///resources/`, for example `/mcp/dev/resources/example`. The content must be in valid JSON format and have the properties: - name: Resource name - uri: Resource URI, for example "config://example" - content: Resource text content It can be declared in a SAM template as: ```yaml ExampleResourceParameter: Type: AWS::SSM::Parameter Properties: Name: !Sub "/${Project}/${Environment}/resources/example" Type: String Value: | { "name": "example", "uri": "config://example", "content": "Just an example resource" } ``` ### Prompts The SSM parameters must begin with prefix `///prompts/`, for example `/mcp/dev/prompts/echo`. The content must be in valid JSON format and have the properties: - name: Prompt name - description: Prompt description - inputSchema.json: [JSON schema](https://json-schema.org/) - content: Prompt template content The content template will be elaborate with [ejs](https://ejs.co/) with input data interpolation. It can be declared in a SAM template as: ```yaml EchoPromptParameter: Type: AWS::SSM::Parameter Properties: Name: !Sub "/${Project}/${Environment}/prompts/echo" Type: String Value: | { "name": "echo", "description": "Execute the example tool", "inputSchema": { "json": { "type": "object", "properties": { "message": { "type": "string" } }, "required": ["message"] } }, "content": "Execute the tool 'echo' with the message '<%= message %>'" } ``` ### Tools The SSM parameters must begin with prefix `///tools/`, for example `/mcp/dev/tools/echo`. The content must be in valid JSON format and have the properties: - name: Prompt name - description: Prompt description - inputSchema.json: [JSON schema](https://json-schema.org/) The related Lambda function that will be executed must be name as `--tools-`, for example `mcp-dev-tools-echo`. The function input and output must respect the [Converse API](https://docs.aws.amazon.com/bedrock/latest/userguide/tool-use-inference-call.html) pattern. The parameter can be declared in a SAM template as: ```yaml EchoToolParameter: Type: AWS::SSM::Parameter Properties: Name: !Sub "/${Project}/${Environment}/tools/echo" Type: String Value: | { "name": "echo", "description": "Print the message provided in input", "inputSchema": { "json": { "type": "object", "properties": { "message": { "type": "string" } }, "required": ["message"] } } } ``` The Lambda function implementation could be: ```js exports.handler = async ({ toolUseId, name, input }, context) => { return { name, toolUseId, status: 'success', content: [{ text: input.message }] } } ``` declared inline in a SAM template: ```yaml EchoToolFunction: Type: AWS::Serverless::Function Properties: FunctionName: !Sub "${Project}-${Environment}-tools-echo" Handler: index.handler InlineCode: | exports.handler = async ({ toolUseId, name, input }, context) => { return { name, toolUseId, s

#aws-apigateway

Serverless MCP Framework