Connect your AI app to Stardust CMS

Which apps work

Supported, tested with the app itself: Claude (claude.ai and Claude Desktop, and on your phone through either), Claude Code, and ChatGPT.
Should work, allowed but not yet tested with the app itself: VS Code with GitHub Copilot, Cursor, Gemini CLI, and other apps on your computer that sign you in through your browser. If one doesn't, tell your Stardust contact which app it was and what the sign-in page showed.
Any other app is stopped at the sign-in page with “This app can't connect”, and nothing is shared. Tell your Stardust contact which app you use.

Before you start

Your organization must have AI app access turned on. Stardust turns it on per organization. If yours is not on, ask your Stardust contact.
You sign in with your Stardust CMS email and password, the same ones you use for the CMS. Not your Claude or ChatGPT account.
To let the app make changes, tick “Also let this app make changes for me” when you connect it. It also needs your organization to have changes through AI apps turned on, which Stardust does per organization, and your role to allow the change: an owner or admin for the settings, a member for draft posts and for stopping a post. To let it schedule posts too, also tick “Also let it schedule posts to customers”: that needs scheduling through AI apps turned on for the organization, which Stardust also does per organization, and an owner or admin. If the app is already connected, disconnect it on the Connected apps page first, then connect it again: an app you have already approved is let back in without the sign-in page asking anything, so the box never shows. In Claude, see Connect in claude.ai or Claude Desktop. In ChatGPT, delete the connector and add it again instead: see Connect in ChatGPT. On the same page you can stop its scheduling, or make it read-only again.
Claude: any plan can add a custom connector. Free plans can add only one. On Team and Enterprise plans, an Owner adds it once for the whole team, and then each person connects with their own Stardust CMS account.
ChatGPT: on the web, adding your own server needs Developer mode, which depends on your plan. On a workspace plan, an admin may have to allow it. The ChatGPT desktop app offers it without Developer mode.

Your Stardust CMS address

Every app below asks for this address. Copy it exactly.

https://ckqkumyejdaxjbvpfnzm.supabase.co/functions/v1/mcp

Connect in claude.ai or Claude Desktop

Open Customize → Connectors, then Add → Add custom connector. On a Team or Enterprise plan, an Owner does this under Organization settings → Connectors. Everyone else then finds “Stardust CMS” under Customize → Connectors and clicks Connect.
Name it Stardust CMS and paste the address.
Under OAuth client, keep what Claude picks: it detects Register automatically. Use Claude's published identity works too. Don't choose Use your own OAuth client: Stardust does not hand out client IDs.
A Stardust CMS sign-in page opens on this site. Sign in with your Stardust CMS email and password, check that it says Claude (claude.ai) wants to access your account, and click Allow access.
In a chat, click + → Connectors and turn on Stardust CMS. Then check that it works.

On your phone: connect on the web or in Claude Desktop first. The connector is then available in the Claude app for iOS and Android.

To let Claude make changes once it is connected read-only, first disconnect it on Connected apps. Then, on the connector's page in Claude, click Disconnect, then Connect, and tick “Also let this app make changes for me” on the sign-in page. Claude registers as a new app when it connects again, and the tools that change settings appear under Write/delete tools. If they do not, choose Refresh tools list in the connector's ⋮ menu. The same list is where you choose whether Claude asks you before each change.

Connect in Claude Code

claude mcp add --transport http stardust-cms https://ckqkumyejdaxjbvpfnzm.supabase.co/functions/v1/mcp

Then, in Claude Code, run /mcp, choose stardust-cms, and choose Authenticate (or run claude mcp login stardust-cms from your terminal). Your browser opens the Stardust CMS sign-in page. Sign in, check that it says An app on your computer (such as Claude Code) wants access, click Allow access, and go back to Claude Code. Then check that it works.

Connect in ChatGPT

On the web, turn on Developer mode first (Settings → Apps → Advanced settings). Then open Plugins in the sidebar, click +, and choose Create custom MCP server. In the ChatGPT desktop app: Customize → Plugins → Add → Create MCP App, no Developer mode needed.
Name it Stardust CMS. Under Connection, keep Server URL and paste the address. Keep Authentication on OAuth.
ChatGPT warns that a custom MCP server can carry risk. Tick I understand and want to continue, and create it.
A Stardust CMS sign-in page opens on this site. Sign in, check that it says ChatGPT wants to access your account, and click Allow access.
If Stardust CMS is not under Installed yet, open Plugins, go to Personal, and click + next to Stardust CMS to install it.
Start a new chat, type @ and choose Stardust CMS. Then check that it works.

