Add CreateOS MCP plugin — 85+ deployment tools

.cursor-plugin/marketplace.json

@@ -32,6 +32,11 @@
       "name": "ralph-loop",
       "source": "ralph-loop",
       "description": "Iterative self-referential AI loops using the Ralph Wiggum technique."
+    },
+    {
+      "name": "createos-mcp",
+      "source": "createos-mcp",
+      "description": "Deploy and manage full-stack applications with 85+ MCP tools. GitHub repos, Docker, AI agents, environments, domains, security, and analytics."
     }
   ]
 }

createos-mcp/.cursor-plugin/plugin.json

@@ -0,0 +1,94 @@
+{
+  "name": "createos-mcp",
+  "displayName": "CreateOS MCP",
+  "version": "1.0.0",
+  "description": "Deploy and manage full-stack applications from your editor. 85+ MCP tools for GitHub repos, Docker containers, AI agents, and more with environments, domains, security scanning, analytics, and a template marketplace.",
+  "author": {
+    "name": "NodeOps",
+    "email": "naman@nodeops.xyz"
+  },{
+  "name": "createos-mcp",
+  "displayName": "CreateOS MCP",
+  "version": "1.0.0",
+  "description": "Deploy and manage full-stack applications from your editor. 85+ MCP tools for GitHub repos, Docker containers, AI agents, and more with environments, domains, security scanning, analytics, and a template marketplace.",
+  "author": {
+    "name": "NodeOps",
+    "email": "naman@nodeops.network"
+  },
+  "publisher": "NodeOps",
+  "homepage": "https://createos.nodeops.network",
+  "repository": "https://github.com/NodeOps-app/createos-mcp",
+  "license": "MIT",
+  "keywords": [
+    "deployment",
+    "hosting",
+    "cloud",
+    "docker",
+    "github",
+    "devops",
+    "infrastructure",
+    "mcp",
+    "createos",
+    "nodeops",
+    "ai-agents",
+    "databases",
+    "security",
+    "domains",
+    "environments",
+    "analytics"
+  ],
+  "category": "cloud-infrastructure",
+  "tags": [
+    "deployment",
+    "cloud",
+    "mcp-server",
+    "devops",
+    "ai-agents"
+  ],
+  "skills": "./skills/",
+  "agents": "./agents/",
+  "rules": "./rules/",
+  "mcpServers": {
+    "createos-mcp": {
+      "url": "https://api-createos.nodeops.network/mcp"
+    }
+  }
+}  "publisher": "NodeOps",
+  "homepage": "https://createos.nodeops.network",
+  "repository": "https://github.com/NodeOps-app/createos-mcp",
+  "license": "MIT",
+  "keywords": [
+    "deployment",
+    "hosting",
+    "cloud",
+    "docker",
+    "github",
+    "devops",
+    "infrastructure",
+    "mcp",
+    "createos",
+    "nodeops",
+    "ai-agents",
+    "databases",
+    "security",
+    "domains",
+    "environments",
+    "analytics"
+  ],
+  "category": "cloud-infrastructure",
+  "tags": [
+    "deployment",
+    "cloud",
+    "mcp-server",
+    "devops",
+    "ai-agents"
+  ],
+  "skills": "./skills/",
+  "agents": "./agents/",
+  "rules": "./rules/",
+  "mcpServers": {
+    "createos-mcp": {
+      "url": "https://api-createos.nodeops.network/mcp"
+    }
+  }
+}

createos-mcp/CHANGELOG.md

@@ -0,0 +1,11 @@
+# Changelog
+
+## 1.0.0
+
+- Initial release
+- 85+ MCP tools for full-stack deployment management
+- Skills: deploy, manage-environments, security-scan
+- Agent: deployment-monitor for background build tracking
+- Rules: CreateOS best practices
+- Support for GitHub, Docker, and file-based deployments
+- 11 runtimes and 15 frameworks supported

createos-mcp/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 NodeOps
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

createos-mcp/README.md

