Run your creator business from ChatGPT: the KiVio Plugin

ChatGPT's new Plugins & Skills system (the Custom GPT successor, cutover October 2026) connects to hosted MCP servers directly. We ship one at api.kidsaivideo.com/mcp — point your plugin at it, authenticate with a 90-day bearer, and manage your KiVio creator business by chatting with ChatGPT.

Platform shift (October 2026): OpenAI closed new Custom GPT creation on 2026-10-26 and sunsets the whole Custom GPT system on 2026-12-11. The successor is Plugins & Skills, which uses hosted MCP endpoints instead of OpenAPI Actions. Our setup already works with the new system — same bearer, new URL field.

What's included vs the local MCP (Claude Code)

Both surfaces hit the same KiVio backend. The hosted MCP for ChatGPT exposes 12 tools; the local stdio MCP for Claude Code exposes 15 (the extra 3 are file-upload tools that need access to your local disk).

	KiVio MCP (Claude Code, local stdio)	KiVio Plugin (ChatGPT, hosted MCP)
Upload AI video files from your disk	Yes	No — hosted MCPs can't reach your filesystem
Replace bytes on a live video	Yes	No — same reason
Create / list / manage series	Yes	Yes
List + respond to commissions	Yes	Yes
Chat with commissioning parents	Yes	Yes
See earnings	Yes	Yes
Deliver a commission to a video already uploaded	Yes	Yes
Request admin deletion of a live video	Yes	Yes

Pattern we recommend: upload videos via the local MCP in Claude Code, run the business side (commissions, chat, earnings reports) from the ChatGPT Plugin wherever you happen to be.

Setup in 5 minutes

Sign up for a KiVio creator account at kidsaivideo.com/creator (free). Verify your email.
On the Studio dashboard, open the Link external tools panel. Click the ChatGPT Plugin tab.
Click Generate ChatGPT bearer token. Copy the token (shown once — if you lose it, generate a new one).
Open ChatGPT. Click + Create → Create a plugin. Name it "KiVio Creator".
In the plugin's Tools / Connected server section:
- MCP server URL: https://api.kidsaivideo.com/mcp
- Authentication: Bearer token → paste the token from step 3.
Copy the suggested instructions (shown in the Studio panel) into the plugin's Instructions / skills prompt field.
Save. Private is fine; publish to the Plugin Store later if you want public visibility.

Example session

You: What's my KiVio pending-escrow balance and any new commissions? Plugin: *calls kivio.whoami* Available: 4,230 coins ($42.30) Pending escrow: 1,180 coins ($11.80) *calls kivio.list_commissions* You have 1 PROPOSED commission: - Parent #a81e offered 500 coins for a "penguin birthday cartoon for Mia, 7". Received 2 hours ago. You: Counter at 800. Message them asking what Mia's favorite color is. Plugin: *calls kivio.counter_commission(id=…, offerCoins=800)* *calls kivio.reply_in_thread(threadId=…, body="Hi! Love this idea. I countered at 800 coins so I can take the time to make it really special for Mia. One quick thing — what's her favorite color? I'll weave it into the cake and party decorations.")* Done. Contact-info scrubber confirmed clean. You: Create a new series called "Birthday Specials", public commission bucket, 20 planned episodes. Plugin: *calls kivio.create_series(title="Birthday Specials", totalEpisodesPlanned=20, commissionBucket="PUBLIC_COMMISSION")* Created. id a7f3-… ; pricing bands 6 free + 11 mid + 3 final.

Why hosted MCP (not stdio)

The stdio MCP server runs as a local process on your machine. ChatGPT runs in the cloud and can't launch processes on your laptop — so the plugin platform standardized on hosted MCP endpoints: a public URL the client POSTs JSON-RPC to, with bearer auth. We implement the Streamable HTTP transport on our API server at /mcp.

Every call is scoped to the creator the bearer identifies. No per-request keys to manage, no OAuth loopback — just one long-lived token per device, same shape as the npm package's 90-day session.

Security

Token: 90-day creator JWT with a server-side session row (revocable). Rotate anytime by minting a new one and revoking the old session.
Scope: ChatGPT stores the bearer encrypted in its plugin credentials; it never flows through chat.
Chat scrubbing: every kivio.reply_in_thread call runs through our server-side contact-info scrubber. Email, phone, URLs, @handles, and messenger app names are stripped before storage — same code path the web Studio and local MCP use.
Revoke: if you lose a token, hit POST /creator/api/sessions/:sid/revoke with the session id (list them via GET /creator/api/sessions), or email support@kidsaivideo.com with the first 8 characters of the token.

Publishing to the Plugin Store

In the plugin editor, click Share → Plugin Store.
Pick a public name and tagline. Suggested: "KiVio Creator Studio — manage your AI-video creator business from ChatGPT".
Category: Productivity or Business.
Add a note that each end-user supplies their own KiVio creator account + their own bearer token (minted on their own Studio dashboard).

When you publish a plugin, OpenAI's platform shares the MCP URL and tool contract but NEVER your bearer token. Every end-user authenticates with their own.

Create a KiVio creator account → See the MCP guide for file uploads

Published 2026-11-03. Updated for OpenAI's Plugins & Skills cutover.