Skip to content

Using AI assistants with GreenStack

GreenStack now has official AI tooling: a Claude skill that knows how to configure and deploy Umbraco on GreenStack, and a Model Context Protocol (MCP) server that lets an AI assistant act in your UmbPanel portal as you — reading your services, managing DNS, and triggering deploys.

Everything is distributed as free, open plugins in the public UmbHost marketplace (github.com/UmbHost/claude-plugins), and the MCP servers are listed in the official MCP Registry.

  • Set up a new site, or fix an existing one — the greenstack-umbraco-setup skill configures an Umbraco 13 or 17 project for GreenStack correctly the first time: forwarded headers, the HTTPS/health-check settings, Data Protection keys, the Dockerfile and CI pipeline (for any Git provider and any Docker registry), and the SignalR backplane for a load-balanced backoffice.
  • Manage your hosting by chat — with the UmbPanel MCP connected, the assistant can list your services, read a service’s status and deploy webhook, set the container registry and image, scale replicas, trigger deploys, and manage your Cloudflare DNS — all scoped to your account.
  • An AI assistant that supports plugins/MCP — Claude Code is the fully supported option today.
  • A GreenStack service in UmbPanel.
  • Your usual UmbPanel member login (you sign in through the normal portal login; the assistant only ever gets the access you already have).

Add the marketplace once, then install the plugins:

Terminal window
claude plugin marketplace add UmbHost/claude-plugins
claude plugin install greenstack-umbraco@umbhost # the setup skill
claude plugin install umbpanel-mcp@umbhost # manage your hosting (optional)

The first time the assistant uses a management tool, it opens your browser to the UmbPanel login. Sign in as you normally would and approve the request — the assistant is then connected as you.

You don’t need the MCP plugin to benefit from the skill. On its own, the skill does all the app-side configuration and walks you through the portal steps by hand. Add umbpanel-mcp when you want the assistant to carry out the UmbPanel steps for you.

  • “Set this Umbraco 17 project up for GreenStack and get it deploying from GitHub.”
  • “My backoffice says ‘HTTPS is required’ on the preview URL — fix it.”
  • “We’re scaling to two replicas — what do I need for the load-balanced backoffice?”
  • “Add an A record for blog.mysite.com to my zone.” (the assistant shows a preview and asks before making any change)
  • “Deploy the latest image and tell me when the site is healthy.”

Search this knowledgebase from your assistant

Section titled “Search this knowledgebase from your assistant”

This knowledgebase also has its own MCP server, so your assistant can search and read these articles directly instead of guessing:

Terminal window
claude mcp add --transport http umbhost-kb https://kb.umbhost.net/mcp

It provides search_docs, get_doc and list_docs tools and needs no login. Assistants that don’t support MCP can read llms.txt instead, or llms-full.txt for every article in a single file.

  • The setup skill works in any assistant that reads the ~/.agents/skills/ folder (including OpenAI Codex and GitHub Copilot CLI) — copy the greenstack-umbraco-setup folder from the marketplace repo into ~/.agents/skills/. Full steps are in the plugin’s README.
  • The UmbPanel MCP server is listed in the MCP Registry, so it’s discoverable in VS Code / GitHub Copilot and Codex. Connecting from those uses the public umbraco-member client; if you’d like help wiring it up, contact support.
  • ChatGPT’s app connectors aren’t supported yet — use Codex (OpenAI’s coding assistant) for agent-driven GreenStack work.
  • The assistant acts as your member account and can only see and change your own services and DNS — the same things you can do in the portal. There is no admin or back-office access.
  • Destructive, billing and provisioning actions are confirmed first — the assistant shows you a preview of exactly what will change and only proceeds when you say yes.
  • Sign-in uses standard OAuth (with PKCE); you can review and revoke connected sessions from your UmbPanel account at any time.
  • The login page didn’t appear / the connection says it isn’t authorised — trigger a tool again to restart the sign-in, and make sure you complete the login in the browser.
  • The assistant suggests changing platform settings (connection strings, MainDomLock, the application URL) — it shouldn’t; GreenStack injects those for you. If in doubt, don’t override them.
  • Stuck? Contact UmbHost support and we’ll help.