---
title: "Agents"
description: "How coding agents learn to write wervt apps."
canonical_url: "https://docs.dev.lightdrop.cloud/guides/agents"
---
# Agents

> How coding agents learn to write wervt apps.

wervt is built for apps written by agents. They get the same information several ways.

## The `wervt` skill: build and ship from anywhere

Install it once per machine, and an agent can take "build a habit tracker and ship it on wervt" from an
empty folder to a working URL: check the login, scaffold with `create-wervt`, build, deploy, set
access and env, check the logs, and optionally set up a GitHub repo that deploys on push.

```bash
vpx @wervt/cli skill install    # ~/.claude/skills/wervt; --project for this repo only (or npx)
```

Run it again after CLI updates to get the newest version. The agent never handles tokens: if the
machine isn't logged in, it asks you to run `wervt login`, and deploy tokens go straight from
`wervt tokens` into `gh secret set`.

After a deploy, the agent checks private apps itself: `wervt token <app>` mints a short-lived
access token for your CLI account on that app, for curl or (with `--cookie`) a headless browser.
See [Testing a private app](https://docs.dev.lightdrop.cloud/guides/private-apps#testing-a-private-app).

## Which MCP server?

wervt has three MCP servers, all signed in through the wervt login as you:

<table>
<thead>
  <tr>
    <th>
      
    </th>
    
    <th>
      For
    </th>
    
    <th>
      Connect
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <a href="https://docs.dev.lightdrop.cloud/guides/mcp">
        App MCP
      </a>
    </td>
    
    <td>
      Using one app through its own tools (<code>
        server/tools/
      </code>
      
      ), as its user
    </td>
    
    <td>
      <code>
        https://<app>.dev.lightdrop.cloud/mcp
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="https://docs.dev.lightdrop.cloud/guides/build-mcp">
        Build MCP
      </a>
    </td>
    
    <td>
      Building and deploying apps in a cloud sandbox, without a local setup
    </td>
    
    <td>
      <code>
        https://build.dev.lightdrop.cloud/mcp
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="https://docs.dev.lightdrop.cloud/guides/dashboard-mcp">
        Dashboard MCP
      </a>
    </td>
    
    <td>
      Managing deployed apps without the CLI: releases, access, env, logs, tokens
    </td>
    
    <td>
      <code>
        https://dashboard.dev.lightdrop.cloud/mcp
      </code>
    </td>
  </tr>
</tbody>
</table>

Add one with `claude mcp add --transport http <name> <URL>` (or your client's equivalent).
With a local setup and a signed-in CLI, agents need none of them: the skill above uses the CLI. The
docs have an MCP server as well, for searching them (see below).

## `AGENTS.md` in every app

The template ships an `AGENTS.md` (and a `CLAUDE.md` that includes it) covering the APIs to use,
migrations, live data and what doesn't work in an isolate. Agents that read repo instructions pick
it up automatically. Skills for UI (`nuxt-ui`, `nuxt-ui-mobile`) and logs (`review-logging-patterns`,
`wervt-logs`) ship in `.claude/skills/`.

## Docs skill

These docs also publish `wervt-apps`, a reference skill for writing app code (the same rules as
`AGENTS.md`), following the
[Agent Skills Discovery RFC](https://github.com/cloudflare/agent-skills-discovery-rfc):

```bash
npx skills add https://docs.dev.lightdrop.cloud
```

## MCP server and `llms.txt`

The docs site runs an MCP server at `https://docs.dev.lightdrop.cloud/mcp`, so agents can search the docs while
they work, and serves [`/llms.txt`](https://docs.dev.lightdrop.cloud/llms.txt) and `/llms-full.txt`.

## Rules worth repeating

- Use `nuxt/server` and the `@wervt/nuxt/server` helpers, not `h3` directly.
- Validate every input with valibot.
- Change the schema, then `pnpm db:generate`. Never edit migrations.
- Keep state in Postgres: isolates stop when idle and have no persistent filesystem.
- Run `pnpm exec vp check --fix` before finishing.


## Sitemap

See the full [sitemap](https://docs.dev.lightdrop.cloud/sitemap.md) for all pages.
