serverless

A super simple Model Context Protocol (MCP) server deployed on AWS Lambda and exposed via Amazon API Gateway, deployed with Serverless Framework.

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

View docs

Command

claude mcp add --transport stdio eleva-serverless-mcp-server node src/index.js \
  --env STAGE="dev" \
  --env AWS_REGION="us-east-1" \
  --env LAMBDA_HANDLER="src/index.handler"

How to use

This MCP server is designed to run as a Lambda-backed service exposed via API Gateway under the /mcp path. It uses the Model Context Protocol SDK to provide a minimal MCP server with a sample tool (add) that demonstrates how tools are registered and invoked via JSON-RPC. You can invoke the server locally using Serverless Offline or deploy it to AWS Lambda behind API Gateway. The server exposes a single HTTP POST endpoint that accepts MCP requests and returns MCP responses, including tool discovery (tools/list) and tool execution (tools/call) interactions. The included add tool demonstrates JSON-RPC style parameter passing and the content payload format that MCP tools return (e.g., content with type and text).

How to install

Prerequisites:

Node.js v18+ (the project lists Node.js v22+ as a prerequisite, ensure compatibility with your environment)
npm (comes with Node.js)
Serverless Framework (and Serverless Offline for local development)

Installation steps:

Clone or download the repository and open a terminal in the project root.
Install dependencies: npm install
(Optional) Install Serverless globally if not already installed: npm install -g serverless or the project’s preferred variant (as noted in the README, some users may use osls).
For local development with offline support, ensure serverless-offline is configured in serverless.yml (as in the README). Then start offline: npm run sls offline or sls offline

Local development note:

By default, the local endpoint is POST http://localhost:3000/dev/mcp when using Serverless Offline with the REST API (http) mode. If you switch to HTTP API (httpApi) mode, the path changes to http://localhost:3000/mcp and you won’t see the /dev/ stage.

Deployment: 5) Deploy to AWS: sls deploy

After deployment, obtain the endpoint URL from the Serverless output and send MCP requests to the /mcp path via POST.

Additional notes

Tips and notes:

The server is a minimal MCP server built with @modelcontextprotocol/sdk and Middy middleware to handle MCP requests.
The included example tool is add, which accepts two numbers a and b and returns their sum as a text payload in the MCP content structure.
If you enable API Gateway v2 (HTTP API), you can adjust serverless.yml to use httpApi instead of http for REST vs HTTP API semantics. Remember to update client requests accordingly (base URL path may differ and the /dev/ stage is not used with HTTP API).
When testing locally, ensure that port 3000 is available and not blocked by other services.
Environment variables can be used to configure deployment specifics (e.g., stage, region).

Related MCP Servers

zen

1.1k

Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage

MCP -Deepseek_R1

A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)

mcp-fhir

A Model Context Protocol implementation for FHIR

mcp

Inkdrop Model Context Protocol Server

mcp-appium-gestures

This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..

dubco -npm

The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.