Skip to content

Terms, support and OpenAI domain challenge pages for the ChatGPT plugin directory listing #305

Closed

Description

@jeffreyaven

Summary

Depends on stackql/stackql#893 (ChatGPT plugin directory packaging), parent stackql/stackql#699.

The OpenAI plugin directory listing requires four HTTPS URLs that identify the same publisher as the submission: websiteURL, supportURL, privacyPolicyURL and termsOfServiceURL. As of 2026-11-04, https://stackql.io/privacy returns 200, while /terms, /support and /.well-known/openai-apps-challenge return 404. Target date for the submission is Friday 2026-11-13.

Changes

  1. src/pages/terms.md: terms of service covering the StackQL binaries, the MCP server and the ChatGPT and Claude plugins. No pricing, subscription or promotional claims (the plugin guidelines reject them in listing copy, and the page should not contradict the listing).
  2. src/pages/support.md: support contact details (GitHub issues, email, community channel) and the expected response path. The guidelines require customer support contact details for a verified developer.
  3. src/pages/privacy.md: check it covers the OpenAI minimum (categories of personal data collected, purposes, categories of recipients, retention timelines, user controls) and states that the plugin runs locally, that provider credentials never leave the user's machine, and that first-run binary downloads from releases.stackql.io appear in access logs.
  4. static/.well-known/openai-apps-challenge: the exact challenge token from the portal as plain text, nothing else. Ensure the host serves it as text/plain with no redirect and no trailing content. Only needed if the portal requests domain verification for the local MCP submission; add it when the token is shown.
  5. Docs: add the ChatGPT desktop directory install path to the MCP client install documentation, next to the Claude Desktop connector directory entry, including the Desktop only badge and the Work-mode note.

Verification

  • All four URLs return 200 over HTTPS with no redirect loops.
  • The challenge URL returns only the token.
  • Pages render in the Docusaurus build and pass the existing site checks.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions