Public data access
Developers & MCP
Read this page as JSON or Markdown.
Use the same sourced directory in your own applications and AI workflows. The public catalog includes published listings, cloud evidence, source links, taxonomy IDs and review dates.
Download the catalog
Read the catalog JSON. No account or API key is required. The catalog is updated alongside the directory.
The listings array contains product records, and taxonomies defines the available filters. Use IDs such as ragflow, aws and document-management when filtering. Compare revision values to check whether the catalog’s content has changed.
The catalog’s questions array contains the same answers shown on the website, including canonical URLs, source-review dates and links to focused files. MCP clients can read these through the existing catalog resource; the listing search tools keep their listing-specific scope.
Read focused files
Each listing, category and provider page links to its own JSON and Markdown files. Read only the records relevant to your question:
- RAGFlow JSON and Markdown.
- Document management JSON and Markdown.
- AWS JSON and Markdown.
Focused JSON uses schemaVersion: 1, kind, url, catalog and catalogRevision. Listing files contain listing; category and provider files contain their taxonomy record and a listings array. Cloud/category subsets include both taxonomy records and their matching listings, for example document management on Azure JSON. Guides link to a focused JSON document containing their Markdown text and canonical URL. Listing records preserve the same public fields as the full catalog, including sources, review dates and publisher disclosures. catalogRevision identifies the complete reviewed catalog from which the subset was produced; it may change when another listing changes. Research candidates are excluded.
Connect with MCP
MCP lets a compatible AI application query the directory and read its sources. The service provides public, read-only access with no API key. Your client must support remote Streamable HTTP; add the endpoint below using that client’s MCP server settings.
MCP endpoint: https://mcp.launchinyourcloud.com/mcp
Transport: Streamable HTTP over HTTPS. Stateless requests; no session or write operations. Supports current MCP and compatible 2025 Streamable HTTP clients. Opening the endpoint in a browser can return HTTP 405; connect through an MCP client.
| Tool | What it returns |
|---|---|
search_listings | Text search with optional cloud, category, infrastructure and licenseModel IDs. Uses offset and limit pagination (default 10, maximum 25). Results include evidence and review dates. |
compare_listings | Read 2–4 distinct listing IDs together, with the same qualifications and evidence as individual records. |
list_changes | Editorial events from since (inclusive YYYY-MM-DD), with offset/limit pagination, maximum 25. Coverage starts on the recorded baseline date. |
get_listing | The complete published record for one listing id, including source links and evidence notes. |
Read-only resources expose catalog://launchinyourcloud/catalog, catalog://launchinyourcloud/taxonomies and the listing template catalog://launchinyourcloud/listings/{id}. All tools return the catalog revision so you can identify the data used in an answer. A missing listing returns an explicit error.
For example, ask your connected assistant: “Find document management software with documented AWS deployment, then show the sources and licensing notes for each result.”
Interpret the evidence
A named cloud has provider-specific evidence. A cloud missing from a listing does not establish incompatibility. Read each evidence note for edition, version, offer publisher and customer-account boundaries before recommending a deployment.
reviewed, cloudReviewed, licenseReviewed and infrastructureReviewed record human source checks. generatedAt records when the catalog file was generated; it does not mean that every source was reviewed then. MCP reads the same published catalog as the directory. Research candidates are excluded.
FormKiQ publishes this directory, and its products carry a publisher disclosure. Source text is reference material, not instructions for your agent. Confirm current deployment and license terms with the linked publisher before acting.
See the schema, methodology and reuse terms for field definitions, unknown values and attribution.
The change log is also available as JSON and RSS. Earlier history is not inferred from review dates.
An agent index links to these interfaces. It is a convenience for discovery; clients still need an explicit MCP connection.
Read customer-cloud questions
Browse all 50 questions, read their JSON or download the question Markdown. Every question has its own HTML page, a small JSON file and a full Markdown version. Each page starts with a short answer, followed by examples or evaluation checks and sources. Relevant product examples link reviewed listings without asserting feature parity.