To let ChatGPT make changes once it is connected read-only, delete its Stardust CMS connector in ChatGPT and add it again, ticking “Also let this app make changes for me” on the sign-in page. Connecting again alone is not enough: ChatGPT keeps the tools it saw when the connector was added. Adding it again registers it as a new app, so Connected apps then lists ChatGPT twice. Disconnect the one used longest ago.

When ChatGPT changes a setting, it asks you to confirm first. It may also mark the change “Suspicious Instruction”. AI instructions are instructions for another AI, which is what that check looks for, and the whole text goes with every change, not only your edit. Check that the change is the one you asked for, then allow it. ChatGPT can also stop a change itself, before it reaches Stardust CMS, and asking again can work. It may describe its own check, or your own “Deny”, as Stardust CMS refusing: see If something goes wrong.

Other apps

In an app on your computer, such as VS Code with GitHub Copilot, Cursor or Gemini CLI: add an MCP server with the address (HTTP, not a local command), and sign in through your browser when the app asks. The sign-in page names it An app on your computer (such as Claude Code) or VS Code (GitHub Copilot). These apps should work but are not yet tested one by one; see Which apps work.

Check that it works

Ask these in a new chat, with Stardust CMS turned on. Put your organization's name where it says your organization.

“Which organizations can you see in Stardust CMS?”
You should see your organization's name and your role in it. That shows you are connected.
“Show the five most recent customer conversations in your organization.”
You should see customer names, their latest message and the time. Compare one with the CMS: this shows the app is reading your data.
“How many customer messages did your organization receive last month?”
You should get a number close to the one on your CMS dashboard. Times are in UTC, so a day's edges can differ slightly.

If the app says it can see no organizations, or can't find yours, see If something goes wrong.

What the app can see

Your organizations, and your role in each.
Customer conversations and their messages, including a text search.
Posts: sent, scheduled and drafts, with delivery totals.
The statistics on your CMS dashboard, as totals.
How your organization talks to customers: AI instructions, tone, welcome message, keyword replies and tags.

What it never gets: customer phone numbers, image links or account keys. A number a customer typed into a message stays in that message's text. The organization's own WhatsApp number is the one exception: it appears in the settings.

Times are in UTC, and so are date filters.

Stardust keeps a record of each request for 90 days: who asked, which tool, whether it worked, and the network address it came from. For claude.ai, Claude Desktop and ChatGPT that is the app maker's servers (Anthropic's or OpenAI's), not yours. It never keeps what you asked or what came back.

Disconnecting

Open Connected apps, sign in, and click Disconnect next to the app. It stops working at its next request.

That page also shows when each app was last used, and, for an app on your computer such as Claude Code, the network address it last connected from. An address you don't recognize is a reason to disconnect.

Removing it in your app alone is not enough: Stardust still trusts that app until you disconnect it there.

If something goes wrong

What you see	What to do
Your organization is not listed	AI app access is not turned on for it, or you are no longer an active member. Ask your Stardust contact.
“This app can't connect” on the sign-in page	Stardust CMS does not connect to that app yet. See Which apps work, and tell your Stardust contact which app you use.
“This sign-in isn't for Stardust CMS”	Your app did not ask for Stardust CMS by its address, which older versions of some apps do not. Update the app, add the address above again, and connect again.
“Request not found” or “Already handled” on the sign-in page	Start again from your app. A sign-in request belongs to the first account that opens it, and expires.
“Start from your app”	The sign-in page only works when your app opens it. Start from your app.
ChatGPT on the web has no Create custom MCP server	Turn on Developer mode first (Settings → Apps → Advanced settings). If it is not offered, your plan or your workspace admin does not allow it. The ChatGPT desktop app has Create MCP App under Customize → Plugins → Add.
Claude Code: `Dynamic Client Registration rejected (HTTP 404)`	Run `claude mcp remove stardust-cms`, add it again with the command above, start a new Claude Code session, and authenticate. Avoid “Clear authentication”.
“Too many requests”	Wait the number of seconds your app reports, then try again.
Your app says a change was blocked, or that Stardust CMS refused it or needs more permission	Look for Stardust's own answer. When Stardust CMS refuses a change, it gives its reason. For example: changes or scheduling through AI apps are not turned on for the organization; the app is connected read-only, or not allowed to schedule posts, with a link to Connected apps; your role cannot make that change; or the settings, or the post, changed since the app read them. When something fails on its side, it says “Stardust CMS could not complete this request. Try again later.” If your app shows neither, the block may be its own, or a change you declined: check the app's confirmation and the tool's response before trying again. What the app says in its own words does not show whether the request reached Stardust CMS.