AI clients
Find your AI client and follow its setup guide.
Choose your AI client
Charming is an MCP server. Chat agents with custom MCP connectors usually need one URL:
https://charm.ing/mcpChoose your client below, add Charming, and approve access.
Once connected, your agent can also read Charming’s public docs through read_docs, without a browser or another connector. read_docs({}) returns the docs index; a known page can be read directly, such as read_docs({ path: "build-mcp.md" }). See Read docs through MCP.
MCP is not the only path. Any agent that can make HTTP requests can build the same apps through Charming’s HTTP API, with no MCP server to add (Build over the HTTP API). Each client page below documents both, so pick whichever your agent can do.
Apps open inside the conversation
- ChatGPT
- Claude, including claude.ai, Claude Desktop, and the Claude Code desktop app
- Microsoft 365 Copilot
- Codex app
- Goose
Apps open in the browser
- Cursor
- Codex CLI
- Claude Code CLI
- Perplexity
- Cline
- Windsurf
- Continue
- Zed
- Notion Custom Agents
- n8n
- Amazon Bedrock AgentCore
- Gemini CLI
- Grok
These clients still build and update the same Charming app. They return its browser URL instead of drawing it inside the conversation.
Copy this prompt for your agent
Connect Charming to this agent and help me build my first app. Read
https://charm.ing/docs/clients.md first.
Choose the setup path documented for this client, MCP or the HTTP
API, whichever you can do. Tell me the exact step I must take, wait
for me to finish it, then use the matching build guide.An MCP client with a browser gets its token by running an OAuth sign-in when it connects. Any other agent pairs to work in your account: it shows you a short code, you approve it at charm.ing/pair while signed in, and it holds an account token from then on. Creating an anonymous app needs no token at all. See Connect to any AI agent for token scope and API access.