@@ -0,0 +1,53 @@
+# CreateOS MCP plugin
+
+Deploy and manage full-stack applications directly from Cursor using the CreateOS platform by NodeOps.
+
+## Installation
+
+```bash
+/add-plugin createos-mcp
+```
+
+## Components
+
+### Skills
+
+| Skill | Description |
+|:------|:------------|
+| `deploy` | Deploy applications from GitHub repos, Docker images, or file uploads |
+| `manage-environments` | Create and configure staging, production, and custom environments |
+| `security-scan` | Run and review security scans on deployed applications |
+
+### Agents
+
+| Agent | Description |
+|:------|:------------|
+| `deployment-monitor` | Monitor deployments and report build status, errors, and runtime health |
+
+### Rules
+
+| Rule | Description |
+|:-----|:------------|
+| `createos-best-practices` | Best practices for deploying and managing applications with CreateOS |
+
+### MCP Server
+
+Connects to the CreateOS MCP endpoint at `https://api-createos.nodeops.network/mcp` providing 85+ tools across 14 domains: projects, deployments, environments, domains, apps, templates, API keys, security, analytics, logs, GitHub integration, file uploads, account management, and project transfers.
+
+## Supported runtimes
+
+Node.js 18/20/22, Python 3.11/3.12, Go 1.22/1.25, Rust 1.75, Bun 1.1/1.3, and static sites.
+
+## Supported frameworks
+
+Next.js, React (SPA/SSR), Vue.js (SPA/SSR), Nuxt, Astro, Remix, Express, FastAPI, Flask, Django, Gin, Fiber, and Actix.
+
+## Links
+
+- [CreateOS Dashboard](https://createos.nodeops.network)
+- [GitHub Repository](https://github.com/NodeOps-app/createos-mcp)
+- [NodeOps](https://nodeops.network)
+
+## License
+
+MIT

createos-mcp/agents/deployment-monitor.md

@@ -0,0 +1,28 @@
+---
+name: deployment-monitor
+description: Monitor CreateOS deployments and report build status, errors, and runtime health. Use when waiting for a deployment to finish or when a deployment has failed.
+model: fast
+is_background: true
+---
+
+# Deployment monitor
+
+Deployment monitoring specialist for CreateOS.
+
+## Trigger
+
+Use when waiting for a deployment to complete, a build has failed, or when proactively checking deployment health.
+
+## Workflow
+
+1. List recent deployments: `ListDeployments` for the target project.
+2. Check deployment status: `GetDeployment` for the latest deployment.
+3. If building: poll status until "deployed" or "failed".
+4. If failed: fetch build logs with `GetBuildLogs` and extract the root error.
+5. If deployed: verify with `GetDeploymentLogs` for runtime errors.
+
+## Output
+
+- Deployment status (queued, building, deploying, deployed, failed, sleeping)
+- If failed: concise error excerpt and suggested fix
+- If deployed: live URL and health confirmation

createos-mcp/rules/createos-best-practices.mdc

@@ -0,0 +1,19 @@
+---
+description: Best practices for deploying and managing applications with CreateOS MCP
+alwaysApply: false
+---
+
+# CreateOS best practices
+
+When deploying or managing infrastructure with CreateOS MCP tools:
+
+- Use CreateOS MCP tools for all deployment operations instead of manual API calls.
+- Always check for existing projects with `ListProjects` before creating new ones.
+- Use environment variables for secrets and configuration — never hardcode credentials.
+- Create separate environments (staging, production) for proper deployment workflows.
+- Run `TriggerSecurityScan` after deploying new code to production.
+- Check `GetBuildLogs` when deployments fail before retrying.
+- Use descriptive, lowercase names with hyphens for projects and environments (4-32 chars).
+- When deploying from GitHub, verify the repo is connected via `ListConnectedGithubAccounts` first.
+- Confirm destructive operations (delete project, deployment, environment) with the user before executing.
+- Resource limits: CPU 200-500 millicores, Memory 500-1024 MB, Replicas 1-3.

createos-mcp/skills/deploy/SKILL.md

@@ -0,0 +1,37 @@
+---
+name: deploy
+description: Deploy applications to CreateOS from GitHub repos, Docker images, or file uploads
+---
+
+# Deploy
+
+## Trigger
+
+User wants to deploy, host, ship, launch, or put an application online.
+
+## Workflow
+
+1. Check existing projects: `ListProjects` to avoid duplicates.
+2. Determine deployment type:
+   - **GitHub repo** — use `ListConnectedGithubAccounts`, then `ListGithubRepositories` to find the repo. Create a VCS project with `CreateProject` (type: "vcs").
+   - **Docker image** — create an image project with `CreateProject` (type: "image"), then `CreateDeployment` with the image reference.
+   - **File upload** — create an upload project with `CreateProject` (type: "upload"), then use `UploadDeploymentFiles` or `UploadDeploymentBase64Files`.
+3. Create an environment if none exists: `CreateProjectEnvironment` with resource limits (CPU: 200-500m, Memory: 500-1024MB, Replicas: 1-3).
+4. Set environment variables: `UpdateProjectEnvironmentEnvironmentVariables` for secrets and config.
+5. Deploy: `CreateDeployment` or `TriggerLatestDeployment`.
+6. Monitor build: `GetBuildLogs` until status is "deployed" or "failed".
+7. If failed, inspect logs and retry: `GetDeploymentLogs`, then `RetriggerDeployment`.
+8. Add a custom domain if needed: `CreateDomain`, then `RefreshDomain` for TLS.
+
+## Guardrails
+
+- Always check for existing projects before creating new ones.
+- Use environment variables for secrets — never hardcode credentials in source.
+- Validate project names: 4-32 chars, alphanumeric with hyphens only.
+- Confirm destructive operations (delete project/deployment) with the user first.
+
+## Output
+
+- Project ID and deployment URL
+- Build status and any errors
+- Environment configuration summary

createos-mcp/skills/manage-environments/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: manage-environments
+description: Create and configure staging, production, and custom environments with variables and resources
+---
+
+# Manage Environments
+
+## Trigger
+
+User wants to set up staging, production, or custom environments, configure environment variables, or adjust resource limits.
+
+## Workflow
+
+1. List current environments: `ListProjectEnvironments` for the target project.
+2. Create a new environment if needed: `CreateProjectEnvironment` with name, branch, and resource allocation.
+3. Configure environment variables: `UpdateProjectEnvironmentEnvironmentVariables` with key-value pairs.
+4. Adjust resources: `UpdateProjectEnvironmentResources` (CPU: 200-500 millicores, Memory: 500-1024 MB, Replicas: 1-3).
+5. Assign a deployment: `AssignDeploymentToProjectEnvironment` to route traffic.
+6. Check logs: `GetProjectEnvironmentLogs` to verify the environment is healthy.
+
+## Guardrails
+
+- Keep production and staging environments separate with distinct variables.
+- Never copy production secrets to staging without user confirmation.
+- Resource limits: CPU min 200m / max 500m, Memory min 500MB / max 1024MB, Replicas min 1 / max 3.
+
+## Output
+
+- Environment ID and configuration summary
+- Resource allocation details
+- Environment variable list (names only, not values)

createos-mcp/skills/security-scan/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: security-scan
+description: Run and review security scans on deployed applications
+---
+
+# Security Scan
+
+## Trigger
+
+User wants to check security, run a vulnerability scan, or review security results for a deployment.
+
+## Workflow
+
+1. Identify the target deployment: `ListDeployments` for the project.
+2. Trigger a scan: `TriggerSecurityScan` on the deployment.
+3. Wait and check results: `GetSecurityScan` to retrieve findings.
+4. Download the full report if needed: `GetSecurityScanDownloadUri`.
+5. If issues found, summarize findings and suggest fixes.
+
+## Guardrails
+
+- Always run scans after new deployments to production.
+- Present findings clearly with severity levels.
+- Do not auto-fix security issues — present recommendations and let the user decide.
+
+## Output
+
+- Scan status and summary of findings
+- Severity breakdown (critical, high, medium, low)
+- Recommended next steps