MCP Server

The Simplifyd Cloud MCP Server is a Model Context Protocol (MCP) server for Simplifyd Cloud workspaces, projects, services, and deployments.

The MCP server is open-source and lives in the cloud-mcp repository.

Understanding MCP and the Simplifyd Cloud MCP Server

The Model Context Protocol (MCP) defines a standard way for compatible applications to call external tools and data sources.

Hosts: Applications such as Claude Code, Cursor, VS Code, or Claude Desktop that connect to MCP servers.
Servers: Standalone programs, such as the Simplifyd Cloud MCP Server, that expose tools over MCP.

The Simplifyd Cloud MCP Server exposes authenticated Simplifyd Cloud operations as MCP tools.

Prerequisites

Homebrew to install the server on macOS, or a pre-built binary from the releases page
A Simplifyd Cloud account — sign up at console.cloud.simplifyd.com
A valid API token (or your account credentials to authenticate interactively)

Install

Install the MCP server from the Simplifyd Homebrew tap:

brew tap simplifyd-systems/tap
brew install --cask cloud-mcp

Verify the installation:

cloud-mcp --version

If you are not using Homebrew, download the right archive for your operating system from the GitHub releases page, extract it, and use the absolute path to the cloud-mcp binary when configuring your MCP client.

Configure your MCP client

Run the following command to register the server with Claude Code:

claude mcp add simplifyd-cloud cloud-mcp \
  -e SIMPLIFYD_API_TOKEN=<your-token>

To verify the server is running:

claude mcp list

Create or edit ~/.cursor/mcp.json:

{
  "mcpServers": {
    "simplifyd-cloud": {
      "command": "cloud-mcp",
      "env": {
        "SIMPLIFYD_API_TOKEN": "<your-token>"
      }
    }
  }
}

Restart Cursor after saving the file.

Create or edit .vscode/mcp.json in your workspace (or the global user settings):

{
  "servers": {
    "simplifyd-cloud": {
      "type": "stdio",
      "command": "cloud-mcp",
      "env": {
        "SIMPLIFYD_API_TOKEN": "<your-token>"
      }
    }
  }
}

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "simplifyd-cloud": {
      "command": "cloud-mcp",
      "env": {
        "SIMPLIFYD_API_TOKEN": "<your-token>"
      }
    }
  }
}

Restart Claude Desktop after saving.

Obtaining a token

You can get your API token from any of these sources:

Login tool — omit SIMPLIFYD_API_TOKEN from the config and use the login MCP tool on first use. The server will save the token to ~/.simplifyd/config.json and reuse it automatically.
Dashboard — go to Project Settings → Tokens, create a token scoped to your environment, and copy it.
CLI — run edge token create --name "MCP" and copy the output.

Example usage

Once the server is connected, your MCP host can call Simplifyd Cloud tools. Common requests include:

Deploy a Docker service:

"Create a service called api using the nginx:latest image in my production environment and deploy it."

Check deployment status:

"What's the status of the latest deployment for the api service?"

Tail deployment logs:

"Show me the logs for the last deployment of api in the staging environment."

Manage environment variables:

"Set DATABASE_URL and REDIS_URL on the api service in production."

Scale a service:

"Scale the api service to 3 replicas and give it 2 vCPUs."

Add a public URL:

"Add an HTTPS ingress on port 8080 for the api service."

Invite a team member:

"Add alice@example.com to my acme workspace."

Check billing:

"How much have I spent this month in the acme workspace?"

Available MCP tools

The server exposes 57 tools grouped by resource type.

Authentication

Tool	Description
`login`	Log in with your email and password. Saves the session token to `~/.simplifyd/config.json`.
`get-me`	Return the profile of the currently authenticated user.

Workspaces

