GenHTTP Lambda MCP server
2026년 11월 14일 커밋AI 클라이언트가 소규모 C# 웹 서비스와 사이트를 작성, 배포 및 공용 주소로 호스팅할 수 있게 합니다.
다른 이름 MDA2AV/GenHTTP.Lambda, genhttp-lambda
- 스타
- 4
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 0.1.0
- 마지막 커밋
- 2026년 11월 14일
- 라이선스
- MIT
GenHTTP Lambda MCP란?
GenHTTP Lambda은(는) MCP server입니다. AI 클라이언트가 소규모 C# 웹 서비스와 사이트를 작성, 배포 및 공용 주소로 호스팅할 수 있게 합니다.
프로젝트 README에서 생성된 요약
GenHTTP Lambda MCP server 정보
GenHTTP Lambda는 개발자와 AI 에이전트가 소규모 C# 웹 서비스를 공용 주소로 작성, 배포 및 호스팅할 수 있는 플랫폼을 제공합니다. 이 시스템은 Roslyn을 사용하여 런타임에 C# 스니펫을 컴파일하며, IHandler를 실제 작동하는 웹 서비스로 변환합니다. 이를 통해 간단한 코드 블록을 고유한 서브도메인을 가진 기능적인 사이트로 즉시 변환하는 신속한 프로토타이핑이 가능합니다.
사용자는 웹 인터페이스 또는 에이전트용으로 설계된 API를 통해 서버와 상호작용합니다. 서버는 호스팅되는 각 lambda에 대해 SQLite 데이터베이스, 워크스페이스, secret을 포함한 다양한 리소스를 관리합니다. 개발자는 게시를 위한 /ship 또는 직접 조작을 위한 /editor와 같은 특정 라우트를 통해 서비스를 관리할 수 있습니다. 환경은 Docker Compose를 사용한 로컬 개발이나 .NET 서버와 Vite 프론트엔드를 별도로 실행하는 방식을 모두 지원합니다. 또한 버전 관리, 배포 이력 확인, 서비스 상태 모니터링을 위한 로그 액세스 기능도 포함되어 있습니다.
활용 사례
- 1에이전트를 통한 코드 변경 자동화에이전트에게 특정 lambda 버전에 변경을 수행하도록 지시할 수 있습니다.
- 2서비스 트래픽 및 로그 모니터링사용자는 배포된 handler의 요청 이력과 로그를 확인할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
GenHTTP Lambda MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 GenHTTP Lambda MCP 설치
$ claude mcp add --transport http genhttp-lambda https://genhttp.dev/mcpCursor에 GenHTTP Lambda MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"genhttp-lambda": {
"url": "https://genhttp.dev/mcp"
}
}
}VS Code에 GenHTTP Lambda MCP 설치
.vscode/mcp.json
{
"servers": {
"genhttp-lambda": {
"type": "http",
"url": "https://genhttp.dev/mcp"
}
}
}VS Code CLI에 GenHTTP Lambda MCP 설치
$ code --add-mcp '{"name":"genhttp-lambda","type":"http","url":"https://genhttp.dev/mcp"}'Codex에 GenHTTP Lambda MCP 설치
$ codex mcp add genhttp-lambda --url https://genhttp.dev/mcpCodex config.toml에 GenHTTP Lambda MCP 설치
~/.codex/config.toml
[mcp_servers.genhttp-lambda] url = "https://genhttp.dev/mcp"
Gemini CLI에 GenHTTP Lambda MCP 설치
$ gemini mcp add -s user --transport http genhttp-lambda https://genhttp.dev/mcpGemini settings.json에 GenHTTP Lambda MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"genhttp-lambda": {
"url": "https://genhttp.dev/mcp",
"type": "http"
}
}
}구성
LAMBDA_CERTIFICATELAMBDA_CERTIFICATE_KEYLAMBDA_HOSTING_URLLAMBDA_TLS_PORT
| 이름 | 설명 | 유형 |
|---|---|---|
| LAMBDA_CERTIFICATE | — | |
| LAMBDA_CERTIFICATE_KEY | — | |
| LAMBDA_HOSTING_URL | — | |
| LAMBDA_TLS_PORT | — |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능mda2av/genhttp.lambda is public and reachablegithub.com/mda2av/genhttp.lambda ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-13github.com/mda2av/genhttp.lambda ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답initialize answered with protocol 2025-06-18 in 117 ms통과
README
GitHub에서 보기GenHTTP Lambda
Write a C# snippet that returns a GenHTTP IHandler, press deploy, and get a
public URL that serves it. The snippet is compiled with Roslyn at runtime and
the resulting handler is hosted by the same [GenHTTP][genhttp] server that
serves this application.
return Inline.Create()
.Get(() => "Hello from my lambda!");
Quick start
docker compose up --build
The application is then available at http://localhost:8080/. Its data - the
SQLite database, the stored code, and the workspaces and databases of the
lambdas - lives in a named volume mounted at /data. The lambdas answer at
subdomains of LAMBDA_HOSTING_URL, one each (see
Where the lambdas answer).
Developing locally
Two processes: the .NET server, and Vite serving the frontend with hot reload.
# the server, on http://localhost:8080/
dotnet run --project src/GenHTTP.Lambda
# the frontend, on http://localhost:5173/ (proxies /api, /lambda and /features to the server)
cd src/Frontend && npm install && npm run dev
Work against http://localhost:5173/ while developing. The lambdas answer at
subdomains of localhost named after their keys - http://quiz.localhost:8080/ -
which browsers resolve without a record. The server on its own answers with a
placeholder page until a frontend has been built into its web root, which is
what npm run build does:
cd src/Frontend && npm run build # writes src/GenHTTP.Lambda/wwwroot
English is the source of every page; the other languages are translated by script and agent, so that only what changed is read and written:
cd src/Frontend
npm run translations -- extract # a request per language in .translations/
# one `translator` agent per request (.claude/agents/translator.md, on Sonnet)
npm run translations -- apply # the answers into the catalogs, checked
npm run translations -- check # every language against English
CLAUDE.md ("How a change is translated") has the rules.
Build and test everything the way CI does:
dotnet build GenHTTP.Lambda.slnx -c Release
dotnet test GenHTTP.Lambda.slnx -c Release
The tests compile and execute real lambdas against a real server on a random port, each against its own temporary data directory.
Routes
| Route | Serves |
|---|---|
/ |
the landing page |
/build |
the text box for somebody who wants an app built, no code |
/ship |
for developers: connect an agent and publish what it built |
/docs |
the guide for owners |
/showcase |
the lambdas their owners chose to show |
/source |
the lambdas whose owners published their code |
/source/:publicKey |
the published code of one: its files, documentation, tests and changes, per version |
/source/:publicKey.git |
the published code as a git repository, read only |
/enterprise, /terms, /privacy, /imprint |
the company pages |
/editor/create |
the creation assistant |
/editor/:privateKey |
the editor for one lambda |
/editor/:privateKey/:name.git |
the lambda as a git repository, to clone and push to (any name; the editor offers the public key) |
/lambda/:publicKey/… |
where a lambda answered once: a permanent redirect to where it answers now, with the rest of the path and the query |
/features/:feature |
the preview of a feature, while it is online |
any path, at {publicKey}.{hosting domain} |
the deployed handler - or, while the lambda answers at a domain of its own, a permanent redirect there |
| any path, at a lambda's own domain | the deployed handler of a premium lambda with that domain |
| the hosting domain itself | a page saying what is hosted there, leading to the site |
/api/v1/ |
everything the editor calls, see below |
/mcp |
the same, for agents |
/admin |
every lambda on the server, for whoever runs it |
API
Browsable at /api/v1/scalar/, described by /api/v1/openapi.json (or
.yaml). The description is the reference for whoever calls the API: it opens
with an introduction (getting started, keys, files, limits, errors), groups
the operations by what they are about, and says of each what it does, what it
leaves alone and every way it is refused. It is written with GenHTTP's
documentation attributes beside the code (see ApiDocumentation), and
ApiDocumentationTests keeps it complete.
A lambda is addressed by its editor key, which is also what authorizes the
call. Things that can be listed, read, created or changed are resources; what
is a process rather than a thing is a verb in the path. A refusal is answered
with a status and { status, error, message }, where error is Invalid
(400), Forbidden (403), NotFound (404), Conflict (409) or TooMany (429).
| Endpoint | Does |
|---|---|
POST /lambdas |
creates a lambda (optionally with view: Full or Simple) |
GET / PATCH / DELETE /lambdas/:privateKey |
reads, changes (its key, its view), removes it |
GET /lambdas/:privateKey/export |
the newest version as a runnable .NET 10 project with a Dockerfile (zip), with its database, see below |
GET / POST /lambdas/:privateKey/versions |
lists versions, saves a new one (optionally with specification and change) |
GET /lambdas/:privateKey/versions/:version |
reads one version (?folder=docs/ for its documentation alone, resources/ for its resources) |
GET /lambdas/:privateKey/versions/:version/zip |
one version's files as a zip (?layout=project laid out as a clone) |
POST /lambdas/:privateKey/versions/zip |
saves a zip of all files as a new version (?layout=project for one laid out as a clone) |
POST /lambdas/:privateKey/versions/changes |
changes some files of the newest version, as a new one |
GET /lambdas/:privateKey/deployment |
what is online, and until when |
POST /lambdas/:privateKey/deployment/start / stop |
puts a version online, takes it off |
GET /lambdas/:privateKey/deployment/history |
every stretch it was online, and what ended it |
GET /lambdas/:privateKey/summary |
the dashboard: state, traffic, problems, storage, what the documentation says |
GET /lambdas/:privateKey/traffic |
requests by minute and quarter hour, statuses, paths |
GET /lambdas/:privateKey/logs |
its own log, followed with ?since=; no visitor addresses |
GET /lambdas/:privateKey/agent |
the agent's change of it - under way, or the last one - and how many are left today |
POST /lambdas/:privateKey/agent/start / stop |
asks the agent for a change, stops it |
GET /lambdas/:privateKey/data |
the kinds of data it keeps, and how full each is |
GET / PUT / DELETE /lambdas/:privateKey/data/:kind |
one kind (database, workspace, secrets); switches it on; switches it off and deletes what it held |
GET /lambdas/:privateKey/database |
its database: tables and views, their columns and rows, how full it is, whether the code connects |
GET /lambdas/:privateKey/database/tables/:table |
a page of one table's rows, newest first (offset, limit, order, descending) |
GET /lambdas/:privateKey/secrets |
the secrets by name, which names the code reads, and which of those have no value |
PUT / DELETE /lambdas/:privateKey/secrets/:name |
stores a value ({ "value": … }), never read back; removes one |
GET /lambdas/:privateKey/files |
lists the workspace |
GET / PUT / DELETE /lambdas/:privateKey/files/:path |
one file, its path encoded (a%2Fb.txt), as base64 up to 32 MB |
GET / PUT /lambdas/:privateKey/files/:path/content |
one file as it is, streamed, however large |
PUT /lambdas/:privateKey/folders/:path |
makes a folder |
GET / POST /lambdas/:privateKey/features |
lists the features, starts one (name, specification, base) |
GET / PATCH / DELETE /lambdas/:privateKey/features/:feature |
one feature with its files (?folder= as for a version); changes its name, notes or base; deletes it |
PUT /lambdas/:privateKey/features/:feature/files |
replaces its files (?deploy=true puts its preview online) |
POST /lambdas/:privateKey/features/:feature/changes |
changes some of its files |
GET / PUT /lambdas/:privateKey/features/:feature/zip |
its files as a zip; a zip put back into it (both with ?layout=project) |
POST /lambdas/:privateKey/features/:feature/preview/start / stop |
puts its preview online, takes it off |
POST /lambdas/:privateKey/features/:feature/merge |
makes it the next version and deletes it (deploy to put that online) |
GET /lambdas/:privateKey/features/:feature/logs |
what its preview has been doing |
GET /lambdas/:privateKey/features/:feature/data, POST …/data/refresh |
its copy of the data; a fresh copy of the lambda's |
…/features/:feature/workspace[/:path[/content]], …/folders/:path |
its copy of the workspace, as files and folders are the lambda's |
…/features/:feature/secrets[/:name] |
its copy of the secrets, as secrets are the lambda's |
…/features/:feature/database[/tables/:table] |
its copy of the database, as database is the lambda's |
POST /lambdas/:privateKey/code/check |
compiles without saving |
POST /lambdas/:privateKey/code/semantics, completions, definition |
what the editor asks the compiler |
GET /keys/:publicKey |
whether a key is free, and if not, online |
GET /demos |
the demos, and the keys to read them with |
GET / PUT / DELETE /lambdas/:privateKey/showcase |
its entry on the showcase: read, list it (title, description, picture), take it off |
GET /lambdas/:privateKey/domain, PUT / DELETE |
the domain of a premium lambda, whether it is served, and what it resolves to |
GET /showcases, GET /showcases/:publicKey/image |
what /showcase lists, and a picture |
GET / PUT / DELETE /lambdas/:privateKey/analytics |
who visits it, by day, over the last days (at most what its tier shows); switches counting on; switches it off and deletes what was counted, see Analytics |
GET / PUT / DELETE /lambdas/:privateKey/source |
whether its code is published and under which license, the licenses on offer; publishes it or changes the license (license, author); takes it down |
GET /sources |
what /source lists (search, order: stars, updated, published, skip, take) |
GET /sources/:publicKey |
a published source: what it is, its license, where it runs, every version and what it changed, a ticket to star it with |
GET /sources/:publicKey/versions/:version |
the files of a version as its project has them, packed on the first request |
GET /sources/:publicKey/versions/:version/files/:path, …/raw/:path |
one file, its path encoded: its text; as it is (?download=1 to save it) |
GET /sources/:publicKey/versions/:version/zip |
a version as a project to download |
POST /sources/:publicKey/star |
stars it, or takes the star back (ticket, starred) |
POST /builds, GET /builds/:id |
the text box on /build |
GET /system |
terms, limits, starters, build agent, where a lambda answers (lambdaUrl) |
GET /telemetry, /logs, /admin/... |
for whoever runs the installation |
Creating a lambda asks what somebody would like to build and offers the demos
in those words - "Keep track of things", "Let people sign up" - next to an empty
lambda. Picking a demo starts the new lambda as a copy of it, which is theirs to
change. The files are in Resources/Templates and listed in TemplateCatalog.
A lambda has two keys. The public one names its address - quiz answers at
https://quiz.genhttp.run/ - and may be changed; the private one is the
editor link and is shown only to whoever created the lambda - anyone holding
it can edit, deploy and delete. What the API answers about a lambda carries
both its address below the hosting domain, publicUrl, and where to link to
it, address - its own domain while it answers at one, publicUrl otherwise
(see Where the lambdas answer).
A lambda may also return a websocket rather than a document, in any of the
three flavours the module offers - Websocket.Functional(), .Reactive() and
.Imperative(). The handshake is an ordinary request and is bounded by the
execution timeout like any other; everything after it belongs to the
connection, which is why a socket may stay open far longer than a lambda is
given to answer. FrameType, which the imperative flavour reads off every
frame, is one of the names a lambda is given, so no import is needed.
A lambda may offer tools to AI agents itself, over the Model Context Protocol:
Tools.Create() with a class whose methods are marked [Tool], added at a
path such as mcp, which an agent then connects to. And a webservice of its
own describes itself as OpenAPI, in the words of [Summary], [Remarks],
[Tag] and [Response] on its routes and records. The MCP module and those
attributes are imported for every lambda and in its export; demo-crud shows
both, and the guide says how (toolsForAgents, describingAnApi).
The editor says when both free tier timers run out: a hint under the public URL for the deployment, and a chip beside the buttons for the lambda itself, which opens an explanation of how each one is extended.
Where the lambdas answer
Every lambda answers at a subdomain of one domain, the hosting domain, named
after its public key: https://quiz.genhttp.run/, the whole of the host its
own. LAMBDA_HOSTING_URL names that domain with its scheme and port; left
empty it is this server on localhost - http://quiz.localhost:8080/ - which
browsers resolve without a record in the DNS.
A host of its own rather than a path below the platform's, so that what
somebody built is a site of its own: a page of it cannot read what the
platform keeps in a browser - the admin token, for one - nor what another
lambda keeps there, and its paths start at the root of its host, so a
browser asking for /favicon.ico asks the lambda. The editor, the API, the
agents' endpoint and git stay where they are, on the platform.
- Its old address.
/lambda/{key}/…on the platform is answered with a permanent redirect to where the lambda answers now, with the rest of the path and the query as they were sent, byte for byte - a signature over them still matches - Moved Permanently for a read, Permanent Redirect for anything else, which a client sends again with the same method and body. It is answered before anything else the server does: no request line, no telemetry, no upgrade to HTTPS, since the address it sends to is secure already. A browser keeps it for a day rather than for good, because where a lambda answers changes when it gets a domain or loses one. A key nobody has is sent on as well - the address moved, whether or not something is there - while a path below/lambda/that could never have been a key is not found. - A domain of its own. A premium lambda with a domain answers there and
only there: its subdomain sends visitors on to the domain the same way, so
there is one address for search engines to keep and for visitors to pass
on. Removing the domain, or the tier that serves it, has the subdomain
answer again. For the same reason
www.in front of the domain sends its visitors on to it -www.shop.example.comtoshop.example.com- unless the owner entered the domain withwww., which is then where it answers, and nothing is sent there from the name without; or unless thatwww.is the domain of another lambda, or one of the platform's own names. - Nothing there. A subdomain nothing is online at - a key nobody has, a
lambda that is offline, a name no key can be - is told so in a plain page
that leads to the site, or in a line of JSON for anything but a browser.
The hosting domain itself, and
www.in front of it, has a page of its own that says what is hosted there and leads to the site, in the language the browser prefers; its words are inpages.json(hosting:/andhosting:/:key) and translated with the rest. Both link the site's legal notice and privacy policy, named as the site names them. Neither is one of the site's pages: none of the site's scripts is ever served at the hosting domain. - A host nobody has. Where
LAMBDA_PUBLIC_URLis set, the platform answers only at its own names -localhost, the host of that address and the hosts inLAMBDA_MCP_ORIGINS- and a host that is neither one of those nor a lambda's is told nothing is online there, in the same page, with a 404 on every path. That is usually a domain pointed here before its owner entered it, or after it left the lambda or the premium tier. Served the site, it was a copy of the site under somebody else's name, which crawlers kept and kept asking for once the domain was a lambda's. The challenges of an ACME client are answered there all the same. An installation withoutLAMBDA_PUBLIC_URLcannot tell its own names from anybody else's, and the platform answers at every host. - Keys are host names. A key is a label of the hosting domain, so the
names mail clients and servers look for below a domain (
mail,autoconfig,autodiscover,mta-sts) cannot be claimed, nor can a key starting withxn--, which a browser reads as an international name. A lambda is found by its key as it is spelled, whatever the rules for claiming one say today, so a rule made later takes nothing offline. - Previews stay on the platform. The preview of a feature answers at
/features/{feature}/, as it did, which is why a lambda links relatively. It is the one place a lambda's code still runs on the platform's host - with what the platform keeps in that browser in reach of its scripts - until previews get hosts of their own as well.
The request log names the host in front of the path - GET quiz.genhttp.run/api/items - as it does for a domain of its own, and the
traffic of a lambda counts its visitors by the host they came to.
What it takes is a wildcard record in the DNS - *.genhttp.run, and
genhttp.run for the page at its root, pointing at the server - and a
certificate for both names (see The hosting domain).
The hosting domain belongs on the Public Suffix List:
until it is there, a lambda can set a cookie for the whole domain, which the
browser then sends to every other lambda as well.
GenHTTP Lambda MCP 질문
GenHTTP Lambda MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --transport http genhttp-lambda https://genhttp.dev/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
GenHTTP Lambda MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
C# 스니펫을 어떻게 배포하나요?
GenHTTP IHandler를 반환하는 C# 스니펫을 작성한 후 deploy를 누르면 공용 URL을 받을 수 있습니다.
코드는 어떻게 컴파일되나요?
코드 스니펫은 런타임에 Roslyn을 사용하여 컴파일됩니다.
에이전트 기반 개발에 사용할 수 있나요?
네, 에이전트를 위한 전용 엔드포인트와 에이전트가 구축한 결과물을 게시할 수 있도록 연결하는 라우트가 제공됩니다.