Serverlessrun

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026

AWS Lambda functions, versions, aliases, layers and settings as MCP tools.

VerifiedSTDIODesktop onlyCloud & Infrastructure

Overview

Serverlessrun's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Serverlessrun in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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.

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

bash
export AWS_ACCESS_KEY_ID=...export AWS_SECRET_ACCESS_KEY=...export AWS_REGION=us-east-1        # optional, this is the defaultexport 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

bash
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

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

Docker

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

Development

bash
npm installnpm run buildnpm test

License

MIT

Source: README.md at commit 419af01

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestNov 3, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts