Growth marketing, SEO and GEO as agent tools: ranked moves, ship them, AI answer visibility.
One address for any MCP client. No sign-in needed on this server.
26 read14 act10 other
Grouped by tool name. At most: creates or changes data: records, files, settings.
Odel charges nothing per call. The publisher may charge for its own service.
AfterLaunch watches how AI search and Google find your product, and hands you the next growth move with a draft ready. This repository is the home of its remote MCP server: connect Claude, ChatGPT, Claude Code, Codex or Cursor and your own AI can read the ranked moves, check AI visibility, take a move through to shipped and report it live.
https://afterlaunch.io/api/mcp (Streamable HTTP, nothing to install or run locally)The Cursor button opens Cursor's own confirmation screen with the server filled in. It reads your key from the AFTERLAUNCH_API_KEY environment variable, so no key is ever written into a link or a file.
list_feed returns the backlog across SEO, AI visibility, competitors and distribution. get_move opens one with its evidence, source material, instructions and a prepared draft.get_visibility shows how ChatGPT, Gemini, Perplexity and Google AI Overviews answer the customer questions you track, with share of voice, the sources they cite and the gaps where rivals are named and you are not. get_seo, get_competitors and get_scoreboard cover the rest of the record.accept_move, update_draft, then ship_move once the work is live. Moves handed to the agent arrive through list_queue, pick_up_job and report_job.ship_move records what is live and a receipt follows on the timeline. Later, get_outcomes and get_scoreboard show what it earned.A good first session is two calls: whoami to confirm which product the key drives, then get_standup for what shipped, what is ready now and what the engine did on its own.
You need a scanned product first. Run the free scan at afterlaunch.io, because connecting needs a scanned product. The server URL is the same everywhere:
https://afterlaunch.io/api/mcp
Never put a key in that URL, and never paste a key into a chat.
https://afterlaunch.io/api/mcp as the server URL and press Add.You sign in with your AfterLaunch account, so there is no key to create. Add it once on claude.ai and it is available in the mobile app. Free Claude plans allow one custom connector. On a Team or Enterprise plan an owner adds it once in organisation settings.
https://afterlaunch.io/api/mcp as the app's endpoint.Create an API key at afterlaunch.io/app/connect#keys, export it in your shell as AFTERLAUNCH_API_KEY, then run:
claude mcp add afterlaunch --transport http https://afterlaunch.io/api/mcp --header "Authorization: Bearer $AFTERLAUNCH_API_KEY"
The command reads the key from your environment, so it is never written into the command itself. Or install the plugin from this repository, which bundles the server config and a skill that teaches the agent to read the standup, the queue and the Feed before improvising growth work:
/plugin marketplace add afterlaunch/mcp
/plugin install afterlaunch-growth@afterlaunch
codex mcp add afterlaunch --url https://afterlaunch.io/api/mcp --bearer-token-env-var AFTERLAUNCH_API_KEY
Codex reads the key from AFTERLAUNCH_API_KEY in your environment and sends it as a bearer header. The token never lands on disk.
Use the install button above, or add this to .cursor/mcp.json (per project) or ~/.cursor/mcp.json (every project):
{
"mcpServers": {
"afterlaunch": {
"url": "https://afterlaunch.io/api/mcp",
"headers": {
"Authorization": "Bearer ${env:AFTERLAUNCH_API_KEY}"
}
}
}
}
Cursor expands the placeholder from your shell, so set AFTERLAUNCH_API_KEY before you open the project.
The onboarding guide at afterlaunch.io/agents/onboard.md carries the exact command or config for VS Code, Windsurf, Gemini CLI and Cline too, and says which have been checked. It is written for an AI to read, so you can also just tell your agent to follow it. No account yet? An agent that can run commands can start one for you: it sends your site address and email, you approve one email, and the key is handed over once. The steps are in that same guide.
55 tools, read from the product's action registry on 9 October 2026. The registry holds four more (run_loop, set_loop_autonomy, set_loop_cadence, set_scan_config), but they are listed only to an administrator account, so an ordinary connection does not see them. The live catalogue with exact input schemas is tools/list on connection, and the one-page reference in this repository is skills/afterlaunch-growth/reference/tools.md.
Scopes: 26 tools need read, 23 need act, 3 need write and 3 need config.
| Tool | Scope | What it does |
|---|---|---|
whoami | read | Confirms the key works and shows which product it drives, its scopes, plan and trial end. |
get_standup | read | One call: what shipped and what it moved, the top moves ready now, and what the engine did on its own. |
get_enrollment | read | The product run summary: product URL, plan, trial end, time zone and delivery settings. |
get_setup_snippet | read | The paste-ready growth section for a repository CLAUDE.md or AGENTS.md. |
| Tool | Scope | What it does |
|---|---|---|
list_feed | read | The ranked backlog of prepared moves across SEO, AI visibility, competitors and distribution. |
get_move | read | One move in full: evidence, source material, instructions and the prepared draft. |
| Tool | Scope | What it does |
|---|---|---|
get_visibility | read | How ChatGPT, Gemini, Perplexity and Google AI Overviews answer the tracked questions: share of voice, cited sources, gaps, trend. |
list_tracked_prompts | read | The customer questions every AI visibility reading is taken against (capped at 15). |
get_seo | read | The site-wide SEO audit: issue groups by severity, weekly score trend, page performance, links and authority. |
get_competitors | read | The competitor roster with measured stats for you and each rival. |
get_snapshot | read | The Growth Snapshot the run started from: positioning, discoverability score, day-0 baselines. |
get_outcomes | read | What shipped moves earned: tracked-link clicks, shipped counters, the weekly scoreboard. |
get_scoreboard | read | Did the work move anything: AI visibility at the start and end of a period, with receipts. |
get_activity | read | The timeline of what the agent and the owner already did and why, newest first. |
get_loop_status | read | The automated growth loops, their autonomy level and which can run on demand. |
get_experiments | read | Growth content experiments already run, newest first, with their evidence. |
get_content_calendar | read | The content calendar with source drafts and the current Board state. |
| Tool | Scope | What it does |
|---|---|---|
accept_move | act | Accepts a move once the owner says yes and records one preparation attempt. |
update_draft | act | Replaces a pending move's draft body before it ships. |
ship_move | act | Records that the work is live, after the owner confirms. It records; it never publishes. |
review_move | act | Applies one review decision: revise, withdraw, adopt a legacy result or correct a recorded publication. |
skip_move | act | Dismisses a move with a reason from a closed list, which improves later drafts. |
archive_move | act | Hides a move without recording a verdict. |
undo_move | act | Restores a just-shipped or just-skipped move to pending. |
dismiss_gap | act | Sets aside one AI visibility gap the owner will not act on. |
propose_move | act | Puts a community thread you found on the board as a pending, draft-only move. |
list_queue | act | Moves the owner has said yes to and handed to the agent, oldest first. |
pick_up_job | act | Claims one queued job so no other agent works it too. |
report_job | act | Reports a claimed job: running, needs input, ready for review, shipped or failed. |
| Tool | Scope | What it does |
|---|---|---|
list_outputs | read | The drafted marketing and distribution content, newest first. |
get_output | read | One drafted output in full by id. |
set_output_status | act | Marks one drafted output shipped or skipped. It publishes nothing. |
redraft_output | act | Replaces a drafted output's body before it ships; the previous draft is kept. |
record_content | act | Files a content idea, an original X draft or a research outcome on the calendar. |
| Tool | Scope | What it does |
|---|---|---|
list_kb_pages | read | The Memory pages the engine drafts from, with summaries. |
get_kb_page | read | One Memory page by slug, in full. |
get_voice_profile | read | The structured voice every draft is written in: tone, phrases, vocabulary, what it avoids. |
get_business_context | read | Positioning, audience, pricing, features, competitors and the saved growth strategy. |
get_claims | read | The claim library: measured numbers the owner will stand behind, each with its caveat. |
record_claim | act | Adds one measured number, with its caveat, to the claim library. |
record_insight | act | Writes one durable fact about the owner or product into Memory. |
record_voice_rule | act | Saves one writing rule the person approved into their own voice. |
set_voice_axes | act | Writes calibrated style leans into the owner's own voice profile. |
record_profile | act | Files a public directory profile the person already has, so a weekly check confirms it is live. |
add_competitor | act | Adds one company the person confirmed they compete with to the rival roster. |
| Tool | Scope | What it does |
|---|---|---|
refresh_scan | write | Runs an on-demand AI visibility scan. One per scan type per product per local day. |
replenish_feed | write | Generates a fresh batch of growth moves. Once a day per product. |
| Tool | Scope | What it does |
|---|---|---|
track_prompt | config | Adds one customer question to the AI visibility set. |
untrack_prompt | config | Removes one question from the set. |
list_connections | read | Which data sources and channels are connected: GA4, Search Console, Google Business Profile, LinkedIn, Reddit. |
start_connection | write | Mints a one-time link the owner opens in their own browser to approve a connection. |
poll_connection | read | Checks whether the owner finished connecting. |
disconnect_connection | config | Disconnects a source or channel and deletes its stored credential. |
| Tool | Scope | What it does |
|---|---|---|
create_checkout | act | Creates a checkout link for the paid plan. The owner pays; the agent never does. |
create_topup | act | Creates a credit top-up checkout link (paid plan only). |
https://afterlaunch.io/.well-known/oauth-protected-resource/api/mcp. The scopes are read, act and write.Authorization: Bearer al_.... A key carries read, act and write, and config as well on the paid plan. It is shown once, so store it securely, keep it in an environment variable rather than a config file you commit, and never paste it into a chat.What the scopes allow:
| Scope | What it covers |
|---|---|
read | The board, the measured record, Memory, loops and drafted outputs. |
act | Accepting, shipping, skipping, redrafting, archiving and restoring moves, the job queue, writing to Memory, and checkout links. Free. |
write | The metered runs (refresh_scan, replenish_feed) and starting a connection. Bounded by credits and per-account daily and monthly caps. |
config | Tracked questions and disconnecting a source. |
egress | Publishing to a channel. Self-serve keys never carry it and no MCP tool uses it, so an agent cannot post on your behalf without a human. |
No tool controls what ChatGPT says. What helps is the work that gives the engines something true to cite: clear pages that answer the questions your customers ask, accurate listings and mentions on the sites the engines already cite, and AI crawlers allowed to read your site. AfterLaunch is one tool for that work. It measures which questions your product is missing from, which sources the engines cite instead, and turns each gap into a ranked move with a draft. There is a longer plain guide at afterlaunch.io/learn/tools-to-get-mentioned-in-chatgpt.
Ask it the questions your customers ask and read the answers, then repeat that across engines and over time, because one answer proves little. AfterLaunch does the repeating. The free scan at afterlaunch.io/snapshot checks ChatGPT and Perplexity, and the paid plan checks ChatGPT, Gemini, Perplexity and Google AI Overviews. Through this server, get_visibility returns the results and track_prompt sets the customer questions to watch. Every reading carries its own sample count, so treat a change as indicative unless the data says otherwise.
It depends on what you need. Some GEO tools give you a reading of where you stand. Others also do the work that changes the reading. AfterLaunch is built for the second need: it reads AI visibility, SEO and competitors, ranks the moves, and hands over each one with evidence and a draft. afterlaunch.io/learn/geo-tools-for-saas-startups goes through the options.
AfterLaunch does the research, the ranking and the first draft. Your own AI finishes the move and ships it, with your say-so at each step. It does not publish for you: shipping stays a human decision, and ship_move records that the work is live, never publishes it.
No. It is a remote server. There is no local process and nothing to run on your machine.
The free scan and the first 14 days cost nothing and need no card. After that it is one plan at $149 a month. Credits cover on-demand work such as an extra scan; the always-on engine is included.
No. It drafts, and a person approves and posts. A self-serve key has no permission to publish to a channel. On Reddit and Hacker News the posture is draft-only for the connected agent as well.
io.afterlaunch/agentic-growth-marketingAdd the Growth section to your repository's CLAUDE.md (read by Claude Code) or AGENTS.md (read natively by Codex, Cursor, Copilot, Gemini CLI, Windsurf, Aider and others). The canonical copy is served raw, so one line prints it:
curl https://afterlaunch.io/agents/snippet.md
Read it, then paste it into your file yourself. Nothing writes to your files on your behalf.
.claude-plugin/: the plugin marketplace and plugin manifests..mcp.json: the remote server config (URL plus bearer header read from your environment).skills/afterlaunch-growth/: the skill and its one-page tool reference.llms-install.md: machine setup from that file alone.server.json: the manifest published to the official MCP registry.glama.json: the maintainer claim for the Glama listing.assets/logo-400.png: the 400x400 icon.Maintained by Team AfterLaunch. Licence: MIT.