The hosted server works with any client on its own; what the repository adds is the `cloudgate-build` skill, which tells the model the right order to create controllers, actions and workflow graphs in. That is the difference between a model that can call the API and one that builds something coherent with it.
A hosted, remote server for the Cloudgate platform. It speaks Model Context Protocol over streamable HTTP and signs each user in with OAuth, so every call is scoped to that person's own tenant and account rather than to a shared key.
Tools for building and managing Cloudgate workflow-APIs: controllers, actions, workflow graphs and databases. The repository also ships the `cloudgate-builder` Claude plugin, which bundles the connection config plus a `cloudgate-build` skill — a playbook that walks the model through creating those objects correctly.
An account you can sign into at `hub.cloudgate.dev`. Any client that supports remote streamable-HTTP servers connects straight to `https://api.cloudgate.dev/mcp/workflow` and completes an OAuth 2.1 sign-in with authorization code and PKCE. In Claude Code: `claude plugin marketplace add cloudgatedevs/mcp` then `claude plugin install cloudgate-builder@cloudgate-app-templates`. For stdio-only clients, bridge with `npx -y mcp-remote https://api.cloudgate.dev/mcp/workflow`. Listed in the official MCP Registry as `dev.cloudgate/workflow`.
One command — npx -y mcp-remote https://api.cloudgate.dev/mcp/workflow