Skip to main content
Glama

serverlessrun

AWS Lambda as MCP tools, shaping requests for the documented Lambda REST API. serverlessrun is a clean-room rebuild of the core surface of the aws-lambda MCP server, under a new name: the same tool names and request shapes, fresh code, no copied branding.

Tools (core subset, 10)

list_functions, get_function, invoke_function, list_versions_by_function, get_alias, list_aliases, list_layers, get_layer_version, list_event_source_mappings, get_account_settings.

Not in this subset: function create/update/delete and code upload, configuration and policy management, tags, concurrency controls, function URLs, destinations, event source mapping writes, and code signing.

Related MCP server: MetaCall MCP Server

How it works

Every tool shapes a documented Lambda REST request (API version 2015-03-31) and hands it to an injectable executor: execute({ service: "lambda", operation, path, method, body, query }). Library users can inject their own executor or signer to run against real AWS with their own signing stack.

Setup

export AWS_ACCESS_KEY_ID=...
export AWS_SECRET_ACCESS_KEY=...
export AWS_REGION=us-east-1        # optional, this is the default
export AWS_SESSION_TOKEN=...       # optional

Honest limitation: this rebuild ships no SigV4 signer of its own. With credentials set but no signer injected, calls fail with SigV4 signing not configured: inject a signer/executor. With no credentials, calls fail with an error naming AWS_ACCESS_KEY_ID.

CLI

npx @reneturcios/serverlessrun list_functions '{}'
npx @reneturcios/serverlessrun mcp        # stdio MCP server

Each tool name is a subcommand taking one JSON object argument.

MCP client config

{
  "mcpServers": {
    "serverlessrun": {
      "command": "npx",
      "args": ["-y", "@reneturcios/serverlessrun", "mcp"],
      "env": { "AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..." }
    }
  }
}

Docker

docker run -i -e AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY ghcr.io/cloudcorprecords/serverlessrun

Development

npm install
npm run build
npm test

License

MIT

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables MCP clients to interact with any OpenAPI-defined REST API through a serverless AWS Lambda deployment. Supports multiple authentication methods and provides cost-effective, scalable access to third-party APIs through natural language.
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Bridges MCP clients and AWS Lambda functions, enabling generative AI models to invoke Lambda functions as tools without code changes.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes the LogicMonitor REST API as MCP tools with per-request LMv1 authentication, enabling querying of devices, alerts, reports, and more.
      Apache 2.0