Use AfterLaunch with Cursor

Cursor connects to a remote MCP server through a small JSON file, either per project or globally. Add one entry and the AfterLaunch tools appear in the editor.

Connect

Add this to your .cursor/mcp.json, which is per project. Use ~/.cursor/mcp.json to apply it to every project.

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

Cursor expands the environment placeholder from your shell, so the key stays out of the committed file. Set AFTERLAUNCH_API_KEY before you open the project.

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

In the Cursor chat pane, you line up growth work without leaving the editor.

You

What is queued to improve how people find this product?

Cursor

Reading list_feed. Three items are ready: an llms.txt file, a comparison page, and a backlinks outreach draft. The top one is the llms.txt file. Shall I open the draft?

You

Yes, and check we are not about to pitch a competitor.

Cursor

get_competitors confirms the outreach target is not on your rival roster. Here is the draft.

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 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 Cursor to a growth marketing agent?

Add an afterlaunch entry to .cursor/mcp.json with the url https://afterlaunch.io/api/mcp and an Authorization: Bearer header. Cursor resolves the key from your environment, so it stays out of the committed file, and the tools appear in the chat pane.

Is AfterLaunch a local or a remote MCP server for Cursor?

Remote. The config only points Cursor at an HTTPS endpoint and attaches your key. There is no local process to install and nothing to run on your machine.

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 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?

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