← ClaudeAtlas

charminglisted

Create, update, inspect, or troubleshoot Charming-hosted interactive web apps via the Charming MCP server, or connect an AI client (Claude, Cursor, Codex, Gemini CLI, ChatGPT) to Charming.
tambo-labs/charming-mcp · ★ 8 · AI & Automation · score 75
Install: claude install-skill tambo-labs/charming-mcp
<!-- Generated by scripts/build-packages.mjs from canonical/. Do not edit. --> # Charming ## Overview Use this skill when the user asks to create an app with Charming, edit an existing Charming app, connect the Charming MCP server, or inspect Charming-generated app source. Charming is a hosted service that generates, hosts, and updates small interactive web apps. Each app gets a real URL, persistent storage, and inline rendering inside MCP Apps-capable chat clients. It has two authoring paths: - **MCP tools** (preferred): use this path whenever Charming tools such as `create_app`, `update_app`, `list_apps`, or `get_app` are available to you. - **HTTP API** (fallback): use only when Charming MCP tools are not available and you have outbound HTTP access. ## Connect Charming is a remote server; there is nothing to clone, build, or run locally. Add the endpoint to your client's MCP settings: | Client | Endpoint | |--------|----------| | Claude, Claude Code, Cursor, Codex, Gemini CLI, and most MCP clients | `https://charm.ing/mcp` | | ChatGPT | the Charming listing in the ChatGPT Apps directory is one click; `https://charm.ing/mcp/chatgpt` is the Developer Mode fallback | Charming's MCP endpoints always require a bearer token. OAuth with Dynamic Client Registration bootstraps one automatically on first connect: clients that support it show a one-time consent screen, with no API key to paste. Anonymous creation with no token is available on the HTTP path only (`POST https: