← Plugin catalog
Developer Tools

Charming

Tambo v1.2.1

Secure cloud for AI-built apps

Create a free account to save this plugin.

From the developer

Declared limitations

  • Do not trigger for general coding help that does not ask to create or manage a Charming app.
  • Do not trigger for unrelated calendar or scheduling requests.
  • Do not trigger for requests to publish content to third-party services.

Not specified in the available declarations: capabilities, pricing & account requirements.

Onboarding example

Help me build a personal app that feels handcrafted, like a real object.
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 18, 2026. Package observed Nov 17, 2026.

View package source →

Description

From the marketplace listing

Charming is a secure cloud for apps you build with AI. Ask your assistant to build an app with Charming. Charming gives your app a link you can open anywhere and use to invite people to use it with you. They can use the app from their own AI assistant or their browser.

Language: English · Automatically detected from descriptions.

Matches for “CD”

Exact text from the indicated source. A mention alone does not establish support for your task.

Package name

app-6a56c533cd7c8191b9a16cb7973a65e6

What changed

· 4 observations

Capabilities & instructions

Skill instructions: added “Explain Charming first If the user is new to Charming or asks how it works, offer: "Want me to make a short video explaining how Charming works, tailored to...”.

View comparison →
Positioning & listing

App ids updated; open the comparison for details. App-6a56c533cd7c8191b9a16cb7973a65e6 updated; open the comparison for details. Charming updated; open the comparison for details. Full description changed from “Charming is a hosted runtime for personal web apps that users and their agents can share. An agent creates...

View comparison →
Positioning & listing

App ids updated; open the comparison for details. App-6a56c533cd7c8191b9a16cb7973a65e6 updated; open the comparison for details. Charming updated; open the comparison for details. Full description changed from “Charming is a hosted runtime for personal web apps that users and their agents can share. An agent creates...

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

Similar plugins

Similar plugins could not be prepared right now. Please try again in a moment.

Browse plugins →

Files & skills

File archives

Plugin package6 files · 20.8 KBBrowse files →
Skill instructions
build-a-charming-app6.06 KB

View saved version →

---
name: build-a-charming-app
description: Create, host, and iterate on a personal interactive web app with Charming — a real URL, persistent storage, and an MCP or HTTP API — from any agent.
---

# Build a Charming app

Charming turns a natural-language description into a hosted web app with a real URL and a database. Use it from any MCP-capable client or over plain HTTP; the HTTP path builds a first app with no signup.

## When to use this

Reach for Charming when the user wants a small app that outlives the chat: a tracker, a dashboard, a form, a personal tool. Charming gives it a persistent URL, storage, and an API your agent can keep using and updating across sessions.

## Two surfaces

- **MCP** (Claude, Cursor, Claude Code, and more): add `https://charm.ing/mcp` as an MCP server, then call the tools. ChatGPT uses its own endpoint, `https://charm.ing/mcp/chatgpt`, which carries the inline-widget metadata. Per-client setup strings: https://charm.ing/docs/clients.txt
- **HTTP**: `POST https://charm.ing/app` with the app source. Full contract: https://charm.ing/.well-known/openapi.json

## The app contract

An app is one ES module with two named exports, `manifest` and `routes`. Every new app uses this shape on both surfaces.

```js
export const manifest = {
  $schema: 'https://charm.ing/schema/app-manifest/2026-07-31.json',
  id: 'counter',
  meta: { name: 'Counter', icon: { emoji: '➕', bg: '#e8611c' } },
  capabilities: { imports: ['charming:storage/kv@1.0'] },
};

export const routes = [
  {
    op: 'increment',
    method: 'POST',
    path: '/api/increment',
    title: 'Increment counter',
    description: 'Add one and return the new value.',
    inputSchema: { type: 'object', properties: {}, additionalProperties: false },
    outputSchema: { type: 'object', properties: { count: { type: 'integer' } } },
    annotations: { readOnlyHint: false },
    public: true,
    examples: [{ input: {}, output: { count: 1 } }],
    handler: async (input, { env, ctx, request }) => {
      const count = ((await env.storage.get('count')) ?? 0) + 1;
      await env.storage.put('count', count);
      return { count };
    },
  },
];
```

`manifest` is parsed statically, so keep it a plain literal with no computed values. `capabilities` accepts `imports` and nothing else: `charming:storage/kv@1.0` gives `env.storage`, `charming:storage/blob@1.0` gives `env.assets`, `charming:logging/emit@1.0` gives `env.log`, `charming:network/fetch@1.0` gives plain outbound `fetch` and `charming:secrets/fetch@1.0` gives the sealed `env.fetch` that substitutes `{{secret:NAME}}` into headers. Both are claimed-apps-only, and `permissions.server.fetch` gates every backend egress path, plain and sealed alike: list each allowed origin there, because an import without origins leaves egress blocked and origins without the import do too. Remote image origins go in `permissions.browser["img-src"]`. Each origin is a concrete `https://` host. `$schema` may be omitted on create; Charming inserts the dated URL.

`routes` is an array, never an object keyed by operation name. Only `op` and `handler` are required; the rest of the metadata is what Charming reads to route `query_app` versus `mutate_app`, to answer `get_app`, and to build the app's OpenAPI document, so declare a read with `annotations: { readOnlyHint: true }`. A default export is optional: Charming serves the unmatched-path 404 itself.

## Build flow (MCP)

1. `search_templates` — look for an existing template before building from scratch. A hit's `copyUrl` starts browser navigation where the user chooses to copy and signs in before Charming creates the owned App. It is not an MCP or REST write. After creation, use `list_apps` or `GET /app` to find the copy and `get_app_source` or `GET /app/:id/source` to read it.
2. `create_app` — author a new app from a name plus source (an ES module for logic + UI/styles). The response carries the live URL.
3. `update_app` — iterate on the source.
4. `query_app` / `mutat

Preview of the first 4,000 characters. Read full instructions →

Release notes

Updates the Charming app-building skill and marks set_template and cancel_app_build as destructive.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
Tambo
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Package observed Nov 17, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 18, 2026 · 00:00 UTC
Latest observed change
Oct 8, 2026 · 06:08 UTC
Collection status
Collected

plugin_asdk_app_6a56c533cd7c8191b9a16cb7973a65e6

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.