Use AfterLaunch with Cursor

Connect

Add this to your ~/.cursor/mcp.json, your user-level file, outside every repository, so it applies to every project.

{
  "mcpServers": {
    "afterlaunch": {
      "url": "https://afterlaunch.io/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:AFTERLAUNCH_API_KEY}"
      }
    }
  }
}

Put the block in ~/.cursor/mcp.json, your user-level file outside every repository, and replace ${env:AFTERLAUNCH_API_KEY} with the key itself. Never put the key in a project's .cursor/mcp.json, which is committed with the project. Then fully quit Cursor (Cmd-Q) and reopen it, and check Settings, MCP: AfterLaunch should show its tools. To keep the key out of the file instead, add export AFTERLAUNCH_API_KEY=... to ~/.zshrc and fully quit and reopen Cursor; a variable exported after Cursor started is never seen.

Not verified. Wording updated 21 Oct 2026, live check pending: this exact wording has not been run against the AfterLaunch server yet.

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 Cursor can do

The 62 tools are the same whichever agent calls them. Once connected, Cursor 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 the Cursor chat pane, you line up growth work without leaving the editor.

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

Good to know for Cursor

• Cursor lists connected servers under Settings, MCP. A green dot means afterlaunch handshook; a red dot usually means the key variable is unset, which reads exactly like a refused key, so check that first.
• Cursor publishes no MCP tool limit, and the ceiling it was once reported to have is neither confirmed nor withdrawn. If the tools list looks short, count what Cursor shows against what the server serves.

Honest posture

Cursor reads AGENTS.md natively, so drop the Growth section below into AGENTS.md and the editor knows which growth, SEO and AI visibility tools to reach for.

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 Cursor to use it

The move that compounds. Add the Growth section to your repository AGENTS.md, the file Cursor 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 ChatGPT instead? →
• Using Windsurf instead? →

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