How it works

From a sentence to a live URL.

consostack is a service your AI assistant operates for you over MCP — the open standard that lets AI tools take real actions, not just chat. Connect it once; after that, shipping is a sentence in the chat you already code in.

Step by step

What actually happens.

Connect the endpoint — once

Add a single MCP endpoint to any MCP-capable assistant — Claude, Cursor, and others. There's nothing to install and no key to paste yet; the endpoint is public so your assistant can introduce itself and walk you through the rest. You do this one time, ever.

add mcp → mcp.hosting-01.consostack.eu

Order — your assistant quotes and provisions

Tell it what you're putting online. It calls get_hosting_quote to price the stack, shows you the plan, and on your OK calls order_hosting — which creates your account, your organization, and an API key in one step. You approve; you don't fill in forms. Prefer clicking? The web wizard at /start does the same thing manually.

get_hosting_quote → order_hosting → api key

Create the project — from a repo or a template

Point it at a public git repository, or pick a ready-made starter template and skip the repo entirely. The assistant calls create_project (or deploy_from_template), and if the app needs a database it provisions one and injects a DATABASE_URL automatically.

create_project · deploy_from_template · create_database

Build & go live — usually under a minute

consostack clones the repo, detects the framework with Nixpacks, builds a container, runs it on a compute node, and wires a route through Traefik with an automatic Let's Encrypt certificate. Your app answers over HTTPS on its own *.consostack.eu subdomain.

nixpacks build → run container → ● live over HTTPS

Manage it — in the same conversation

The chat that shipped it keeps running it. Attach a database, set an environment secret, add a custom domain, tail the logs, schedule a cron job, or roll back a bad deploy — each is one more instruction, not a new tool to learn.

add_custom_domain · get_logs · rollback · create_scheduled_task

Under the hood

Real infrastructure, quietly.

You never touch any of this — but it's worth knowing it's real hosting, not a black box.

Build

Nixpacks auto-detect

Your framework is identified straight from the repo — Next.js, SvelteKit, FastAPI, Flask, Express, NestJS, Laravel, Symfony, ASP.NET Core and more. No Dockerfile to write or maintain.

Run

Isolated containers on compute nodes

Each app runs in its own Docker container, placed on the least-loaded compute node. Your organization's data is strictly separated from every other tenant.

Serve

Traefik + automatic HTTPS

Routing is handled by Traefik with Let's Encrypt certificates issued and renewed for you — on both your free subdomain and any custom domain you attach.

The tool surface

What your assistant can actually do.

These are the real MCP tools consostack exposes. Your assistant calls them on your behalf — the same actions are available over the REST API and the web console.

get_hosting_quote order_hosting create_project deploy_from_template get_deployment_status list_deployments rollback create_database list_databases add_custom_domain list_domains list_environment_variables get_logs get_build_logs create_scheduled_task list_templates

Three ways to drive it

However you like to work.

Conversational

MCP

The native path. Your AI assistant runs everything from the chat you already code in — quote, order, deploy, and manage.

Programmatic

REST API

Every action has a plain HTTP endpoint. Script your deploys, wire them into CI, or build your own tooling on top.

Visual

Web console

A dashboard for the moments you'd rather click — inspect projects, read logs, and manage settings by hand.