# Genhttp Lambda MCP server

Source: https://glimind.com/server/mcp-registry%2Fdev.genhttp%2Flambda
Registry id: `mcp-registry/dev.genhttp/lambda`
Status: live (checked 2026-11-22T16:51:36.043Z)

## Measurements (30 days)

- Uptime: 99.69%
- Checks: 891
- Outages (90 days): 7

## Install

```json
{
  "mcpServers": {
    "genhttp-lambda-mcp-server": {
      "type": "http",
      "url": "https://genhttp.dev/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http genhttp-lambda-mcp-server https://genhttp.dev/mcp
```

## Tools (25)

- `analytics`: How people reach a lambda, as its owner sees it in the editor: visitors, pages opened and requests per day, and the pages, referring sites, countries, devices, 
- `change_code`: Change some files: add or replace files, remove files, or replace text within a file. Everything not named stays as it is, so there is no need to resend unchang
- `check_code`: Compile without saving or deploying; returns diagnostics with file and line. Does not build the handler, so deploy can still refuse a route whose return type ca
- `create_feature`: Start a feature: a place to change a lambda without touching what it has online. It branches off a version - the newest unless base names another - with a copy 
- `create_lambda`: Create a lambda. Returns its public address and a private editor key, the only way back in. It starts with version 1 - an empty starter, or a copy of a demo. No
- `delete_feature`: Throw a feature away: its files, its preview and its copy of the data. The lambda is not touched. For a feature the user does not want after all.
- `delete_file`: Remove a file, or a folder with its contents, from the workspace - the lambda's data, shared by every version. No deploy or rollback brings it back. With featur
- `delete_secret`: Remove a secret. Code that reads it with Secret.ReadAsync fails from its next call on. Only when the user asks for it, or a secret you stored yourself is no lon
- `deploy`: Deploy (publish) a saved version so it goes live at its public address - the newest by default. With feature, deploy that feature's files to its own preview add
- `enable_data`: Switch on a kind of data the lambda needs and does not have: 'database' (a database of its own for its records - off until switched on, which makes it, empty), 
- `list_demos`: Demos this platform keeps online, each a finished lambda showing one way to build something: a REST API over records, registration and login, a websocket game, 
- `list_files`: The lambda's data: whether its workspace is switched on, and every file in it with size and last write - the same whichever version is online. With feature, tha
- `list_secrets`: The lambda's secrets by name - never their values: whether secrets are switched on, what is stored and when, which names the code reads with Secret.ReadAsync an
- `merge_feature`: Make a feature's files the next version of the lambda, and delete the feature with its preview and its copy of the data - the lambda's own data is not touched. 
- `open_source`: Publish a lambda's source code at /source/{publicKey} for anybody to read, star and download as a .NET project, change the license it is published under, or tak
- `platform_guide`: How this platform works, read first: one Markdown document in sections the other tools point to as 'platform_guide, <section>' - how versions, features and data
- `read_database`: The lambda's database - its records, shared by every version: whether it is switched on, how full it is, and its tables and views with their columns and how man
- `read_lambda`: A lambda's status (online version, newest version, expiry, its tier and what it may use there), its open features, the recent versions with what each was asked 
- `read_logs`: What a deployed lambda has been doing: its recent requests and how they were answered, what it printed, the errors it threw with their stack traces, and how muc
- `request_connectivity`: Ask the operator of the installation to let a lambda's code connect to other servers - call an API with HttpClient, open a socket, a WebSocket or mail client - 
- `set_secret`: Store an API key, password or token under a name the code reads with Secret.ReadAsync("NAME") - never put one in the code, a resource, the workspace, a log line
- `update_feature`: Rename a feature, change what it says about itself, or move its base. merge_feature refuses a feature that is not based on the newest version, since merging it 
- `update_lambda`: Change how a lambda's editor opens: view 'Simple' shows the app, how it is doing and a box to ask for a change - for an owner who does not write code - and 'Ful
- `upload_file`: Write a file to the lambda's workspace - its data, which every version shares and no deploy, rollback or merge touches. With feature, to that feature's copy of 
- `write_code`: Save every file, replacing the previous set: as a new version of the lambda, or - with feature - into that feature. A version is its code and its resources. The

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
