Charming

io.github.tambo-aiPublished by GitHub account tambo-aiv1.0.1Updated Nov 2, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & StorageDeveloper Tools

Overview

AI-generated overview

Hosted MCP server that lets an assistant generate, host and update personal interactive web apps with real URLs and persistent storage.

What you can do
  • Create, update, copy, rename and delete apps, with inline rendering and versioned source access
  • Run read-only or mutating backend operations inside an app and upload static assets
  • Share apps with collaborators, viewers or end users, make them public, or publish them as templates
  • Search the public template directory and manage feedback on your apps
  • Schedule routines, manage webhooks, and read Charming docs without web access
When to use it
Useful when you want an assistant to turn an idea into a small working web app you can keep, share by URL, and let others use or copy, rather than a throwaway snippet. Also fits when you need scheduled jobs or webhooks attached to such an app.
Requirements
Remote streamable HTTP endpoint at charm.ing; OAuth with dynamic client registration is required for the MCP endpoints, with a one-time consent screen instead of an API key. Anonymous creation without a token is available on the HTTP path only. No local runtime or environment variables.
Before you install
Deleting an app is permanent and can also purge stored state; making an app public lets any anonymous visitor read and write one shared data pool, so anyone with the URL can overwrite or wipe it. Webhooks expose app operations to external services and carry a secret that can be rotated. Charming uses Composio to hold OAuth tokens and run connector calls to services such as Gmail, Google Drive and GitHub, so data passes through third parties.

Installation

In SourceWeft

  1. Open Charming in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.tambo-ai%2Fcharming/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

[Charming]

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

ClientEndpoint
Claude, Claude Code, Cursor, Codex, Gemini CLI, and most MCP clientshttps://charm.ing/mcp
ChatGPThttps://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:

json
{  "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.

ToolWhat it does
create_appStore 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_appEdit an existing app by replacing its module/UI/styles/description or applying exact-string edits, with optimistic-concurrency versioning.
get_appRender an existing app inline (where the client supports it) and return its callable API operations and metadata.
get_app_sourceReturn the persisted module, UI, and styles for an existing app plus its current version.
list_appsList the caller's apps plus apps shared with them, newest first, with each app's role, description, and capabilities.
delete_appPermanently 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_assetStore a static asset (image, PDF, dataset) so app code stays small; readable back same-origin.
rename_appChange an app's URL slug. The old URL keeps working by redirecting.
set_remixableMark an app remixable so visitors get their own editable copy.
unset_remixableStop allowing remixes; existing remixes survive untouched.
set_starter_promptSet or clear the prompt prefilled in the chat host when a visitor opens a shared app.
query_appRun a read-only backend operation inside an app module.
mutate_appRun a mutating backend operation inside an app module without editing code.
submit_feedbackRecord agent-authored feedback (bugs, enhancements, crash reports) about an app.
list_feedbackList feedback rows for the caller's apps, newest first.
set_handleChange the signed-in user's handle (the first segment of their app URLs).
share_appInvite 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_appRevoke access for any grantee, whether the invitation is still pending or already accepted.
list_app_sharesList active and pending share invites for one of your apps.
set_publicMake 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_publicMake a public app private again; anonymous visitors can no longer open it.
set_templatePublish 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_templateStop treating an app as a template: new visitors can no longer copy it, and any public listing is cleared. Existing copies survive.
search_templatesSearch 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_responsesAcknowledge feedback responses after the agent has processed them.
cancel_app_buildUse this to cancel an accepted app build before it publishes.
create_routineUse this when the user wants an app op to run on its own, on a timer — no chat needs to be open.
delete_routineUse this to stop and remove a Routine.
get_app_buildUse this to inspect an accepted app build without running or publishing it.
list_feedback_responsesFetch unread Charming staff responses to feedback submitted by this authenticated account.
list_routinesUse this to see the caller's Routines across their apps.
read_docsRead Charming documentation without web access.
update_routineUse this to change a Routine's interval, or enable/disable it.
create_webhookUse this when an external service (Zapier, a payment provider, a partner backend) needs to call one of an app's ops directly.
delete_webhookUse this to remove a Webhook.
list_webhooksUse this to see the Webhooks on every app the caller can edit, with delivery state.
update_webhookUse this to rename a Webhook, enable/disable it, or rotate its secret.
copy_appUse 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_handoffResolve 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.

KindArtifact
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
bash
npm ci                                   # install ajv, the schema validatornode scripts/build-packages.mjs          # regenerate every adapternode 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

Built with Composio

[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.

Source: README.md at commit 536de3f

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts