Charming

Name: Charming
Author: tambo-labs

作者：tambo-labs版本 1.0.1i★ –i在云端运行

注册名称io.github.tambo-ai/charming

安装

概览

作者提供的说明（英文原文）

Build personal interactive apps with real URLs and persistent storage, using any AI.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 0 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在云端运行
传输方式: Streamable HTTP
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 0 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
注册中心没有列出需要填写的密钥。

你需要

在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude：

打开 Settings → Connectors
点击 Add custom connector
粘贴下面的地址，然后点击 Add
如果要求登录，请登录作者的服务

https://charm.ing/mcp

在终端中运行这条命令

claude mcp add --transport http charming https://charm.ing/mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "charming": {
      "url": "https://charm.ing/mcp"
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "charming": {
      "type": "http",
      "url": "https://charm.ing/mcp"
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

ChatGPT 只能连接互联网上的服务器：

打开网页版 ChatGPT → Settings → Connectors (Apps)
点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
粘贴下面的地址，起个名字，然后保存
如果要求登录，请登录作者的服务

https://charm.ing/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

! 注意
作者与仓库一致
发布者（tambo-ai）不是仓库所有者（tambo-labs）；可能是其他人代为上架的
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
… 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
… 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32673 个服务器的 0%
发布到注册中心的时间比此分类中其他 32673 个服务器的 17% 更新
基础检查结果等于或优于此分类中其他 32673 个服务器的 29%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Charming 安全吗？

它在 1 项适用的基础检查中通过了 0 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.0.1）于4个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Systemdox

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211前天更新

安装

Systemdox

作者：puglieseweb

Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Charming MCP Server

Charming is a hosted MCP server that generates, hosts, and updates interactive web apps. Connect it to any MCP-compatible AI client and ask it to build an app. You get back a live URL in seconds.

Connect

Client	Endpoint
Claude, Claude Code, Cursor, Codex, Gemini CLI, and most MCP clients	`https://charm.ing/mcp`
ChatGPT	`https://charm.ing/mcp/chatgpt` (one-click via the Charming listing in the ChatGPT Apps directory; this paste-string is the Developer Mode fallback)

Most MCP clients can use this remote configuration:

"mcpServers": { "charming": { "url": "https://charm.ing/mcp", "type": "streamableHttp" } } }

The MCP endpoints require a bearer token, and OAuth with Dynamic Client Registration bootstraps one automatically: 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. Auth guide: usecharming.com/auth.md.

For per-client paste-strings and setup steps, see usecharming.com/clients.txt.

Starter Prompt

Once Charming is connected, paste this to start a build session:

Help me figure out what to build. Look at what you know about me and suggest 2-3 apps that fit, or ask me up to 3 short questions to find an idea.

Read https://usecharming.com/start.md then help me create my first app.

Tools

Charming exposes 39 tools. Connected clients discover them automatically via tools/list.