Tool	Description
`list-workspaces`	List all workspaces accessible to the authenticated user.
`get-workspace`	Get details of a specific workspace including wallet balance and projects.
`create-workspace`	Create a new workspace.
`update-workspace`	Update the display name of an existing workspace.
`get-workspace-usage`	Get current-month billing usage (CPU, memory, data costs).
`get-workspace-transactions`	List billing transactions (credits and debits).
`get-my-role`	Get the authenticated user's role in a workspace.
`list-workspace-members`	List all members of a workspace.
`add-workspace-member`	Invite a user by email address.
`update-member-role`	Update a workspace member's role.
`remove-workspace-member`	Remove a member from a workspace.
`fund-workspace`	Initiate a wallet top-up via Paystack, Stripe, or bank transfer.
`get-registry`	Get the workspace registry details.
`get-registry-credentials`	Get short-lived registry credentials.
`list-registry-repos`	List repositories in the workspace registry.

Projects

Tool	Description
`list-projects`	List all projects in a workspace.
`get-project`	Get details of a specific project.
`create-project`	Create a new project inside a workspace.
`update-project`	Rename an existing project.

Environments

Tool	Description
`list-environments`	List all environments in a project.
`get-environment`	Get environment details including services and variables.
`create-environment`	Create a new environment inside a project.
`update-environment`	Rename an existing environment.
`list-env-variables`	List all shared environment variables.
`create-env-variable`	Create or update a shared environment variable by name.
`update-env-variable`	Update the value of an existing variable.
`delete-env-variable`	Delete a shared environment variable by name or slug.

Services

Tool	Description
`list-services`	List all services in an environment.
`get-service`	Get full service details: status, config, variables, ingress rules.
`create-service`	Create a Docker, Postgres, Redis, HTTP gateway, or S3 bucket service.
`update-service`	Update service name, vCPUs, memory, image, tag, or start command.
`delete-service`	Delete a service and all its resources.
`list-service-variables`	List environment variables set on a service.
`add-service-variable`	Add or update a single environment variable on a service.
`set-service-variables`	Bulk-set environment variables on a service.
`delete-service-variable`	Delete a specific service environment variable by name or slug.
`add-service-ingress`	Create an HTTP, gRPC, TCP, or UDP ingress rule.
`delete-service-ingress`	Remove an ingress rule by FQDN.
`add-tcp-proxy`	Expose a service port externally via TCP proxy.
`delete-tcp-proxy`	Remove a TCP proxy from a service.
`add-service-config`	Add a config file mount to a service.
`update-service-config`	Update an existing service config file mount.
`delete-service-config`	Delete a service config file mount.
`approve-service-changeset`	Approve and deploy a service's pending changeset.
`discard-service-changeset`	Discard a service's pending changeset.
`add-shared-variable`	Link a shared environment variable into a specific service.

Deployments

Tool	Description
`list-deployments`	List all deployments for a service, most recent first.
`get-deployment`	Get deployment details: status, resource allocation, timestamps.
`deploy-service`	Deploy a service, optionally specifying a new image or resource limits.
`redeploy-service`	Redeploy the active deployment (useful after config or variable changes).
`undeploy-service`	Stop and remove the active deployment without deleting the service.
`get-deployment-logs`	Fetch logs for a specific deployment.

API Tokens

Tool	Description
`list-tokens`	List all API tokens for a project.
`create-token`	Create a new project token scoped to a specific environment.
`delete-token`	Revoke a project API token.

Security considerations

The MCP server uses your API token to make real changes to your infrastructure. Take the following precautions.

Review actions before they execute. Most MCP clients show the tool call and its arguments before running. Read them carefully, especially for destructive operations like delete-service or undeploy-service.
Use scoped tokens. Create a dedicated token with access only to the required environments. Avoid using your personal token from edge auth login.
Start in non-production environments when testing a new MCP setup. Use a staging or dev environment first.
Do not share your ~/.simplifyd/config.json. It contains your authentication token in plain text.
Rotate tokens regularly. If you suspect a token has been compromised, revoke it immediately from the dashboard or with edge token delete <slug>.

Feature requests

The MCP server is open source. If a tool or workflow is missing, open an issue or pull request in the cloud-mcp repository.

MCP Server

On this page