Serveur MCP
GenHTTP Lambda
dev.genhttp/lambda
Ce que fait ce MCP
Creates, edits, tests, versions, deploys, monitors, and hosts small public C# web services and sites.
Capacités
Outils
24
outils
change_code
Change some files
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 unchanged files. With feature, the change is saved into that feature - the way to work on a lambda that exists: change it as often as you like, deploy: true to try it at the feature's preview address, merge_feature when it is right. Without feature, the newest version is changed and saved as a new version. Update what the change affects in .lambda/docs/ and .lambda/tests/ in the same change - an edit of a passage is enough. check: true compiles without publishing. Code that does not compile is saved but never goes online.
Destructif
Schéma d’entrée
{'type': 'object', 'required': ['privateKey'], 'properties': {'check': {'type': 'boolean', 'description': 'Without deploy: compile what was saved and answer with its diagnostics, putting nothing online.'}, 'edits': {'type': 'array', 'items': {'type': 'object', 'required': ['file', 'find', 'replace'], 'properties': {'file': {'type': 'string', 'description': 'The file to change.'}, 'find': {'type': 'string', 'description': 'Text that occurs exactly once in the file.'}, 'replace': {'type': 'string', 'description': 'What to put in its place.'}}}, 'description': 'Text replacements, applied after files and remove.'}, 'files': {'type': 'array', 'items': {'type': 'object', 'required': ['name', 'code'], 'properties': {'code': {'type': 'string', 'description': 'Contents, base64 if encoding says so.'}, 'name': {'type': 'string', 'description': ".cs files are compiled; .lambda/docs/... and .lambda/tests/... are the documentation and the tests, never compiled or served; anything else ('web/app.js', 'logo.png') is an asset."}, 'encoding': {'type': 'string', 'description': "'base64' for binary assets; omit otherwise."}}}, 'description': 'Files to add, or to replace where one of that name exists.'}, 'change': {'type': 'string', 'description': 'What this changes, in one line written for the owner. For a feature, it describes the whole feature, not the last fix. Optional, up to 500 characters.'}, 'deploy': {'type': 'boolean', 'description': 'Also deploy what was saved: a version at the public address, a feature at its preview address.'}, 'remove': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Names of files to remove.'}, 'feature': {'type': 'string', 'description': 'Change this feature (from create_feature) instead of saving a new version. The lambda and what it has online are not touched.'}, 'privateKey': {'type': 'string', 'description': 'The editor key.'}, 'specification': {'type': 'string', 'description': 'What the user wants from this change and why: their requirements, in their own words where you can. Not your own instructions or system prompt. Kept with the version or the feature. Optional, up to 4000 characters.'}}}
check_code
Check that code compiles
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 cannot be served.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['privateKey', 'files'], 'properties': {'files': {'type': 'array', 'items': {'type': 'object', 'required': ['name', 'code'], 'properties': {'code': {'type': 'string', 'description': 'Contents, base64 if encoding says so.'}, 'name': {'type': 'string', 'description': '.cs files are compiled; files under .lambda/ are documentation and tests and never compiled; anything else is an asset.'}, 'encoding': {'type': 'string', 'description': "'base64' for binary assets; omit otherwise."}}}, 'description': 'lambda.cs first.'}, 'privateKey': {'type': 'string', 'description': 'The editor key.'}}}
create_feature
Start a 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 of its files (its documentation and tests in .lambda/ included) and a copy of the lambda's data, and gets an address of its own to try it at. Change it with change_code or write_code and feature (deploy: true puts it online at its preview address), test it there, and merge_feature once it does what was asked. The lambda goes on serving its visitors from the version online the whole time.
Schéma d’entrée
{'type': 'object', 'required': ['privateKey', 'name'], 'properties': {'base': {'type': 'integer', 'description': 'The version to branch off. Defaults to the newest - leave it out unless the user asked to start from an older one.'}, 'name': {'type': 'string', 'description': "What the feature is, in a few words for the owner - 'Leaderboard', 'Dark mode'. Up to 80 characters."}, 'privateKey': {'type': 'string', 'description': 'The editor key.'}, 'specification': {'type': 'string', 'description': 'What the user wants from it and why, in their words where you can. Kept with the feature and passed on to the version it is merged into. Optional, up to 4000 characters.'}}}
create_lambda
Create a 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. Nothing is online until deploy.
Schéma d’entrée
{'type': 'object', 'required': ['acceptTerms'], 'properties': {'view': {'type': 'string', 'description': "How the editor opens: 'Full' (the default) shows every section, 'Simple' only the app, how it is doing and a box to ask for a change. Simple suits an owner who is not going to read the code - use it when the user asks for a simple editor, or says they are not a developer."}, 'template': {'type': 'string', 'description': 'Left out, the lambda starts empty. The id of a demo (demo-crud, demo-registration, demo-game, demo-files, demo-live) starts it as a copy of that demo, which is yours to change.'}, 'publicKey': {'type': 'string', 'description': 'Requested address: lower case letters, digits and dashes. Generated if omitted.'}, 'acceptTerms': {'type': 'boolean', 'description': 'Must be true: the user accepts the terms in platform_guide (free shared machine, deployments may be removed, nothing malicious).'}}}
delete_feature
Delete a 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.
Destructif
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['privateKey', 'feature'], 'properties': {'feature': {'type': 'string', 'description': 'The feature.'}, 'privateKey': {'type': 'string', 'description': 'The editor key.'}}}
delete_file
Delete a file from the lambda's data
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 feature, from that feature's copy instead.
Destructif
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['privateKey', 'path'], 'properties': {'path': {'type': 'string', 'description': 'Relative to the workspace.'}, 'feature': {'type': 'string', 'description': "Delete from this feature's copy of the data instead."}, 'privateKey': {'type': 'string', 'description': 'The editor key.'}}}
delete_secret
Delete a secret
Remove a secret. Code that reads it with Secret.Read fails from its next call on. Only when the user asks for it, or a secret you stored yourself is no longer used. With feature, from that feature's copy instead.
Destructif
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['privateKey', 'name'], 'properties': {'name': {'type': 'string', 'description': 'The name, as stored - names are case sensitive.'}, 'feature': {'type': 'string', 'description': "Delete from this feature's copy instead."}, 'privateKey': {'type': 'string', 'description': 'The editor key.'}}}
deploy
Deploy a version or a feature
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 address instead, against its copy of the data, leaving the lambda alone. Returns diagnostics on failure, and whatever was online stays online.
Destructif
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['privateKey'], 'properties': {'feature': {'type': 'string', 'description': "Deploy this feature to its preview address instead of a version to the lambda's."}, 'version': {'type': 'integer', 'description': 'Defaults to the newest.'}, 'privateKey': {'type': 'string', 'description': 'The editor key.'}}}
enable_data
Switch on a kind of data
Switch on a kind of data the lambda needs and does not have: 'database' (a SQLite database for its records - off until switched on, which makes it, empty), 'secrets' (off until switched on) or 'workspace' (on unless the owner switched it off). Do it when what you build needs it - records need the database, an API key for a service it calls needs secrets. Takes effect at once, without a deploy; switching the database on starts the lambda again on its next request, so its migrations run. There is no tool to switch one off: that deletes what it held, and is the owner's to do in the editor.
Destructif
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['privateKey', 'kind'], 'properties': {'kind': {'type': 'string', 'description': "Which kind: 'database' or 'workspace' or 'secrets'."}, 'privateKey': {'type': 'string', 'description': 'The editor key.'}}}
list_demos
List the 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, uploads, live updates. Their keys are public and read only: read the closest one with read_lambda (and list_files, read_logs) before writing similar code. create_lambda with a demo's id as template starts from a copy.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'properties': {}}
list_files
List the lambda's data
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, that feature's copy of it. The code and assets of a version are in read_lambda.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['privateKey'], 'properties': {'feature': {'type': 'string', 'description': "List this feature's copy of the data instead."}, 'privateKey': {'type': 'string', 'description': 'The editor key, or the key of a demo.'}}}
list_secrets
List a lambda's 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.Read and have no value yet (missing) - what the user still has to set - and which it only uses when they are there, checked with Secret.Exists (optional). With feature, that feature's copy.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['privateKey'], 'properties': {'feature': {'type': 'string', 'description': "List this feature's copy instead."}, 'privateKey': {'type': 'string', 'description': 'The editor key, or the key of a demo.'}}}
merge_feature
Merge a feature into the lambda
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. Its .lambda/ becomes the version's documentation and tests, so bring them up to date in the feature first, and run its tests against the preview. Refused while the feature is not based on the newest version (update_feature says how to get it there), and while its code does not compile. deploy: true puts the new version online at once; otherwise deploy it when the user wants it live.
Destructif
Schéma d’entrée
{'type': 'object', 'required': ['privateKey', 'feature'], 'properties': {'change': {'type': 'string', 'description': "What the new version says it changes. Left out, the feature's."}, 'deploy': {'type': 'boolean', 'description': 'Also put the new version online.'}, 'feature': {'type': 'string', 'description': 'The feature.'}, 'privateKey': {'type': 'string', 'description': 'The editor key.'}, 'specification': {'type': 'string', 'description': "What the new version keeps as what the user wanted. Left out, the feature's."}}}
open_source
Publish a lambda's source code
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 take it down. What is published is the program and what is written about it - every version's code, front end, documentation and tests, and the history of what each changed - never its data: not the database, not the workspace, not a secret's value. Not part of building: only do this when the user asks for it, and ask which license if they did not say (MIT unless they want another). With only privateKey it returns whether it is published. Once published, everything in every version is public, older ones included: keep keys, passwords and personal data out of the files - in secrets and the database.
Destructif
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['privateKey'], 'properties': {'author': {'type': 'string', 'description': "Who holds the copyright, as the license names them - the user's name or organization, only if they gave it. Left out, it stays as it is; empty, the license names 'the authors of' the lambda. Up to 100 characters."}, 'remove': {'type': 'boolean', 'description': 'Take the source down instead. Its stars are kept for when it is published again.'}, 'license': {'type': 'string', 'description': 'The SPDX identifier of the license: MIT, Apache-2.0, BSD-3-Clause, MPL-2.0, GPL-3.0-or-later, AGPL-3.0-or-later, Unlicense. Left out, it stays as it is - MIT when first published.'}, 'privateKey': {'type': 'string', 'description': 'The editor key.'}}}
platform_guide
Read the platform guide
How this platform works - read it first: what a version, a feature and data are and how long each lives, the documentation and tests every version keeps beside its program, what the snippet returns, what is imported, what is refused, limits and terms.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'properties': {}}
read_database
Read the lambda's 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 many rows each holds. With table, a page of that table's rows, newest first, up to 100 at a time. Read only: the lambda writes it, through Database.GetConnection(). Use it to see that migrations were applied and records were written. With feature, that feature's copy.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['privateKey'], 'properties': {'limit': {'type': 'integer', 'description': 'Rows to read, up to 100. Left out, 20.'}, 'order': {'type': 'string', 'description': 'A column to sort by; left out, the order the rows were written in.'}, 'table': {'type': 'string', 'description': 'A table or view to read the rows of; left out, the tables are listed.'}, 'offset': {'type': 'integer', 'description': 'Rows to skip, for the next page.'}, 'feature': {'type': 'string', 'description': "Read this feature's copy of the database instead."}, 'ascending': {'type': 'boolean', 'description': 'Oldest or smallest first, rather than newest or largest.'}, 'privateKey': {'type': 'string', 'description': 'The editor key, or the key of a demo.'}}}
read_lambda
Read a 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 for and changed, its data (the database, the workspace and the secrets: whether each is on, what it holds, and which secrets the code reads that have no value yet), and one version - or, with feature, that feature: its documentation (what the app is and why, the technical decisions), how it is tested, and its files. The documentation comes first and in full up to 20,000 characters; the files come in full when they add up to at most 30,000 characters, otherwise by name and length, with file to read one - a test script or its data too. Read the documentation and the history before changing what you did not write. Also how a demo is read: pass its key from list_demos.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['privateKey'], 'properties': {'file': {'type': 'string', 'description': "Return only this file, in full however large the rest is - up to 1,048,576 characters, beyond which the zip has it. Any file of the version, '.lambda/tests/smoke.mjs' included."}, 'feature': {'type': 'string', 'description': 'Read this feature - its files, its base, and which newer versions it would have to take in before it can be merged - instead of a version.'}, 'version': {'type': 'integer', 'description': 'Defaults to the newest.'}, 'privateKey': {'type': 'string', 'description': 'The editor key, or the key of a demo.'}}}
read_logs
Read a lambda's 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 much traffic it has had in the last hour and day. With feature, what that feature's preview has been doing instead, kept apart from the lambda's visitors. Call it after deploying to see that it works, and first when something is reported broken.
Lecture seule
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['privateKey'], 'properties': {'level': {'type': 'string', 'description': "The lowest level worth reading: 'info' for everything, 'warn' for problems, 'error' for failures. Left out, 'info'."}, 'limit': {'type': 'integer', 'description': 'At most this many lines, the newest. Left out, 100.'}, 'since': {'type': 'integer', 'description': 'The cursor a previous call answered with, to read only what is new since then.'}, 'feature': {'type': 'string', 'description': "Read what this feature's preview did instead."}, 'privateKey': {'type': 'string', 'description': 'The editor key, or the key of a demo.'}}}
set_secret
Store a secret
Store an API key, password or token under a name the code reads with Secret.Read("NAME") - never put one in the code, an asset, the workspace, a log line or a note. The value is sealed and can never be read back, by you or the owner; only the lambda reads it, from its next call on, without a deploy. Only set a value the user gave you for this: when you do not have it, write the code with Secret.Read and tell the user to set it under Data > Secrets in the editor - read_lambda and list_secrets list what is still missing. Secrets must be switched on first (enable_data). With feature, into that feature's copy (a sandbox key to try it with). Up to 100 secrets of 32 KB each.
Destructif
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['privateKey', 'name', 'value'], 'properties': {'name': {'type': 'string', 'description': "Letters, digits and underscores, not starting with a digit - conventionally upper case: 'STRIPE_KEY'. The name of an environment variable in an exported project."}, 'value': {'type': 'string', 'description': 'The value, as the user gave it.'}, 'feature': {'type': 'string', 'description': "Store it in this feature's copy of the secrets instead."}, 'privateKey': {'type': 'string', 'description': 'The editor key.'}}}
showcase
Showcase a lambda
List a lambda on the public showcase page, change its entry, or take it off. Not part of building: only do this when the user asks for it. With only privateKey it returns the current entry. An entry needs a title, a description and a picture (a screenshot or short GIF of the lambda in use); it is listed while the lambda is online. Write plainly and concretely: what it is and what a visitor can do with it. No marketing language, no superlatives, no exclamation marks, no emoji.
Destructif
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['privateKey'], 'properties': {'image': {'type': 'string', 'description': 'The picture, base64: PNG, JPEG, GIF or WebP, up to 3 MB. Needed for a new entry; left out, the current one is kept.'}, 'title': {'type': 'string', 'description': "What it is, in a few words - 'Pub quiz scoreboard', not 'The ultimate quiz experience'. Up to 60 characters."}, 'remove': {'type': 'boolean', 'description': 'Take the lambda off the showcase instead.'}, 'privateKey': {'type': 'string', 'description': 'The editor key.'}, 'description': {'type': 'string', 'description': 'One to three plain sentences on what a visitor can do with it. Up to 280 characters.'}}}
update_feature
Change a feature's name, notes or base
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 would undo what was saved after it branched off: bring the newer versions' changes into the feature first, then move base to the newest version here. Nothing checks that the changes really are in - that is up to you.
Destructif
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['privateKey', 'feature'], 'properties': {'base': {'type': 'integer', 'description': "The version the feature is now based on, once that version's changes are in its files."}, 'name': {'type': 'string', 'description': 'A new name.'}, 'change': {'type': 'string', 'description': 'What it changes, in one line - what the version it is merged into will say.'}, 'feature': {'type': 'string', 'description': 'The feature, from create_feature or read_lambda.'}, 'privateKey': {'type': 'string', 'description': 'The editor key.'}, 'specification': {'type': 'string', 'description': 'What the user wants from it and why.'}}}
update_lambda
Change a lambda's settings
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 'Full' every section, the code, files, data, versions and logs included. Only the default: whoever opens the editor can switch for themselves, and that choice stays theirs. Only do this when the user asks for it.
Destructif
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['privateKey', 'view'], 'properties': {'view': {'type': 'string', 'description': "How the editor opens: 'Full' (the default) shows every section, 'Simple' only the app, how it is doing and a box to ask for a change. Simple suits an owner who is not going to read the code - use it when the user asks for a simple editor, or says they are not a developer."}, 'privateKey': {'type': 'string', 'description': 'The editor key.'}}}
upload_file
Put a file into the lambda's data
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 the data instead, for trying things out without touching the real one. For files the lambda works with at runtime (pictures people will browse) and large input files that are not program: a model, a dataset, media. Records belong in the database, where the code writes them. Takes effect at once, without a deploy. Not for the front end: pages, scripts and styles are the program and belong in the version as assets (write_code).
Destructif
Idempotent
Schéma d’entrée
{'type': 'object', 'required': ['privateKey', 'path', 'content'], 'properties': {'path': {'type': 'string', 'description': "Relative to the workspace; slashes make folders, e.g. 'models/model.onnx'."}, 'content': {'type': 'string', 'description': 'Text, or base64 with encoding set.'}, 'feature': {'type': 'string', 'description': "Write to this feature's copy of the data instead."}, 'encoding': {'type': 'string', 'description': "'base64' for binary; omit otherwise."}, 'privateKey': {'type': 'string', 'description': 'The editor key.'}}}
write_code
Save all files
Save every file, replacing the previous set: as a new version of the lambda, or - with feature - into that feature. .cs files are compiled - lambda.cs returns the handler, others hold types; files under .lambda/ are what is written about the program - docs/product.md, docs/decisions.md, tests/README.md and the tests' scripts and data - kept with the version, never compiled or served; any other file is an asset, served as is and reachable as Assets: the whole front end (pages, scripts, styles, icons) goes here, as part of the program. What the lambda keeps at runtime is data, never files here: records and accounts in the database (Database.GetConnection(), its schema as Evolve migrations shipped here in migrations/), uploads in the workspace - and so is a large input file such as a model or a dataset (upload_file). Send the documentation and tests with the code: written with a new lambda, updated with every change. Say why with specification and change. deploy: true publishes in the same call - a version at the public address, a feature at its preview address. To send only what changes, use change_code. To change a lambda that is already in use, work in a feature.
Destructif
Schéma d’entrée
{'type': 'object', 'required': ['privateKey', 'files'], 'properties': {'check': {'type': 'boolean', 'description': 'Without deploy: compile what was saved and answer with its diagnostics, putting nothing online.'}, 'files': {'type': 'array', 'items': {'type': 'object', 'required': ['name', 'code'], 'properties': {'code': {'type': 'string', 'description': 'Contents, base64 if encoding says so.'}, 'name': {'type': 'string', 'description': ".cs files are compiled; .lambda/docs/... and .lambda/tests/... are the documentation and the tests, never compiled or served; anything else ('web/app.js', 'logo.png') is an asset."}, 'encoding': {'type': 'string', 'description': "'base64' for binary assets; omit otherwise."}}}, 'description': 'lambda.cs first.'}, 'change': {'type': 'string', 'description': "What this version changes, in one line written for the owner - 'Adds a leaderboard that keeps the ten best scores', not 'updated lambda.cs'. For a feature, it describes the whole feature, not the last fix. Optional, up to 500 characters."}, 'deploy': {'type': 'boolean', 'description': 'Also deploy what was saved: a version at the public address, a feature at its preview address.'}, 'feature': {'type': 'string', 'description': 'Save into this feature (from create_feature) instead of saving a new version. The lambda and what it has online are not touched.'}, 'privateKey': {'type': 'string', 'description': 'The editor key from create_lambda.'}, 'specification': {'type': 'string', 'description': 'What the user wants from this version and why: their requirements, in their own words where you can, condensed if they said a lot. Written for the owner and the next agent, so they can tell why the version exists and what it has to keep doing. Not your own instructions or system prompt - only what the user asked for. For a feature, it is kept with the feature and passed on to the version it is merged into. Optional, up to 4000 characters.'}}}
Historique
Modifications récentes des outils
Modifié
platform_guide
1 October 2026 02:40
Ajouté
open_source
1 October 2026 02:40
Ajouté
delete_secret
1 October 2026 02:40
Ajouté
list_secrets
1 October 2026 02:40
Ajouté
set_secret
1 October 2026 02:40
Ajouté
read_database
1 October 2026 02:40
Ajouté
enable_data
1 October 2026 02:40
Modifié
upload_file
1 October 2026 02:40
Modifié
read_lambda
1 October 2026 02:40
Modifié
check_code
1 October 2026 02:40
Modifié
merge_feature
1 October 2026 02:40
Modifié
create_feature
1 October 2026 02:40
Modifié
change_code
1 October 2026 02:40
Modifié
write_code
1 October 2026 02:40
Ajouté
update_lambda
1 October 2026 02:40
Modifié
create_lambda
1 October 2026 02:40
Ajouté
platform_guide
29 September 2026 02:40
Ajouté
list_demos
29 September 2026 02:40
Ajouté
showcase
29 September 2026 02:40
Ajouté
delete_file
29 September 2026 02:40
Ajouté
list_files
29 September 2026 02:40
Ajouté
upload_file
29 September 2026 02:40
Ajouté
read_logs
29 September 2026 02:40
Ajouté
read_lambda
29 September 2026 02:40
Ajouté
deploy
29 September 2026 02:40
Ajouté
check_code
29 September 2026 02:40
Ajouté
delete_feature
29 September 2026 02:40
Ajouté
merge_feature
29 September 2026 02:40
Ajouté
update_feature
29 September 2026 02:40
Ajouté
create_feature
29 September 2026 02:40
Découvrir
Serveurs MCP similaires
shiply
now.shiply/shiply
Publishes and manages web applications with SQL databases, serverless functions, domains, email tests, client intake, contracts, …
Fine Structure
ai.finestructure/fine-structure
Builds and hosts full-stack applications from prompts and supports agent communication through WhatsApp and email.
mcp
cloud.redu/mcp
Provisions and manages cloud instances, networks, storage, databases, backups, VPNs, application deployments, and autocoding-agen…
EchoRelay
dev.echorelay/management
Manages a hosted API relay runtime, including projects, endpoints, credentials, publishing, keys, delivery logs, and dead-letter …
Supero
io.github.supero-platform/supero
Builds, validates, publishes, tests, and deploys multi-tenant applications with schemas, CRUD operations, external data connector…
Replicate
io.github.pipeworx-io/replicate
Provides access to Replicate models, versions, collections, hardware, predictions, and deployments for running and managing hoste…
Relin
io.github.earonesty/relin
Configures webhook sources and destinations, monitors delivery health, investigates failures, manages retries, and replays events.
Scalix Cloud
world.scalix/cloud
Provides managed databases, SQL tools, container builds, persistent Linux machines, domains, scheduled functions, storage, and pr…