Use AfterLaunch with Gemini CLI

Connect

Add this to your ~/.gemini/settings.json:

{
  "mcpServers": {
    "afterlaunch": {
      "httpUrl": "https://afterlaunch.io/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_AFTERLAUNCH_API_KEY"
      }
    }
  }
}

Restart the CLI after editing the file, then run /mcp inside it to confirm the AfterLaunch tools loaded.

Not verified. One documentation check on 28 August 2026 matched this block, but nobody here has driven Gemini CLI against the AfterLaunch server, so treat it as the shape rather than the proof. Two of the four shapes that were re-checked on 15 August had moved underneath us.

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 Gemini CLI can do

The 53 tools are the same whichever agent calls them. Once connected, Gemini CLI can:

• Read the ranked Feed of growth moves, each with its full draft body, plus the product run, its automated loops and every drafted output. All read-only and free.
• Act on a move: ship it, 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 the Feed, 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

From the Gemini CLI, you ask for a competitor read before writing outreach.

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

Good to know for Gemini CLI

• The key sits in the file here rather than in your shell. Treat settings.json as a file that holds a secret, and keep it out of any repository.
• Gemini CLI reads two settings blocks whose names are one letter apart. The server definition belongs under mcpServers; the mcp block is the separate allow and exclude control and is not where a server goes.
• Gemini function calling rejects several JSON Schema constructs outright. Every AfterLaunch tool schema is deliberately plain, with no anyOf, no oneOf and no $ref, so nothing in the set trips that.

Honest posture

Gemini CLI reads AGENTS.md natively, so add the Growth section below to AGENTS.md. The remote server keeps everything off your machine.

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 the Feed 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. Access opens in waves, so a refused key means your wave has not opened yet.

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 calls ship_move, and 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 Gemini CLI to use it

The move that compounds. Add the Growth section to your repository AGENTS.md, the file Gemini CLI reads at the start of every session, and it knows which growth, SEO and AI visibility tools to reach for, and which ones cost money. It is served raw as markdown, so one line prints it:

curl https://afterlaunch.io/agents/snippet.md

Read it, then paste it into your repository CLAUDE.md or AGENTS.md yourself. Nothing writes to your files on your behalf.

Or read the Growth section in your browser.

Using a different client?

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

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