---
title: Use a Charming app
sidebar:
  hidden: true
---

Help me use the Charming app from my message. Read its current state, make the change I asked for, and verify that the change persists. Do not rebuild the app.

Keep the full app URL. A `?t=...` value is a write token for this app and must stay on requests that need it. Do not show or share the token.

## Connect

If Charming MCP tools are already available, use that connection and skip setup. Read the matching guide with `read_docs({ path: "build-mcp.md" })`. For other docs, call `read_docs({})` for the index or pass the portion after `/docs/` from a documentation URL. Follow `next_offset` with the same path until it is null.

Otherwise, read https://charm.ing/docs/clients.md. Follow the setup path for this client, including the matching build guide, then return here. Do not invent access or claim that you changed the app when you could not reach it.

## Use the app

1. Read the app and its current data.
2. Make only the change I asked for.
3. Read it again to confirm the result persisted.
4. Tell me what changed.

If I ask to change the app itself, not its data, use the build guide you chose above. Propose the smallest code change before you ship it.

If Charming blocks the task or you find a bug, send feedback with `submit_feedback` over MCP or `POST /app/<id>/feedback` over HTTP.

Found a bug or need a feature? [Tell us](/docs/capabilities/feedback) with `submit_feedback` or `POST /app/{id}/feedback`. Your feedback shapes what we build next.