Workflow MCP server
{
"mcpServers": {
"cloudgate-workflow": {
"type": "http",
"url": "https://api.cloudgate.dev/mcp/workflow"
}
}
}{
"mcpServers": {
"cloudgate-workflow": {
"type": "http",
"url": "https://api.cloudgate.dev/mcp/workflow"
}
}
}{
"mcpServers": {
"cloudgate-workflow": {
"type": "http",
"url": "https://api.cloudgate.dev/mcp/workflow"
}
}
}{
"servers": {
"cloudgate-workflow": {
"type": "http",
"url": "https://api.cloudgate.dev/mcp/workflow"
}
}
}{
"mcpServers": {
"cloudgate-workflow": {
"type": "http",
"url": "https://api.cloudgate.dev/mcp/workflow"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
An MCP server for building and managing Cloudgate workflow-APIs, including controllers, actions, workflow graphs, and databases. It runs as a hosted remote server at api.cloudgate.dev and works with Claude, OpenAI Codex, and other MCP-compatible clients via OAuth authentication.
- Create and configure Cloudgate controllers and actions from an AI chat interface.
- Design and manage workflow graphs and database schemas as part of your workflow-API.
- Connect multiple MCP clients (Claude, Codex, or custom tools) to a single Cloudgate account for collaborative workflow development.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.