Claude Code
AfterLaunch is the agentic growth engine: it measures how your product gets found and ranks the next move. One command wires it into Claude Code over MCP.
Read →AfterLaunch watches how customers find you and keeps a ranked board of your next growth moves, with the evidence behind each rank. Your agent reads that board over MCP. Pick your agent for the exact connect config and an honest note on what it can do.
AfterLaunch is the agentic growth engine: it measures how your product gets found and ranks the next move. One command wires it into Claude Code over MCP.
Read →AfterLaunch is the agentic growth engine, measuring how the leading AI search engines answer about you. Gemini CLI reads it over MCP from settings.json.
Read →AfterLaunch is the agentic growth engine: the ranked, briefed record of how your product gets found. Claude on the web reads it over MCP at /api/mcp.
Read →These have no page of their own, which changes nothing about what you paste. The endpoint and the header are the same everywhere. What differs is the field names, and here they are.
Run this once in your project:
codex mcp add afterlaunch --url https://afterlaunch.io/api/mcp --bearer-token-env-var AFTERLAUNCH_API_KEYCodex reads the key from AFTERLAUNCH_API_KEY in your environment and sends it as a bearer header. The token itself never lands on disk.
Add this to your Cline MCP settings, opened from the Cline panel: MCP Servers, then Configure, then Configure MCP Servers. Cline's documentation gives two different paths for that file, so let Cline open it rather than hunting for it.
{
"mcpServers": {
"afterlaunch": {
"type": "streamableHttp",
"url": "https://afterlaunch.io/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_AFTERLAUNCH_API_KEY"
}
}
}
}The type line is the one that matters. Cline treats a missing type as the older SSE transport, which this server does not serve, so leaving it out fails the handshake with no explanation.
Connect it like this:
There is nothing to set up on the phone itself. A connector belongs to your Claude account rather than to one device, so a connection made on the web is there the next time you sign in on the app. Adding a custom connector from the phone is still in beta, which is why these steps add it on the web.
Connect it like this:
A web session runs against your Claude account rather than your machine, so there is no local config file and no key to export. Complete the sign-in on claude.ai before you start the session, which is the route Anthropic documents.