n8n Workflow Builder
salacosteLABSCO SUMMARY
The plugin ships a playbook, not just a connection string.
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.
What it is
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.
What you get
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.
Requirements
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.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Standing up a new workflow-API by describing it
Have the model create the controller, its actions and the graph in the order the skill lays out.
02
Seeing what you already have deployed
Ask for your controllers and read them back without opening the console.
03
Wiring a database into a workflow
Create and connect it from the same conversation as the workflow itself.
04
Using it from a client with no remote-server support
Bridge the endpoint through mcp-remote and connect over stdio instead.
BEFORE YOU INSTALL
What to know first
Requires
npx on PATH
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://api.cloudgate.dev/mcp/workflowMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude plugin marketplace add cloudgatedevs/mcp
claude plugin install cloudgate-builder@cloudgate-app-templatesCodex
Add the remote server to ~/.codex/config.toml (OAuth remote servers use Codex's RMCP client):
CODEX · TOML
experimental_use_rmcp_client = true
[mcp_servers.cloudgate]
url = "https://api.cloudgate.dev/mcp/workflow"Then authenticate by running codex mcp login cloudgate, which opens the Cloudgate OAuth sign-in.
Any MCP client — mcp-remote
ANY MCP CLIENT — MCP-REMOTE · JSON
{
"mcpServers": {
"cloudgate": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://api.cloudgate.dev/mcp/workflow"
]
}
}
}
