Moving from Buildy to Charming

Buildy is now Charming. Your apps already moved — here is the new URL, the new MCP connector, and how to update an agent that still remembers Buildy.

Buildy is now Charming. If you built an app with Buildy, it did not go anywhere — it already lives at its new Charming address, ready to open.

Your apps already moved

Every app you built at app.buildy.so/<handle>/<app> now lives at:

https://charm.ing/<handle>/<app>

Old buildy.so links still work: opening one in a browser sends you straight to the matching charm.ing page. Nothing to export, copy, or rebuild.

Every client that could connect to Buildy can now connect to Charming — Claude, ChatGPT, Cursor, Codex, Windsurf, Cline, and the rest. See all AI clients for setup steps.

The one exception: the ChatGPT Apps directory listing still shows under the Buildy name while the listing itself moves to Charming branding. The connector works today either way — the directory entry is coming soon.

Update your connector

If you added Buildy as a custom MCP connector, swap it for Charming. For Claude:

Follow Set up Claude to add https://charm.ing/mcp as a new custom connector.
Remove the old Buildy connector from Claude’s connector settings.

Other clients follow the same add-then-remove pattern — see all AI clients for each one’s steps. That’s it — the apps you built are already there under your account.

If your agent remembers Buildy

Memory is not a Claude-only feature — ChatGPT, Claude, and most chat clients can carry facts across conversations. If yours does and still references Buildy, tell it to update with a prompt like:

I replaced the Buildy MCP connector with Charming. Treat any past
conversation or reference to Buildy as Charming going forward.

For coding agents

If your agent has Buildy configured — as an MCP server entry, a plugin, or in its own memory — update it directly instead of asking a human to click through settings. This applies to any coding agent that keeps its own MCP config: Codex, Claude Code, Cursor, Windsurf, Cline, Continue, Zed, Gemini CLI, and the rest.

1. Replace the MCP server entry

Find the config file your agent uses for MCP servers, find the entry pointing at app.buildy.so (or named buildy), and replace its URL with https://charm.ing/mcp. Rename the server key to charming if the client keys config by name. There is no other change to server behavior or tool names.

For example, Codex uses ~/.codex/config.toml:

[mcp_servers.charming]
url = "https://charm.ing/mcp"

Delete any [mcp_servers.buildy] block, or the plugin marketplace entry if Buildy was installed as a plugin — see Set up Codex for the plugin path. Other agents follow the same pattern in their own config file or settings UI; see all AI clients for each client’s setup guide and config location.

2. Scrub stored memory

If the agent keeps its own persistent memory or project notes (AGENTS.md, CLAUDE.md, a memory file, prior session summaries), search it for Buildy or buildy.so and either:

replace each reference with Charming / charm.ing, or

if the references are numerous or historical, add one line instead of editing each occurrence:

Note: "Buildy" in this file refers to Charming (charm.ing). The
product was renamed; treat all such references as Charming.

3. Verify

Ask the agent to list its available tools and confirm the Charming tools appear (create_app, mutate_app, list_apps, and so on) instead of, or in addition to, Buildy’s. Then ask it to list your apps — the same apps you built under Buildy should show up unchanged.