MCP server de Simplifyd Cloud
Commit 31 oct 2026Gestiona y despliega servicios, bases de datos, dominios y recursos de DNS en la plataforma Simplifyd Cloud.
También conocido como simplifyd-systems/cloud-mcp, cloud-mcp
- Stars
- 0
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- 0.0.44
- Último commit
- 31 oct 2026
- Licencia
- —
¿Qué es Simplifyd Cloud MCP?
Gestiona y despliega servicios, bases de datos, dominios y recursos de DNS en la plataforma Simplifyd Cloud.
Resumen generado a partir del README del proyecto
Acerca del MCP server de Simplifyd Cloud
El Simplifyd Cloud MCP Server proporciona una interfaz completa para gestionar infraestructura en la nube a través de un cliente de IA. Permite a los desarrolladores controlar servicios, bases de datos, dominios y recursos de DNS. El servidor admite dos modos de operación distintos: un transporte local vía stdio para usuarios individuales y un transporte streamable HTTP para despliegues alojados multiusuario. Los usuarios locales pueden autenticarse mediante un token de API o la herramienta de login, mientras que los usuarios de HTTP proporcionan un bearer token con cada solicitud.
El conjunto de herramientas está organizado en categorías funcionales que incluyen workspaces, proyectos, entornos y servicios. Los desarrolladores pueden realizar tareas complejas como desplegar servicios, gestionar variables de entorno y monitorear métricas del sistema como el uso de CPU y memoria. También gestiona credenciales de registro para imágenes privadas y administra el registro de dominios y zonas DNS. Cada herramienta incluye anotaciones específicas para ayudar a los clientes a identificar acciones de solo lectura, destructivas o de mundo abierto, garantizando interacciones más seguras durante los flujos de trabajo automatizados.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar Simplifyd Cloud MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar Simplifyd Cloud MCP en Claude Code
$ claude mcp add --transport http cloud-mcp https://mcp.simplifyd.com/Instalar Simplifyd Cloud MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"cloud-mcp": {
"url": "https://mcp.simplifyd.com/"
}
}
}Instalar Simplifyd Cloud MCP en VS Code
.vscode/mcp.json
{
"servers": {
"cloud-mcp": {
"type": "http",
"url": "https://mcp.simplifyd.com/"
}
}
}Instalar Simplifyd Cloud MCP en VS Code CLI
$ code --add-mcp '{"name":"cloud-mcp","type":"http","url":"https://mcp.simplifyd.com/"}'Instalar Simplifyd Cloud MCP en Codex
$ codex mcp add cloud-mcp --url https://mcp.simplifyd.com/Instalar Simplifyd Cloud MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.cloud-mcp] url = "https://mcp.simplifyd.com/"
Instalar Simplifyd Cloud MCP en Gemini CLI
$ gemini mcp add -s user --transport http cloud-mcp https://mcp.simplifyd.com/Instalar Simplifyd Cloud MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"cloud-mcp": {
"url": "https://mcp.simplifyd.com/",
"type": "http"
}
}
}Configuración
MCP_TRANSPORTSIMPLIFYD_API_TOKEN
| Nombre | Descripción | Tipo |
|---|---|---|
| MCP_TRANSPORT | — | |
| SIMPLIFYD_API_TOKEN | — |
Verificaciones automáticas
Ejecutado 15 nov 2026Informe completo →Aún no verificado. Un servidor necesita una puntuación de 80, ningún hallazgo grave y suficientes datos para que podamos revisarlo. Cómo funcionan las verificaciones · Qué corregir para obtener más puntos
- Repositorio de origen vinculado y accesiblesimplifyd-systems/cloud-mcp is public and reachablegithub.com/simplifyd-systems/cloud-mcp ↗Aprobado
- El paquete indica este repositorio como su origenNo verificado
- Procedencia de la compilación (atestación de Sigstore)No verificado
- Licencia de código abierto (OSI)No licenseHallazgo
- Commit o lanzamiento en el último añoLast commit or release 2026-10-31github.com/simplifyd-systems/cloud-mcp ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo verificado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
- Sin instrucciones ocultas para el modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo verificado
- El endpoint remoto responde al handshake de MCPHTTPS endpoint answered 401 (sign-in required)Aprobado
README
Ver en GitHubSimplifyd 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.
Preguntas sobre Simplifyd Cloud MCP
¿Cómo agrego Simplifyd Cloud MCP a Claude Code?
Ejecuta claude mcp add --transport http cloud-mcp https://mcp.simplifyd.com/ en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego Simplifyd Cloud MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿El servidor soporta transporte HTTP para despliegues multiusuario?
Sí, el servidor soporta streamable HTTP para despliegues alojados multiusuario donde cada solicitud incluye su propio encabezado de Authorization.