---
title: "Build MCP"
description: "Build and ship apps from any AI client, without a local setup."
canonical_url: "https://docs.dev.lightdrop.cloud/guides/build-mcp"
---
# Build MCP

> Build and ship apps from any AI client, without a local setup.

wervt build is an MCP server for building apps with your own agent (Claude Code, claude.ai,
ChatGPT, Cursor) when you have no development setup: no Node, pnpm or Docker. Each app gets a
cloud sandbox with its source, a running dev server and its own development database. The agent
edits files and runs commands there, and `deploy` ships the app to `<app>.dev.lightdrop.cloud`.

```bash
claude mcp add --transport http wervt-build https://build.dev.lightdrop.cloud/mcp
```

The first call opens the wervt login: sign in and allow the client. Which MCP is for what is in
[Agents](https://docs.dev.lightdrop.cloud/guides/agents#which-mcp-server).

<note>

build runs with wervt Studio (`deploy/studio` in the wervt repo). It is on wervt.app; a
self-hosted server only has it if it runs that stack too.

</note>

## Who can use it

Everyone the [dashboard](https://docs.dev.lightdrop.cloud/guides/dashboard) lets in (its allow-list, invites and admins). Each
person has up to 3 apps in build at a time (`BUILD_MAX_APPS`), admins any number. Deploys go out as
you: the first deploy of a name claims it, and a name someone else owns is refused.

## How a request goes

"Build a habit tracker and ship it" ends with a working URL:

1. `list-apps` shows your apps in build; `create-app` starts a new one from the wervt template and
returns its preview URL.
2. The agent reads the app's `AGENTS.md` (`read-file`) and follows its rules for routes,
validation, the database, live data and users.
3. It changes the app with `edit-file` and `write-file`. The dev server reloads on every change,
and migrations from `pnpm db:generate` apply on their own.
4. `run` runs commands like `vp check` or `pnpm add <pkg>`; long ones run in the background and
`job-output` reads them.
5. `deploy` builds the app and releases it. It returns the live URL, or the build or start errors
to fix. A new app is private: only you (and admins) can open it.

Access, env vars and making the app public are then up to the [dashboard](https://docs.dev.lightdrop.cloud/guides/dashboard) or the
[Dashboard MCP](https://docs.dev.lightdrop.cloud/guides/dashboard-mcp).

## Tools

<table>
<thead>
  <tr>
    <th>
      Tool
    </th>
    
    <th>
      
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        list-apps
      </code>
    </td>
    
    <td>
      Your apps in build and their state (running, or paused until the next call)
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        create-app
      </code>
    </td>
    
    <td>
      A new app in a sandbox with its dev server running; returns the preview URL
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        preview
      </code>
    </td>
    
    <td>
      The dev server's URL, to look at the app
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        list-files
      </code>
    </td>
    
    <td>
      The app's files, without <code>
        node_modules
      </code>
      
       and build output
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        read-file
      </code>
    </td>
    
    <td>
      Read a file
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        write-file
      </code>
    </td>
    
    <td>
      Create a file or replace its content
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        edit-file
      </code>
    </td>
    
    <td>
      Replace exact text in a file
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        run
      </code>
    </td>
    
    <td>
      Run a command in the app folder; <code>
        background
      </code>
      
       for long ones
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        job-output
      </code>
    </td>
    
    <td>
      Output and exit code of a background command
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        deploy
      </code>
    </td>
    
    <td>
      Build and release at <code>
        <app>.dev.lightdrop.cloud
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        delete-app
      </code>
    </td>
    
    <td>
      Delete the sandbox: source and development database. The deployed app keeps running
    </td>
  </tr>
</tbody>
</table>

## Sandboxes

A sandbox pauses when it isn't used and resumes on the next call. Its source lives only there:
`delete-app` removes it for good, while the deployed app and its production data stay. The
development database is separate from production; deploying doesn't copy data.


## Sitemap

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