Tool	What it does
`create_app`	Store an agent-authored module (a `manifest` plus `routes`) with optional UI and CSS, and render it inline. Requires a `description`. Give the user the returned token-free `shareUrl`, never the machine-only `url`.
`update_app`	Edit an existing app by replacing its module/UI/styles/description or applying exact-string edits, with optimistic-concurrency versioning.
`get_app`	Render an existing app inline (where the client supports it) and return its callable API operations and metadata.
`get_app_source`	Return the persisted module, UI, and styles for an existing app plus its current version.
`list_apps`	List the caller's apps plus apps shared with them, newest first, with each app's role, description, and capabilities.
`delete_app`	Permanently delete an app you own. Irreversible and confirmation-gated: it fails closed until re-invoked with `confirm: true`. Pass `purge_storage: true` to also wipe stored state.
`upload_asset`	Store a static asset (image, PDF, dataset) so app code stays small; readable back same-origin.
`rename_app`	Change an app's URL slug. The old URL keeps working by redirecting.
`set_remixable`	Mark an app remixable so visitors get their own editable copy.
`unset_remixable`	Stop allowing remixes; existing remixes survive untouched.
`set_starter_prompt`	Set or clear the prompt prefilled in the chat host when a visitor opens a shared app.
`query_app`	Run a read-only backend operation inside an app module.
`mutate_app`	Run a mutating backend operation inside an app module without editing code.
`submit_feedback`	Record agent-authored feedback (bugs, enhancements, crash reports) about an app.
`list_feedback`	List feedback rows for the caller's apps, newest first.
`set_handle`	Change the signed-in user's handle (the first segment of their app URLs).
`share_app`	Invite someone to an app as `collaborator` (default), `end-user` (run and write data, cannot edit source), or `viewer` (read-only). Calling it again with a role changes their role in place.
`unshare_app`	Revoke access for any grantee, whether the invitation is still pending or already accepted.
`list_app_shares`	List active and pending share invites for one of your apps.
`set_public`	Make an app public: anyone with the URL can open it with no login and read AND write its shared data. Warn the user that every anonymous visitor shares one data pool, so anyone with the URL can overwrite or wipe it.
`unset_public`	Make a public app private again; anonymous visitors can no longer open it.
`set_template`	Publish an app as a template so anyone opening its URL gets their own brand-new copy, leaving the original untouched. Pass `listed: true` to also list it in the public directory. Omitting `listed` leaves the current listing state alone. The app must be claimed first.
`unset_template`	Stop treating an app as a template: new visitors can no longer copy it, and any public listing is cleared. Existing copies survive.
`search_templates`	Search the public Charming template directory by keyword. Check here for an existing template before calling `create_app`, or when the user asks what templates exist. Each hit carries a `copyUrl` a visitor can open to mint their own independent copy with no login.
`acknowledge_feedback_responses`	Acknowledge feedback responses after the agent has processed them.
`cancel_app_build`	Use this to cancel an accepted app build before it publishes.
`create_routine`	Use this when the user wants an app op to run on its own, on a timer — no chat needs to be open.
`delete_routine`	Use this to stop and remove a Routine.
`get_app_build`	Use this to inspect an accepted app build without running or publishing it.
`list_feedback_responses`	Fetch unread Charming staff responses to feedback submitted by this authenticated account.
`list_routines`	Use this to see the caller's Routines across their apps.
`read_docs`	Read Charming documentation without web access.
`update_routine`	Use this to change a Routine's `interval`, or enable/disable it.
`create_webhook`	Use this when an external service (Zapier, a payment provider, a partner backend) needs to call one of an app's ops directly.
`delete_webhook`	Use this to remove a Webhook.
`list_webhooks`	Use this to see the Webhooks on every app the caller can edit, with delivery state.
`update_webhook`	Use this to rename a Webhook, enable/disable it, or rotate its secret.
`copy_app`	Use this to make the signed-in user a private copy of an existing app in one call, without reading or re-sending its source.
`resolve_handoff`	Resolve a Charming handoff reference into diagnostic data about a problem in one of the caller's apps.

Use with a coding agent

Working in Codex, Claude Code, Cursor, or another AI coding agent? Install the optional Charming authoring skill from skills.sh with npx skills add tambo-labs/charming-mcp. This installs authoring guidance; it does not connect the MCP server.

It teaches the agent Charming's build contract and workflow. The skill itself is SKILL.md; AGENTS.md has connect and authoring instructions for any AI coding agent. Codex users can instead install the bundled Charming Codex plugin.

Cursor

Cursor reads project rules from .cursor/rules/. Drop .cursor/rules/charming.mdc into your project (or copy its body into a legacy root .cursorrules) and Cursor's agent will reach for Charming (real URL, storage, and inline rendering) whenever you ask for an app you want to keep. The rule points at the served docs; it does not duplicate the contract.

Distribution

This repository is the canonical source for every public Charming integration package. Platform-neutral artifacts are hand-edited; platform adapters are generated from them, so a fact lives in exactly one file.

Kind	Artifact
Platform-neutral (edit these)	`canonical/facts.json`, `SKILL.md`, `AGENTS.md`, `.cursor/rules/charming.mdc`, `charming-icon.png`
Adapter (generated)	`plugins/cursor/charming`, `plugins/claude-code/charming`, `plugins/codex/charming`, `plugins/agent-plugins/charming` (a portable Agent Plugins v1.0.0 package), `gemini-extension.json`, `GEMINI.md`, the three marketplace catalogs

npm ci                                   # install ajv, the schema validator

node scripts/build-packages.mjs # regenerate every adapter node scripts/build-packages.mjs --check # fail on drift (runs in CI)

The adapters are not published yet; publishing each one is tracked separately. See DISTRIBUTION.md for the layout, the drift checks, and how the Charming monorepo proposes changes here.

Documentation

Agent skill: SKILL.md · coding-agent guide: AGENTS.md · Cursor rule: .cursor/rules/charming.mdc
Full authoring guide: usecharming.com/llms-full.txt
Auth and pairing: usecharming.com/auth.md · limits: usecharming.com/pricing.md
OpenAPI spec: charm.ing/.well-known/openapi.json
Docs: usecharming.com/docs

Built with Composio

Charming uses Composio to connect apps with external services such as Gmail, Google Drive, and GitHub. Composio holds each OAuth token and runs each connector call; Charming decides whether a call may run and whose connection serves it.

Publisher

Published by Tambo.