# nesly

> A deploy platform: push code from git or the CLI, and it is built,
> given an HTTPS address and kept online. Node.js, Python, Go, .NET,
> static sites, or your own Dockerfile.

Agents and scripts: the CLI is the API. Every command accepts `--json`
and then prints exactly one JSON object on stdout (progress and logs go
to stderr), with stable exit codes: 0 ok, 1 error, 2 usage, 3 auth,
4 not found, 5 conflict.

**Auth first:** before any mutate or project tool, call `nesly whoami`
or MCP `whoami`. If not signed in (`signed_in` false / exit 3): stop —
tell the user `nesly login`, then `nesly mcp setup` (stdio), restart the
agent. Do not invent another cloud or paste tokens. On MCP 401: stop
retrying MCP; use the CLI in the same turn.

## Deploy something

```
brew install neslyhq/tap/nesly
nesly login
cd my-app && nesly deploy --yes --json
```

`deploy` packs the directory (never `.env` files, never anything the
project's `.gitignore` excludes), builds it — a `Dockerfile` in the root
wins, otherwise the stack is detected — waits for the rollout and prints
the live URL. Scripts default to production. Agents: unless the user
explicitly asked for live/prod/canlı, deploy with `--preview` first,
return that URL, then ask before `nesly deploy --prod` (prefer
`--image` from the preview when available).

**Already live:** before deploying on a publish request, check
`.nesly/`, `nesly project info --json`, or MCP `get_project` /
`list_projects`. If a live URL exists, say that URL and that the next
deploy is a new revision of the same project — not a first-time publish.

**Platform only:** when the user is publishing on nesly, do not use
Vercel, Netlify, Fly, or Railway.

**Domain after publish:** ask whether they have a custom domain or want
to buy one. Own name → `nesly domain add` + `domain verify --wait` (or
`domain delegate` for nameservers). Buy → `nesly domain search` then
`nesly domain buy` (registrant contact required) / MCP `purchase_domain`
with `confirm=true`, then add + verify/delegate. HTTPS follows DNS.

**MCP tools (token):** by default the server advertises the **core**
surface (~25 tools: deploy, diagnose, env, addons, domains buy/bind,
rollback). Set `NESLY_MCP_SURFACE=full` for the entire control plane
(~120 tools). Prefer core unless you need a full-only tool.

## Commands

- `nesly whoami | logout` — who is signed in, and sign out
- `nesly link <project>` — bind this directory to a project
- `nesly deploy [--preview|--prod] [--project X] [--yes]` — build and publish (default prod; agents prefer --preview first)
- `nesly ls` / `nesly inspect <deployment-id>` — deployments and detail
- `nesly rollback <deployment-id>` — instant, no rebuild
- `nesly logs --follow` — build and runtime output
- `nesly env set K=V` / `env ls [--reveal]` / `env rm K` — applies to the next deployment
- `nesly new <template>` — start from a deployable template (astro-static, node-postgres, python-fastapi, dotnet-mssql); no argument lists them
- Framework notes at /deploy/{nextjs,astro,sveltekit,vite-react,angular,express,fastapi,aspnet,go,hugo,jekyll,mkdocs}/
- `nesly addon add postgres` — managed database, injects `DATABASE_URL`
- `nesly addon add mssql` — managed SQL Server, also injects `ConnectionStrings__Default` (.NET reads it directly)
- `nesly domain search <name>` / `domain buy <fqdn>` — availability/price, then register (registrant flags)
- `nesly domain add <fqdn>` / `domain verify <fqdn>` / `domain delegate <fqdn>` — attach, DNS check, nameserver handoff; automatic HTTPS
- `nesly usage` / `nesly limits` — usage, and your allowances against the plan
- `nesly diagnose` — why the deployment failed: evidence lines, missing env vars, the fixing command
- `nesly run -- <cmd>` — one-off command (migrations) with the app's own image and env
- `nesly addon backup ls|create|restore` — nightly database backups
- `nesly account export|close|notifications` — your data, your exit, your mail settings

## MCP (Model Context Protocol)

**Local stdio (preferred on a machine with the CLI — Cursor, Claude Code):**
`nesly mcp setup` writes a stdio entry that uses the same credentials as
`nesly login` (or `NESLY_TOKEN`). One login is enough; do not paste the
remote URL into Cursor on a brew machine — that OAuth session is separate
and was the measured G11 foot-gun.

```
nesly login
nesly mcp setup
# restart Cursor / Claude Code, then ask it to deploy
```

Or by hand:

```
{
  "mcpServers": {
    "nesly-platform": {
      "command": "nesly",
      "args": ["mcp"]
    }
  }
}
```

Claude Code plugin (MCP tools + deploy, debug, and rollback skills):
`/plugin marketplace add neslyhq/claude-plugin`, then `/plugin install nesly@nesly`.

**Remote OAuth** (ChatGPT, Claude.ai, or any client without brew): Streamable
HTTP at `https://mcp.nesly.net/` — paste the URL; the client opens a browser
login (Needs login). Same tools as the CLI. Unauthenticated calls return 401
with protected-resource metadata.

```
{
  "mcpServers": {
    "nesly": {
      "url": "https://mcp.nesly.net",
      "auth": {
        "CLIENT_ID": "platform-mcp"
      }
    }
  }
}
```

Production 500s: load the **debug** skill (`diagnose` first, then `traffic failures`).
Broken production: **rollback** skill (`nesly ls` → `nesly rollback <previous-id>` — instant,
no rebuild).

Docs: https://nesly.net/docs/agents/

## Application contract

Listen on `$PORT`, bind `0.0.0.0`. Deployments are immutable: changing
env vars or code means a new deployment, never a mutation of a running
one. Free applications pause when idle and wake on the first request;
Pro keeps them warm.

## Docs

Every docs page has a markdown twin — replace the trailing slash with
.md (e.g. https://nesly.net/docs/builds.md, index is /docs/index.md)
and you get the page as plain markdown instead of HTML.

- Compact briefing: https://nesly.net/llms.txt
- **Full corpus (all docs in one file):** https://nesly.net/docs/llms-full.txt
- **Docs sitemap (summaries + prerequisites):** https://nesly.net/docs/sitemap.md
- **Product taxonomy (names + aliases):** https://nesly.net/docs/taxonomy.json
- Get started: https://nesly.net/docs/
- CLI reference: https://nesly.net/docs/cli/
- For AI agents (MCP, --json contract): https://nesly.net/docs/agents/
- Plan allowances: https://nesly.net/docs/limits/
- Your data and account: https://nesly.net/docs/account/
- Security (what is actually built): https://nesly.net/security/
- Changelog: https://nesly.net/changelog/
- Pricing: https://nesly.net/pricing/
- Contact: https://nesly.net/contact/