
Simplifyd Cloud
com.simplifydPublished by simplifyd.comOfficial publisherv0.0.44Updated Oct 30, 2026
Deploy and manage services, databases, domains and DNS on Simplifyd Cloud.
Overview
Simplifyd Cloud MCP server lets an assistant deploy and manage cloud services, databases, domains, DNS and workspaces on Simplifyd Cloud.
- What you can do
- Manage workspaces, projects, environments and environment variables, including members, funding and registry credentials
- Create, update and delete services, with variables, ingress, TCP proxies, configs and changeset approval
- Deploy, redeploy and undeploy services and read deployment logs
- Read CPU, memory and disk metrics for services and environments
- Search, quote, register and renew domains, and manage DNS zones and records
- List and deploy templates, manage API tokens, and set up email domains
- When to use it
- Useful when you run workloads on Simplifyd Cloud and want an assistant to inspect or change infrastructure from chat: deploying a service, checking metrics or logs, adjusting environment variables, or editing DNS records without switching to the console.
- Requirements
- Remote endpoint at mcp.simplifyd.com over streamable HTTP with OAuth, or a self-hosted binary over stdio or HTTP. Each request needs an Authorization Bearer token, created with the create-token tool or in the dashboard; the stdio build reads SIMPLIFYD_API_TOKEN or a local config file. A Simplifyd Cloud account is required.
Installation
In SourceWeft
- Open Simplifyd Cloud in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.simplifyd%2Fcloud/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"simplifyd-cloud": {
"type": "http",
"url": "https://mcp.simplifyd.com/"
}
}
}README
Simplifyd 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
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
Transports
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):
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):
Or if you prefer to authenticate interactively (omit SIMPLIFYD_API_TOKEN and run login first):
http
Run the server:
Point a client at it, passing your API token as a header:
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.
Source: README.md at commit 5280ded
Tools
0Version history
1- v0.0.44LatestOct 30, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.