Agent guides

Use AfterLaunch with Claude Code

Claude Code speaks MCP natively and reads your repository CLAUDE.md at the start of every session, so it is the shortest path to wiring AfterLaunch into the place you already work. One command connects it.

Connect

Run this once in your project:

claude mcp add afterlaunch --transport http https://afterlaunch.io/api/mcp --header "Authorization: Bearer $AFTERLAUNCH_API_KEY"

Export AFTERLAUNCH_API_KEY in your shell first, or paste the key inline in place of the variable. Claude Code runs tool search by default, so once connected it can find the growth tools on its own.

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 Claude Code can do

The 53 tools are the same whichever agent calls them. Once connected, Claude Code 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

Mid-build in the terminal, you ask Claude Code to check discoverability before you push a release.

You

Before I ship v2, how are AI engines answering questions about us, and what should I fix first?

Claude Code

Calling get_visibility. ChatGPT and Google AI Overviews name two competitors but not you for "best tool in your category". Reading list_feed: the top item is an FAQ schema fix on your pricing page. Want me to draft it?

You

Draft it and show me before anything changes.

Claude Code

Here is the draft from update_draft. Nothing ships until you run ship_move.

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

Good to know for Claude Code

  • Claude Code reads your repository CLAUDE.md at the start of every session, so the Growth section below wires the tools in for good. It does not read AGENTS.md: if your repo already keeps its instructions there, put a line reading @AGENTS.md at the top of CLAUDE.md and Claude Code loads both.
  • Run claude mcp list in your shell to confirm the afterlaunch server is connected before you rely on the tools.
  • The key lives in your shell environment as AFTERLAUNCH_API_KEY, never in the repository.

Honest posture

Claude Code reads CLAUDE.md, so the paste-able Growth section below teaches every future session without another connect step.

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

How do I connect Claude Code to a growth marketing agent?

Run claude mcp add afterlaunch --transport http https://afterlaunch.io/api/mcp --header "Authorization: Bearer $AFTERLAUNCH_API_KEY". Mint the key in AfterLaunch Settings first, or let Claude Code run the onboarding flow. Claude Code then has all 53 AfterLaunch tools.

Does Claude Code reach for AfterLaunch on its own?

Add the Growth section to your CLAUDE.md and every future session uses the AfterLaunch tools without another connect step. The block is served raw at https://afterlaunch.io/agents/snippet.md. Claude Code reads CLAUDE.md rather than AGENTS.md, so if your repo keeps its instructions in AGENTS.md, import it from CLAUDE.md with a line reading @AGENTS.md.

Is AfterLaunch a growth marketing MCP server?

Yes, though the server is the door rather than the product. AfterLaunch is the agentic growth engine: it watches how the leading AI search engines answer about you, audits every page of your site, tracks your competitors and the communities and directories that decide whether you get found, and keeps the history. The remote MCP server at https://afterlaunch.io/api/mcp speaks Streamable HTTP and exposes 53 tools, so an agent reads the ranked Feed of prepared growth work, ships or redrafts it, and reads the product run, its automated loops and its drafted outputs. Reads are free. The on-demand runs are metered and capped per tenant per day and per month.

Can I use it as an SEO MCP server or an AI visibility MCP?

The same server exposes get_seo, the site-wide SEO audit with search ranks, links and ready-to-apply fixes, and get_visibility, how ChatGPT, Gemini, Perplexity and Google AI Overviews answer questions about your product, with share of voice and cited sources. Both reads are free and need only a valid key.

Teach Claude Code to use it

The move that compounds. Add the Growth section to your repository CLAUDE.md, the file Claude Code 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?

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