Charming
Charming MCP server — generate and host interactive web apps via MCP
README
<img src="charming-icon.png" alt="Charming" width="80" />
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, Grok, Gemini, Perplexity | https://charm.ing/mcp |
| ChatGPT | https://charm.ing/mcp/chatgpt (or the Charming listing in the ChatGPT Apps directory) |
OAuth with Dynamic Client Registration is automatic — clients that support it show a one-time consent screen.
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.
MCP Tools
Charming exposes 21 tools. Connected clients discover them automatically via tools/list.
| Tool | What it does |
|---|---|
create_app |
Store an agent-authored ES module plus optional UI and CSS, and render it inline. Returns the public app URL. |
update_app |
Edit an existing app by replacing its module/UI/styles 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 calling user's apps, newest first, with descriptions and capabilities. |
delete_app |
Delete an app's module entry. 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 another user to collaborate on an app; they accept the invite to get access. |
unshare_app |
Revoke a collaborator's access to an app. |
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. |
unset_public |
Make a public app private again; anonymous visitors can no longer open it. |
Use with a coding agent
Working in Codex, Claude Code, Cursor, or another AI coding agent? Install the Charming authoring skill from skills.sh:
npx skills add tambo-labs/charming-mcp
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.
Documentation
- Agent skill:
SKILL.md· coding-agent guide:AGENTS.md· Cursor rule:.cursor/rules/charming.mdc - Full authoring guide: usecharming.com/llms-full.txt
- OpenAPI spec: charm.ing/openapi.json
- Docs: usecharming.com/docs
Publisher
Published by Tambo.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.