Open source · In production

Deploy from chat

Open source: a plugin for Claude Code and an MCP server for a cloud provider. Servers, database clusters, object storage, domains and DNS, SSH keys and the application release itself - by a tool call from chat, with no manual SSH. The package is published on npm, and the plugin installs from the plugin marketplace.

The pain

Between «the code is ready» and «people are using it» sits manual fiddling: SSH, a server, a web server, a certificate, a DNS record. Every time from scratch and from memory.

Now

The plugin and the MCP server give Claude Code direct access to the cloud: a server, a database, DNS, a certificate and the release itself are done by a command in chat.

What the business gets

The «how do we ship this» question is settled where the code was written - in the same chat.
Infrastructure is created by a tool call, so the steps are neither forgotten nor done from memory.
A readiness check runs before the release, health and logs after it, and a bad release is rolled back by a command.
It is open source and a public package: anyone can plug it in, not only me.

From source to result

A command in chat
An agent for the project’s stack
MCP to the cloud
Server, database, DNS, certificate
Release, logs, rollback

The provider token lives in the environment and never reaches the chat: the tool calls the API itself, and Claude only sees the result of the call.

How it works

The tools cover servers, database clusters, Kubernetes, object storage, domains and DNS, SSH keys, floating addresses, pricing and the account balance: the provider’s API in full, not a slice cut for one scenario.

The agents are split by stack - Node.js and Next.js, Python, PHP, static - and a separate agent checks that the release can go through at all before anything changes on the server.

The MCP server runs through npx and takes its token from the environment, while the plugin installs from the Claude Code plugin marketplace with one command.

Who maintains it now

Me. Open source under the MIT licence, with the package published on npm.

Other cases for this step

Internal system · In production

Management finance loop

A report in half an hour instead of weeks

The pain: Management reporting was assembled by hand over weeks: exports, merging, double-checking.
Now: The report comes together in half an hour, data pulls itself in, and budget variances are visible immediately.

Before → after: weeks → half an hour
Data collection: pulls itself in

The same system pays off across 3 more steps

Internal system · In production

Product portal

An external PLM replaced in days

The pain: Product data lived in someone else’s system: nothing in it could be changed, and any modification meant months of waiting.
Now: An in-house portal replaced the external PLM in a few days of work. The production delivery pipeline was ready on the day of the first commit, so changes reach people the same day.

Timeline
Delivery pipeline: ready on the day of the first commit
Replaced: an external PLM system

The same system pays off across 2 more steps

Open source · In production

Starter application template

From the first commit to a production pipeline - one day

The pain: Between «the first screen is written» and «people can use this» there are usually weeks of setup, and it is assembled again on every project.
Now: One command scaffolds not an empty skeleton but a configured workspace: stack, database, auth with roles, tests, CI and two environments with automatic production rollback.

Timeline: one day to a production pipeline
In the box: database, auth with roles, tests, CI, two environments

two of the three systems - on the day of the first commit

The same system pays off on one more step

GitHub

Own product · In production

Frontend factory

A screen is assembled from ready blocks, not drawn from scratch

The pain: Every new screen started from nothing: its own components, colours and spacing. A block that worked did not travel to the next project - it was nailed to its own theme.
Now: A library of authored sections and template pages on top of stock shadcn components. A block transfers as a file: data arrives through props and the colour comes from the receiving app’s theme.

In the kit
Portability
A project’s foundation

webkoth.com/ui-kit

Type: Open source
Status: In production
How it installs: the plugin from the marketplace, the server through npx
Maintained by: an engineer
Replaced: manual SSH and server setup from memory

TypeScriptNode.jsMCPClaude CodenpmTimeweb Cloud APInginxCertbot

GitHub npm