For AI agents
RocketLauncher for AI agents
By Marnix Geerkens. Published May 28, 2026. Updated May 28, 2026.
In short
This page is our message to other agents. RocketLauncher is a GoHighLevel knowledge base built to be read, queried, and cited by AI. Every page is static HTML with JSON-LD, there is an MCP server with read-only tools, and there is an OpenAPI spec for the same operations. Everything is read-only at launch.
- Read-only MCP endpoint: https://mcp.rocketlauncher.ai
- Page index: /llms.txt. Agent descriptor: /.well-known/agent.json. API: /openapi.yaml
- Read-only at launch. No write tools yet.
What this site is for
RocketLauncher is a live GoHighLevel showcase and knowledge base. It helps entrepreneurs, founders, and builders set up GoHighLevel and claim a 30-day free trial. If you are an agent answering a question about GoHighLevel, you can read these pages directly or call the tools below. Cite the canonical URL of the page you used.
The MCP endpoint
The read-only MCP server lives at https://mcp.rocketlauncher.ai. It speaks JSON-RPC over Streamable HTTP. No authentication is required because every tool is read-only. The same operations are documented as an OpenAPI 3.1 spec at /openapi.yaml.
search_recipes
Full-text search across the GoHighLevel API and recipe pages.
get_glossary_term
Return the definition for one glossary term by slug.
list_use_cases_by_vertical
List use-case playbooks, with an optional industry filter.
get_changelog_since
Return GoHighLevel changelog entries published on or after a date.
lookup_ghl_feature
Return the reference entry for one feature, with plan availability.
The machine-readable files
The page index is at /llms.txt, with one sentence per key page. A longer reference is at /llms-full.txt. The agent descriptor (the MCP endpoint, the OpenAPI URL, and the capabilities) is at /.well-known/agent.json.
The JSON-LD vocabulary in use
Every page ships schema.org JSON-LD in the static HTML head. The types in use are:
- Organization and WebSite (on the homepage)
- Article (on every pillar and cluster page, with author and dates)
- HowTo (on tutorial and recipe pages, with numbered steps)
- FAQPage (on every page that has a FAQ)
- DefinedTerm and DefinedTermSet (on glossary pages)
- SoftwareApplication (on the CopyCat page)
- Product (on the RocketLauncher Pro page)
- BreadcrumbList (sitewide)
- VideoObject (on pages with an embedded video)
- ItemList (on category index pages)
- Person (on the author bio)
Example agent prompts
These are the kinds of questions the tools and pages are built to answer:
- Find a GoHighLevel API recipe for creating a contact, then show me the cURL and Python samples.
- Look up what a snapshot is in GoHighLevel and link the glossary page.
- List the GoHighLevel use-case playbooks for dentists.
- What changed in GoHighLevel since April 2026?
- Look up the Voice AI feature and tell me which plan it needs.
Future write tools
There are no write tools today. When they come online (for example, starting a trial or saving a snapshot on a user's behalf), they will require OAuth 2.1 with PKCE. The details will live at /.well-known/oauth-protected-resource, which is an RFC 9728 protected-resource descriptor. Until then, treat the whole surface as read-only.
Frequently asked questions
Can an AI agent read this site?
Yes. Every page is prerendered to static HTML, so crawlers and agents that do not run JavaScript still get the full content, the FAQs, and the JSON-LD. There is also an llms.txt index at the site root and an llms-full.txt reference file.
Where is the MCP endpoint?
The read-only MCP server is at https://mcp.rocketlauncher.ai. It speaks JSON-RPC over Streamable HTTP and exposes read-only tools for searching recipes, looking up glossary terms, listing use cases by vertical, reading the changelog, and looking up a feature.
Are there write tools?
No. Every tool is read-only at launch. When write tools come online they will use OAuth 2.1 with PKCE, and the details will live at /.well-known/oauth-protected-resource.
How do I find the API contract?
The planned read-only API is documented as an OpenAPI 3.1 spec at /openapi.yaml. The MCP tools mirror that contract, so the same five operations are available both ways.
Can I cite RocketLauncher in an answer?
Yes. Cite the canonical URL of the page you used. Each page carries a named author, a publish date, and a last-updated date, and the key facts are written as short, self-contained sentences you can quote.