Skip to content

directory listings: outstanding portal steps (OpenAI review, Anthropic review and Verified organization) #902

Open

Description

@jeffreyaven

Outstanding portal steps for the two directory listings of the StackQL local MCP server, split out of #900 so that issue can close. Everything in the repository is done (#896, #899, #901); these items wait on external replies or on a recording.

ChatGPT plugin directory (release process step 11)

Status 2026-11-05: organization ID sent to the OpenAI representative for local MCP allowlisting; business verification started; the ZIP for 1.0.888 is built (make openai-plugin-zip VERSION=1.0.888) and validates. Not yet uploaded.

  • Allowlist confirmed by OpenAI; business verification complete; any non-owner submitter holds Apps Management Write.
  • First upload at platform.openai.com/plugins (Create plugin, Skills only, Upload plugin) to read the validator; mcp_configuration_excluded on the MCPs tab means the allowlist has not landed. Fix anything flagged in packaging/openai-plugin/plugins/stackql/plugin.json, re-render, rebuild, re-upload.
  • Demo recording of the eight manifest test cases (five positive on credential-free GitHub data, three negative), hosted where a reviewer can open it without an account.
  • Set review.demo_recording_url in plugin.json (validate.py treats it as required for MCP review), re-render, PR. Skips the Build workflow.
  • Domain challenge token at https://stackql.io/.well-known/openai-apps-challenge, only if the portal asks (Terms, support and OpenAI domain challenge pages for the ChatGPT plugin directory listing stackql.io#305).
  • Submit for review with the policy attestations; after approval, Publish plugin.
  • Fold the step 11 walk-through into docs/stackql_release_process.md once the first review completes (what the validator flagged, review turnaround, anything the portal asked for that the doc does not cover).

Anthropic directory (release process step 12)

Status 2026-11-05: plugin bundle submitted from stackql/stackql-claude-plugin at main (v1.0.888), held for policy review on the node launcher as expected; auto-publish on; push webhook configured and pinging; email sent to directory@anthropic.com asking how StackQL Studios becomes a Verified organization.

  • Reviewer decision on the launcher hold (shown on the plugin's page at claude.ai/directory/manage). If changes are requested, they ship with the next release version, since the directory serves a new version only when version changes.
  • First version published (by us or the reviewer).
  • Verified organization: reply from directory@anthropic.com and whatever it requires. The validator states that local MCP servers will later be accepted only from Verified organizations; this must be in place before that gate is enforced.

The per-release procedure for both directories is in docs/stackql_release_process.md (steps 11 and 12) and the one-time checklist in packaging/mcpb/docs/anthropic-submission.md.

Activity

  1. jeffreyaven commented on Nov 10, 2026

    @jeffreyaven
    MemberAuthor

    OpenAI (plugins@openai.com) asked for the plugin ZIP or a source link for the desktop-only allowlisting request on 2026-11-10. Gmail blocks archives that contain .js files, so the ZIP cannot travel as an email attachment. It is now attached to the v1.0.888 release as an extra asset with a checksum file: https://github.com/stackql/stackql/releases/download/v1.0.888/stackql-plugin-1.0.888.zip (SHA-256 382d3226674b87bb552c4dd2b34d4f0fdc2774d6aa208ca26707354bd9764057, built from main 4c447cf). Follow-up for the release process: have the release tooling attach the output of make openai-plugin-zip to every release so the directory ZIP always has a stable download URL.

  2. added a commit that references this issue on Nov 12, 2026
  3. self-assigned this
    on Nov 12, 2026
  4. jeffreyaven commented on Nov 13, 2026

    @jeffreyaven
    MemberAuthor

    Reopening: #910 adds a release helper but does not complete the outstanding external directory review and verification steps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions