Built for you. Readable by agents.

The library and the design library are open to agents today, through an MCP endpoint your agent connects to by signing in: it pins components, draws and edits designs, and sends both to a Terminal site. The goal is one integrated development experience, with hosting it can ship to and you directing, from brief to live site, without leaving the workspace.

See it working today Follow the roadmap

Stacklumen Base / Library / Templates Search or jump to… ⌘K DR

N Overview Library Design Tools Agency Feedback DR

Northwind Library of components. Components Templates Marketplace Import

Whole sites, not single components.

12 complete Astro sites — pages, components, styles — written fully static so they import losslessly into Terminal. Download the folder, pick it in the designer’s Astro panel, and every section arrives styled.

Runs standalone npm install && npm run dev inside the unzipped folder. No client JavaScript, no CSS framework, no dynamic routes.

Meridian SaaS product landing

Atelier Studio portfolio

Cadence Web design agency

Ridgeline Management consultancy

Solace Health Healthcare provider

Foundry Consultancy, dark

Kestrel Trade services

Tidewell Personal finance app

Oxbow Developer platform, dark

Halden Boutique hotel and restaurant

Parallax Design and tech conference

Common Ground Climate charity

Three commitments, one experience.

The first two are live today. Deployment as a connection is on the roadmap.

Machine-readable by design

Everything in the workspace ships as data an agent can consume, not just a page a human can read. Components are searched by name and category over MCP; templates are fully static Astro projects an agent can fetch whole; a design is its document in millimetres, every shape addressable by id, with its artwork as SVG.
Agents in the build loop

Live today: one MCP endpoint your AI agent connects to by signing in, with 26 tools. It searches the library and pins components to a Terminal site. It creates designs and edits them with edit_design, a batch of the designer's own drawing operations saved as one revision, and sends them to a site's assets with push_design, which only proposes until it is told to execute. Scoped, revocable tokens cover agents that cannot sign in. No AI key: your agent runs on your own plan.
Deployment is a connection

Shipping should not be a context switch. In Stacklumen Terminal, a Vercel MCP and native Vercel and Hostinger connections put provisioning, deploys and domains inside the same workspace the site was designed in.

Agents in the build loop. On a token you scope.

Your agent connects to one MCP endpoint by signing in, with 26 tools. Scoped, revocable tokens cover agents that cannot sign in. No AI key: your agent runs on your own plan.

Your agent connects by signing in, on your own plan
Components found and pinned to a site
Designs drawn and pushed with the designer's own operations

Connect an agent

Stacklumen Base / Overview Search or jump to… ⌘K DR

N Overview Library Design Tools Agency Feedback DR

Northwind Overview of everything. Overview

list_designs components:read

The workspace's design library, most recently touched first: id, name, client, trim size in mm, status and when it changed. No artwork; fetch one with get_design.

get_design components:read

One design: its full document (artboard in mm, trim and bleed, every shape) and, unless svg is false, its artwork as SVG. Shape ids here are what edit_design operations name.

list_design_operations components:read

The designer's drawing operations — add_shape, update_shape, set_paint, set_type, arrange and the rest — with each one's input schema. edit_design applies a batch of them.

list_presets components:read

The artboard sizes (business cards, letterhead, logos, social, A-sizes) and the templates a new design can start from.

create_design components:write

Start a new design on a preset artboard (blank) or from a template, save it to the library, and return its document. Draw on it with edit_design.

edit_design components:write

Apply a batch of the designer's operations to a design and save it as one revision — the same edits the designer makes, in the same order. Operations: add_shape, update_shape, set_paint, set_effects, group_shapes, arrange_shapes, combine_shapes, path_command, transform_shapes, set_type, delete_shape, reorder_shape, set_artboard, set_document (schemas from list_design_operations). The batch stops at the first operation that fails, and nothing is saved then. An open designer tab picks the change up when it next loads the design.

push_design components:write

Send a design's artwork to a Terminal site's assets. propose (the default) records what would happen and changes nothing; execute writes it.

list_pushes components:read

The push log — what was sent where, proposed or executed, and how it went — newest first.

list_assets components:read

The workspace's uploaded assets — images and SVGs the designer can place — with their URLs.

8 of these tools change your workspace and need a write scope; the rest only read. deploy:write and dns:write can already be granted, but no tool uses them yet, so a token created today keeps working when those tools arrive.

An agent draws. Every batch, one revision.

edit_design applies a batch of the designer's own drawing operations and saves it as one revision, in the same History as your own snapshots. push_design sends the artwork to a site's assets, and only proposes until it is told to execute.

14 operations, the same edits the designer makes, in the same order
All or nothing: the batch stops at the first operation that fails, and nothing is saved then
Reversible: restoring a revision makes what was on the canvas a snapshot of its own

The design system

edit_design

set_paint Mark

update_shape Northwind

update_shape Brand and print

History

An agent’s edit_design call saved as one revision: the designer’s own operations, run on the designer’s own template, with the note edit_design writes when the agent gives none. The drawing is the designer’s History sheet for a business card. The newest moment is an agent’s revision, marked with a sparkle; under it are snapshots. Picking a moment shows that version of the card, its shape count and size, and a Restore this version button. The batch is set_paint on Mark, update_shape on Northwind, update_shape on Brand and print. Before it, the card reads Northwind, Brand and print, with a blue mark; after it, Northwind Ltd, Brand, print and web, with a black mark.

The goals, plainly.

Where agentic building is going. Each step lands on the roadmap first and in the changelog when it ships.

Every surface machine-readable

If a human can browse it, an agent can consume it — components, templates, tokens and docs all exist as structured routes, not screenshots.
Lossless round-trips

Code to canvas and back without degradation. Templates are written to a static contract the designer imports exactly, so what ships is what was designed.
Brief to deployed site, in one place

An agent should be able to take a brief, compose from the library, draw the brand assets, assemble pages in Terminal's designer and put the result on a domain — without leaving the suite.
Hosting as a connection, not a destination

Vercel and Hostinger as first-class connections: deploys, previews and domains readable and drivable from the workspace, by you or by an agent.
One shared memory

Components, templates and designs live in one workspace, so a component learned once is known everywhere — by every surface, every product and every agent in the suite.

What an agent can reach today.

Components as data: 186
Templates, importable: 12
MCP tools live: 26
Designer operations: 14

Watch it happen. On the roadmap first.

Every step above lands on the roadmap first and in the changelog when it ships.

Open the roadmap Read the changelog

Build

Follow along

Company

The platform

The resources.

Built for you. Readable by agents.

Three commitments, one experience.

Machine-readable by design

Agents in the build loop

Deployment is a connection

Agents in the build loop. On a token you scope.

An agent draws. Every batch, one revision.

The goals, plainly.

Every surface machine-readable

Lossless round-trips

Brief to deployed site, in one place

Hosting as a connection, not a destination

One shared memory

What an agent can reach today.

Watch it happen. On the roadmap first.