Simplifyd Cloud MCP server
Commit 31. Okt. 2026Verwalte und deploye Services, Datenbanken, Domains und DNS-Ressourcen auf der Simplifyd Cloud Plattform.
Auch bekannt als simplifyd-systems/cloud-mcp, cloud-mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 Tage
- —
- Neueste Version
- 0.0.44
- Letzter Commit
- 31. Okt. 2026
- Lizenz
- —
Was ist Simplifyd Cloud MCP?
Verwalte und deploye Services, Datenbanken, Domains und DNS-Ressourcen auf der Simplifyd Cloud Plattform.
Zusammenfassung generiert aus dem README des Projekts
Über Simplifyd Cloud MCP server
Der Simplifyd Cloud MCP Server bietet eine umfassende Schnittstelle, um Cloud-Infrastruktur über einen AI-Client zu verwalten. Er ermöglicht es Entwicklern, Services, Datenbanken, Domains und DNS-Ressourcen zu steuern. Der Server unterstützt zwei verschiedene Betriebsmodi: einen lokalen stdio-Transport für Einzelnutzer und einen streamable HTTP-Transport für Multi-User, gehostete Deployments. Lokale Nutzer können sich über einen API-Token oder das Login-Tool authentifizieren, während HTTP-Nutzer bei jeder Anfrage einen Bearer-Token bereitstellen.
Das Toolset ist in funktionale Kategorien unterteilt, darunter Workspaces, Projekte, Environments und Services. Entwickler können komplexe Aufgaben wie das Deployen von Services, das Verwalten von Umgebungsvariablen und das Monitoring von Systemmetriken wie CPU- und Speicherauslastung durchführen. Er verwaltet zudem Registry-Credentials für private Images sowie die Domain-Registrierung und DNS-Zones. Jedes Tool enthält spezifische Annotationen, die Clients dabei helfen, Read-only-, destructive oder Open-World-Aktionen zu identifizieren, um sicherere Interaktionen während automatisierter Workflows zu gewährleisten.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du Simplifyd Cloud MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenSimplifyd Cloud MCP in Claude Code installieren
$ claude mcp add --transport http cloud-mcp https://mcp.simplifyd.com/Simplifyd Cloud MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"cloud-mcp": {
"url": "https://mcp.simplifyd.com/"
}
}
}Simplifyd Cloud MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"cloud-mcp": {
"type": "http",
"url": "https://mcp.simplifyd.com/"
}
}
}Simplifyd Cloud MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"cloud-mcp","type":"http","url":"https://mcp.simplifyd.com/"}'Simplifyd Cloud MCP in Codex installieren
$ codex mcp add cloud-mcp --url https://mcp.simplifyd.com/Simplifyd Cloud MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.cloud-mcp] url = "https://mcp.simplifyd.com/"
Simplifyd Cloud MCP in Gemini CLI installieren
$ gemini mcp add -s user --transport http cloud-mcp https://mcp.simplifyd.com/Simplifyd Cloud MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"cloud-mcp": {
"url": "https://mcp.simplifyd.com/",
"type": "http"
}
}
}Konfiguration
MCP_TRANSPORTSIMPLIFYD_API_TOKEN
| Name | Beschreibung | Typ |
|---|---|---|
| MCP_TRANSPORT | — | |
| SIMPLIFYD_API_TOKEN | — |
Automatisierte Checks
Geluften am 15. Nov. 2026Vollständiger Bericht →Noch nicht verifiziert. Ein Server benötigt einen Score von 80, keine kritischen Befunde und genug Daten für unsere Prüfung. Wie die Checks funktionieren · Was du für mehr Punkte verbessern kannst
- Source Repository verknüpft und erreichbarsimplifyd-systems/cloud-mcp is public and reachablegithub.com/simplifyd-systems/cloud-mcp ↗Bestanden
- Paket nennt dieses Repository als QuelleNicht geprüft
- Build-Provenienz (Sigstore-Attestierung)Nicht geprüft
- Open Source Lizenz (OSI)No licenseBefund
- Commit oder Release im letzten JahrLast commit or release 2026-10-31github.com/simplifyd-systems/cloud-mcp ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNicht geprüft
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenNicht geprüft
- Keine versteckten Anweisungen an das Modell0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNicht geprüft
- Remote-Endpoint beantwortet den MCP-HandshakeHTTPS endpoint answered 401 (sign-in required)Bestanden
README
Auf GitHub ansehenSimplifyd Cloud MCP Server
An MCP (Model Context Protocol) server for the Simplifyd Cloud platform.
It exposes tools for managing Simplifyd Cloud resources from MCP-enabled clients,
over either stdio (a local client launches the binary as a subprocess) or
streamable HTTP (a hosted, multi-user deployment). One binary serves both;
MCP_TRANSPORT selects.
Tools
| Category | Tools |
|---|---|
| Auth | login (stdio only), get-me |
| Workspaces | list-workspaces, get-workspace, create-workspace, update-workspace, get-workspace-usage, get-workspace-transactions, get-my-role, list-workspace-members, add-workspace-member, update-member-role, remove-workspace-member, fund-workspace, get-registry, list-registry-repos, list-registry-artifacts, delete-registry-tag |
| Registry credentials | list-registry-credentials, add-registry-credential, update-registry-credential, remove-registry-credential — a workspace's pull credentials for private registries (ghcr.io, Docker Hub, ...), inherited by its Docker image services by registry. A service's own credentials are set with update-service and its registry_credentials / clear_registry_credentials actions |
| Projects | list-projects, get-project, create-project, update-project |
| Environments | list-environments, get-environment, create-environment, update-environment, list-env-variables, create-env-variable, update-env-variable, delete-env-variable |
| Services | list-services, get-service, create-service, update-service, delete-service, list-private-service-access, grant-private-service-access, revoke-private-service-access, list-service-variables, add-service-variable, set-service-variables, delete-service-variable, add-service-ingress, delete-service-ingress, add-tcp-proxy, delete-tcp-proxy, set-ingress-source-ranges, add-service-config, update-service-config, delete-service-config, approve-service-changeset, discard-service-changeset, add-shared-variable |
| Deployments | list-deployments, get-deployment, deploy-service, redeploy-service, undeploy-service, get-deployment-logs |
| Metrics | get-service-metrics, get-environment-metrics — CPU, memory and disk over the last 1h, 6h or 1d as a percentage of allocation, with scaling signals |
| Tokens | list-tokens, create-token, delete-token |
| Templates | list-templates, get-template, deploy-template, get-publishable-variables |
list-email-domains, add-email-domain, verify-email-domain, remove-email-domain — create the service itself with create-service and type email |
|
| Domains | search-domains, quote-domain, list-domains, get-domain, register-domain (stdio only), renew-domain (stdio only), update-domain. Buying and renewing charge the wallet only on a second, confirming call; the hosted server leaves them out, since the Claude and ChatGPT directories refuse tools that spend money, and people buy and renew in the console instead. |
| DNS | list-dns-zones, add-dns-zone, check-dns-zone, delete-dns-zone, list-dns-records, add-dns-record, update-dns-record, delete-dns-record |
Every tool carries a title and explicit readOnlyHint, destructiveHint and
openWorldHint annotations, which clients use to decide when to ask before
calling it. The classification lives in tools/annotations.go, and a test
fails if a tool is added without one.
Directory listings
server.json describes the hosted server for the
MCP Registry, which registry-aware
clients such as Lovable browse. Bump its version with each release and publish
with mcp-publisher publish.
Build
go build -o cloud-mcp .
Transports
| Variable | Default | Meaning |
|---|---|---|
MCP_TRANSPORT |
stdio |
stdio or http |
MCP_ADDR |
:8080 |
Listen address (http only) |
MCP_ALLOWED_ORIGINS |
(none) | Comma-separated browser origin allowlist (http only) |
SIMPLIFYD_API_URL |
https://api.cloud.simplifyd.com |
API base URL |
OPENAI_APPS_CHALLENGE |
(none) | Domain verification token from OpenAI's plugin portal, served at /.well-known/openai-apps-challenge (http only) |
Under HTTP the MCP endpoint answers on the bare origin and on /mcp, with
a plain /healthz for probes.
Sessions are stateless, so replicas need no sticky routing.
Authentication
Authentication is per-transport, and the two never mix:
- stdio — a single local user. The token comes from
SIMPLIFYD_API_TOKENor~/.simplifyd/config.json, and thelogintool can set it interactively. - http — many callers. Each request must carry its own
Authorization: Bearer <token>, which is used for that call and nothing else. Nothing is persisted, no credential is shared between callers, andloginis not registered, since it would write one caller's credentials to the server's disk and apply them to everyone else.
stdio
Option 1 — Environment variable (recommended for CI):
export SIMPLIFYD_API_TOKEN="your-jwt-token"
Option 2 — Interactive login:
Use the login tool to authenticate with your email and password. The token is saved to ~/.simplifyd/config.json and reused automatically on subsequent runs.
Claude Code Configuration
Add to your MCP settings (.claude/settings.json or ~/.claude/settings.json):
{
"mcpServers": {
"simplifyd-cloud": {
"command": "/path/to/cloud/mcp/cloud-mcp",
"env": {
"SIMPLIFYD_API_TOKEN": "your-jwt-token"
}
}
}
}
Or if you prefer to authenticate interactively (omit SIMPLIFYD_API_TOKEN and run login first):
{
"mcpServers": {
"simplifyd-cloud": {
"command": "/path/to/cloud/mcp/cloud-mcp"
}
}
}
http
Run the server:
MCP_TRANSPORT=http MCP_ADDR=:8080 ./cloud-mcp
Point a client at it, passing your API token as a header:
{
"mcpServers": {
"simplifyd-cloud": {
"type": "http",
"url": "https://mcp.simplifyd.com",
"headers": {
"Authorization": "Bearer your-jwt-token"
}
}
}
}
Create a token with the create-token tool, or in the dashboard.
Security
Requests carrying an Origin header are refused unless the origin is listed in
MCP_ALLOWED_ORIGINS. This blocks DNS-rebinding attacks, where a page in a
user's browser would otherwise be able to drive a hosted server. Non-browser
clients send no Origin and are unaffected.
Normal resource responses omit variable values, passwords, connection URLs, credential blobs, and config-file contents. Tools whose descriptions say they explicitly reveal credentials return sensitive data by design; use them only when needed and avoid copying their output into logs or tickets.
Deployment logs are filtered for common credential patterns, but applications can emit secrets in unexpected formats. Review log output before sharing it.
Simplifyd Cloud MCP Fragen
Wie füge ich Simplifyd Cloud MCP zu Claude Code hinzu?
Führe claude mcp add --transport http cloud-mcp https://mcp.simplifyd.com/ in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich Simplifyd Cloud MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Unterstützt der Server HTTP-Transport für Multi-User-Deployments?
Ja, der Server unterstützt streamable HTTP für gehostete Multi-User-Deployments, bei denen jede Anfrage ihren eigenen Authorization-Header mitführt.