
Cloudgate Workflow
dev.cloudgatePublished by cloudgate.devOfficial publisherv1.0.0Updated Oct 25, 2026
Build and manage Cloudgate workflow-APIs: controllers, actions, workflow graphs, and databases.
Overview
Cloudgate Workflow is a hosted remote MCP server that lets an assistant build and manage Cloudgate workflow-APIs, including controllers, actions, workflow graph
- What you can do
- Create and manage Cloudgate controllers and actions within a workflow-API project, as described in the description and README (no individual tools are listed). Build and maintain workflow graphs and databases through the hosted server. Connect from any MCP-compatible client over streamable HTTP with OAuth sign-in, with each call scoped to the signed-in user's tenant and account. Optionally install the cloudgate-builder Claude plugin, which bundles the connection config and a build skill that guides the model through creating these resources.
- When to use it
- Use it when you work with Cloudgate and want an AI assistant to create or manage controllers, actions, workflow graphs, and databases for your workflow-APIs, from Claude, Codex, or another client that supports remote MCP servers with OAuth.
- Requirements
- A remote MCP endpoint at api.cloudgate.dev over streamable HTTP; no local runtime or package is needed. A Cloudgate account and an OAuth 2.1 sign-in (authorization code with PKCE) through the Cloudgate hub. The client must support remote MCP servers with OAuth; the packaged plugin does not launch Node.js or mcp-remote.
Installation
In SourceWeft
- Open Cloudgate Workflow 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/dev.cloudgate%2Fworkflow/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": {
"cloudgate-workflow": {
"type": "http",
"url": "https://api.cloudgate.dev/mcp/workflow"
}
}
}README
Cloudgate MCP
Build and manage Cloudgate workflow-APIs — controllers, actions, workflow graphs, and databases — from any MCP-compatible AI client, including Claude, OpenAI Codex, and others.
Cloudgate runs a hosted, remote MCP server at api.cloudgate.dev. It speaks the standard
Model Context Protocol over streamable HTTP and authenticates each user with OAuth, so any
client that supports remote MCP servers can connect. This repo also packages the server as a
ready-to-install Claude plugin for convenience.
- MCP server URL:
https://api.cloudgate.dev/mcp/workflow - Registry: listed in the official MCP Registry as
dev.cloudgate/workflow
Connect
Claude (Cowork / Desktop / Web)
- Open Customize → Plugins.
- In Personal plugins, click + → Add marketplace.
- Choose Add from a repository and enter this repo:
https://github.com/cloudgatedevs/mcp - Install cloudgate-builder from the marketplace.
- Start a chat and ask to list your Cloudgate controllers — you'll be sent to
hub.cloudgate.devto sign in, then the tools become available.
Claude Code
OpenAI Codex
Add the remote server to ~/.codex/config.toml:
Then authenticate:
Other MCP clients
Any client that supports remote (streamable HTTP) MCP servers can connect directly to
https://api.cloudgate.dev/mcp/workflow and complete the OAuth sign-in.
The packaged plugin uses native HTTP and requires a client with remote MCP OAuth support.
It does not launch Node.js or mcp-remote. The previously unpinned bridge could update
independently of the plugin; version 0.10.0 drops the authorization callback issuer when
calling its SDK. Do not replace this configuration with an unpinned bridge command.
Authentication
The Cloudgate MCP server uses OAuth 2.1 (authorization code + PKCE). Each user signs in as themselves; every MCP call is scoped to that user's tenant and account. No tokens or secrets are stored in this repository.
What's in this repo
The hosted server works on its own with any MCP client. This repo additionally ships the
cloudgate-builder Claude plugin, which bundles the connection config plus a
cloudgate-build skill — a playbook that guides the model through creating controllers,
actions, workflow graphs, and databases correctly.
License
© Cloudgate Dev LLC.
Source: README.md at commit fa54cc0
Tools
0Version history
1- v1.0.0LatestSep 16, 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.