serverless-mcp-server
by eleva
A simple Model Context Protocol (MCP) server deployed on AWS Lambda and exposed via Amazon API Gateway, deployed with Serverless Framework. It provides a minimal setup for interacting with models using the MCP standard.
Last updated: N/A
π§ serverless-mcp-server
A super simple Model Context Protocol (MCP) server deployed on AWS Lambda and exposed via Amazon API Gateway, deployed with Serverless Framework. This skeleton is based on the awesome work of FrΓ©dΓ©ric Barthelet: which has developed a middy middleware for Model Context Protocol (MCP) server integration with AWS Lambda functions in this repo
π Features
- πͺ Minimal MCP server setup using @modelcontextprotocol/sdk
- π Deployed as a single AWS Lambda function
- π HTTP POST endpoint exposed via API Gateway at /mcp
- π Supports local development via serverless-offline
- π§ͺ Includes a simple example tool (add) with JSON-RPC interaction
π¦ Project Structure
serverless-mcp-server/
βββ src/ # Source code
β βββ index.js # MCP server handler
βββ .gitignore # Git ignore file
βββ package.json # Project dependencies
βββ package-lock.json # Project lock file
βββ README.md # This documentation file
βββ serverless.yml # Serverless Framework config
π Prerequisites
- Node.js v22+
- Open Source Serverless or Serverless Framework v3+
- Serverless Offline
π Getting Started
- Install dependencies:
npm install
- Install open source severless globally (if not already installed):
npm install -g osls
- Run Locally with serverless-offline
npm sls offline
Local endpoint will be available at:
POST http://localhost:3000/dev/mcp
Note that the /dev/
stage is added by default when using serverless-offline, reflecting Api Gateway V1 (REST API) behavior.
Switch to Api Gateway V2 (HTTP API)
If you want to use API Gateway V2, you can change the serverless.yml
file to use httpApi
instead of http
in the events
section. This will allow you to use HTTP APIs instead of REST APIs.
This will allow you to use HTTP APIs instead of REST APIs.
functions:
mcpServer:
handler: src/index.handler
events:
- httpApi:
path: mcp
method: post
Local endpoint will be available at:
POST http://localhost:3000/mcp
Note that the /dev/
stage is not needed when using API Gateway V2.
Note you should change test curl and postman requests accordingly.
π§ͺ Test with curl requests
List tools
curl --location 'http://localhost:3000/dev/mcp' \
--header 'content-type: application/json' \
--header 'accept: application/json' \
--header 'jsonrpc: 2.0' \
--data '{
"jsonrpc": "2.0",
"method": "tools/list",
"id": 1
}'
β Use the add Tool
curl --location 'http://localhost:3000/dev/mcp' \
--header 'content-type: application/json' \
--header 'accept: application/json' \
--header 'jsonrpc: 2.0' \
--data '{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "add",
"arguments": {
"a": 5,
"b": 3
}
}
}'
𧬠Code Breakdown
This code is based on the awesome work of FrΓ©dΓ©ric Barthelet: which has developed a middy middleware for Model Context Protocol (MCP) server integration with AWS Lambda functions in this repo
src/index.js
import middy from "@middy/core";
import httpErrorHandler from "@middy/http-error-handler";
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { z } from "zod";
import mcpMiddleware from "middy-mcp";
const server = new McpServer({
name: "Lambda hosted MCP Server",
version: "1.0.0",
});
server.tool("add", { a: z.number(), b: z.number() }, async ({ a, b }) => ({
content: [{ type: "text", text: String(a + b) }],
}));
export const handler = middy()
.use(mcpMiddleware({ server }))
.use(httpErrorHandler());
π‘ Deploy to AWS
Just run:
sls deploy
After deployment, the MCP server will be live at the URL output by the command.
π License
MIT β feel free to fork, tweak, and deploy your own version!