Use AfterLaunch with ChatGPT

Connect

Connect it like this:

1. Open ChatGPT at https://chatgpt.com/, then go to Settings, then Security and login, and turn on Developer mode. It is off by default.
2. Open ChatGPT Plugins at https://chatgpt.com/plugins, press the plus button and create a developer-mode app for AfterLaunch.
3. Paste the server URL as the app's endpoint: https://afterlaunch.io/api/mcp
4. Choose OAuth as the authentication and finish creating the app. There is no field for a static API key, so do not go hunting for one.
5. Sign in with your AfterLaunch account and approve the consent screen, then say afterlaunch in ChatGPT to see your standup.

Developer mode is where custom MCP connectors live, and OpenAI keeps moving this surface, so the exact menu names shift between releases. The connectors section is now called plugins.

No key yet? Read the agents page or hand your agent /llms.txt, and it can run the onboarding flow: it submits your site and email, you approve with one click by email, and nothing runs until you do.

What ChatGPT can do

The 62 tools are the same whichever agent calls them. Once connected, ChatGPT can:

• Read your ranked moves as a compact list, then use get_move for one move’s full material. Read the product run, its automated loops and drafted outputs too. All read-only and free.
• Act on a move: record its confirmed completion, skip it with structured feedback, redraft the body before it goes out, or archive it. Free, on the act scope every self-serve key carries. Shipping stays the founder's decision; reporting it back the moment the work is live is the agent's, and it is what the engine measures the next ranking against.
• Run the engine on demand: refresh an AI Visibility scan, top up your growth moves, or run a single loop. These spend money, so they run on the write scope every key already carries and are metered: charged once per logical event, replayed on a repeat, and capped per tenant per day and per month.
• Set the dials: a loop autonomy rung and its cadence. Both need the config scope and Founder tier, and social channels never accept full autonomy, so publishing stays review-and-post by a human.
• Mint a Founder checkout link when the founder wants to upgrade. The link is always bound to the product run the key owns.
• Write the Growth section into the repository it works in, the same block shown below, so the setup teaches the next session too.

In practice

In a ChatGPT chat with the connector enabled, you ask for a read on your category.

Illustrative. The tool names in brackets are the real read and act tools the agent calls.

Good to know for ChatGPT

• Custom MCP connectors sit behind Developer mode, under Settings then Security and login. It is badged as elevated risk and it is off by default. OpenAI decides which plans carry it; we set ours up on a paid plan, and on a work account the workspace admin decides.
• OpenAI documents OAuth for an authenticated custom connector and offers no field for a static API key. Sign in when prompted rather than looking for a key box. Your AfterLaunch key still drives every other client on this page.
• The connector runs inside a chat, not your codebase, so there is no repository file. The AfterLaunch tools appear in the chat composer once the connector is enabled.
• ChatGPT reflows a tool result into its own prose rather than relaying the screen verbatim, so the answer you read is its summary of the screen rather than the screen itself.

Honest posture

ChatGPT operates the tools from a chat, not from your codebase, so there is no repo file to write. The remote server means nothing runs locally.

The AfterLaunch MCP server is remote and bearer-authenticated. There is no local process to install and nothing to execute on your machine: a config only points the agent at an HTTPS endpoint and attaches your key.

A key you mint yourself, or one an agent obtains through onboarding, carries the read, act and write scopes. Reading your growth moves and shipping, skipping, redrafting or archiving moves work straight away. The metered pulls run on that same write scope, bounded by the product run credits and the per-tenant caps, and the autonomy dials need the config scope and Founder tier.

AfterLaunch drafts. A human approves and posts. It never claims to have posted to a social channel on its own.

Reporting back is part of the loop, not an extra step. When the founder confirms a move is live the agent reads get_move for its current state, then calls ship_move to record that confirmation and its actual public URL when it knows it. Without one, AfterLaunch takes the address the move already holds; a change to a site the founder owns with no address held is recorded as prepared. A merged change goes with its page address as planned_url: AfterLaunch checks the page and marks it shipped once the text is live. Nobody is asked to paste a link. This records completion; it does not publish the work. When they decide against it the agent calls skip_move with the real reason. AfterLaunch measures what happens after a move ships, so an unreported ship is work the record never sees.

Questions

Teach ChatGPT to use it

ChatGPT works from a chat rather than a repository, so there is no instructions file to write and nothing to install. The connector above is the whole setup. If you also work in a terminal or an editor, the guides below add the Growth section to that repository, so both surfaces reach for the same tools.

Or read the Growth section in your browser.

Using a different client?

• Using Claude Code instead? →
• Using Cursor instead? →
• Using Windsurf instead? →

Browse all agent guides, see the agents overview, or run a free growth tool first.