# Claude Code

Give Claude Code the platform as tools, once.

Run this once in a terminal:

```bash
claude mcp add uarpie -- npx -y uarpie mcp --client claude-code
```

Or add it to a project so everyone who opens it gets the tools. Save this as `.mcp.json` in the project folder:

```json
{
  "mcpServers": {
    "uarpie": { "command": "npx", "args": ["-y", "uarpie", "mcp", "--client", "claude-code"] }
  }
}
```

## Then just ask

- "Put this app online with uarpie and give me the link."
- "Is my bookkeeping app up? What has it cost this month?"
- "Something's wrong with the school site, check the logs."
- "Go back to the previous version."
- "Invite maya@example.com to the family app."
- "Clone my family-books app from uarpie and continue where I left off." (see [Another computer](/docs/another-computer))

## What Claude will and won't do on its own

Every tool declares whether it only reads or whether it changes something. Claude Code asks you before it uses one, until you tell it not to ask again for that tool. A sensible split: let it check status and read logs without asking, and keep being asked before it goes back to a version or changes a secret.

## If a deploy fails

Claude receives a structured message: a code, a plain explanation, the fix to apply, and the file to edit. It applies the fix and deploys again. You will usually only hear about it after it worked. The full list is under [Error codes](/docs/errors).