Simplifyd Cloud MCP server
Commit 31 Okt 2026Kelola dan deploy service, database, domain, serta resource DNS pada platform Simplifyd Cloud.
Juga dikenal sebagai simplifyd-systems/cloud-mcp, cloud-mcp
- Stars
- 0
- Tools
- —
- Unduhan, 30 hari
- —
- Versi terbaru
- 0.0.44
- Commit terakhir
- 31 Okt 2026
- Lisensi
- —
Apa itu Simplifyd Cloud MCP?
Kelola dan deploy service, database, domain, serta resource DNS pada platform Simplifyd Cloud.
Ringkasan dibuat dari README proyek
Tentang Simplifyd Cloud MCP server
Simplifyd Cloud MCP Server menyediakan interface komprehensif untuk mengelola infrastruktur cloud melalui AI client. Tool ini memungkinkan developer untuk mengontrol service, database, domain, dan resource DNS. Server ini mendukung dua mode operasi yang berbeda: local stdio transport untuk single user dan streamable HTTP transport untuk deployment hosted multi-user.
Toolset ini disusun ke dalam kategori fungsional termasuk workspaces, projects, environments, dan services. Developer dapat melakukan tugas kompleks seperti deploy service, mengelola environment variables, dan memantau metrik sistem seperti penggunaan CPU dan memory. Tool ini juga menangani registry credentials untuk private images serta mengelola registrasi domain dan DNS zones. Setiap tool dilengkapi dengan anotasi spesifik untuk membantu client mengidentifikasi aksi yang bersifat read-only, destructive, atau open-world, guna memastikan interaksi yang lebih aman selama workflow otomatis.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal Simplifyd Cloud MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal Simplifyd Cloud MCP di Claude Code
$ claude mcp add --transport http cloud-mcp https://mcp.simplifyd.com/Instal Simplifyd Cloud MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"cloud-mcp": {
"url": "https://mcp.simplifyd.com/"
}
}
}Instal Simplifyd Cloud MCP di VS Code
.vscode/mcp.json
{
"servers": {
"cloud-mcp": {
"type": "http",
"url": "https://mcp.simplifyd.com/"
}
}
}Instal Simplifyd Cloud MCP di VS Code CLI
$ code --add-mcp '{"name":"cloud-mcp","type":"http","url":"https://mcp.simplifyd.com/"}'Instal Simplifyd Cloud MCP di Codex
$ codex mcp add cloud-mcp --url https://mcp.simplifyd.com/Instal Simplifyd Cloud MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.cloud-mcp] url = "https://mcp.simplifyd.com/"
Instal Simplifyd Cloud MCP di Gemini CLI
$ gemini mcp add -s user --transport http cloud-mcp https://mcp.simplifyd.com/Instal Simplifyd Cloud MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"cloud-mcp": {
"url": "https://mcp.simplifyd.com/",
"type": "http"
}
}
}Konfigurasi
MCP_TRANSPORTSIMPLIFYD_API_TOKEN
| Nama | Deskripsi | Tipe |
|---|---|---|
| MCP_TRANSPORT | — | |
| SIMPLIFYD_API_TOKEN | — |
Pengecekan otomatis
Berjalan 15 Nov 2026Laporan lengkap →Belum diverifikasi. Sebuah server memerlukan skor 80, tidak ada temuan serius, dan data yang cukup untuk kami periksa. Cara kerja checks · Yang perlu diperbaiki untuk menambah poin
- Source repository terhubung dan dapat dijangkausimplifyd-systems/cloud-mcp is public and reachablegithub.com/simplifyd-systems/cloud-mcp ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernyaTidak diperiksa
- Provenance build (atestasi Sigstore)Tidak diperiksa
- Lisensi open source (OSI)No licenseTemuan
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-10-31github.com/simplifyd-systems/cloud-mcp ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerTidak diperiksa
- Tidak ada advisory kritis pada paket atau dependensinyaTidak diperiksa
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote merespons handshake MCPHTTPS endpoint answered 401 (sign-in required)Lolos
README
Lihat di 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.
Pertanyaan tentang Simplifyd Cloud MCP
Bagaimana cara menambahkan Simplifyd Cloud MCP ke Claude Code?
Jalankan claude mcp add --transport http cloud-mcp https://mcp.simplifyd.com/ di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan Simplifyd Cloud MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Apakah server ini mendukung HTTP transport untuk deployment multi-user?
Ya, server ini mendukung streamable HTTP untuk deployment hosted multi-user di mana setiap request menyertakan Authorization header masing-masing.