Skip to content

feat(submission): prepare MCP-only ChatGPT plugin candidate - #28

Draft
lukas-bekr wants to merge 2 commits into
apify:mainfrom
lukas-bekr:feat/chatgpt-submission
Draft

lukas-bekr wants to merge 2 commits into
apify:mainfrom
lukas-bekr:feat/chatgpt-submission

Conversation

@lukas-bekr

@lukas-bekr lukas-bekr commented Oct 26, 2026 •

Copy link
Copy Markdown

Prepare a separate MCP-only Apify package for the planned ChatGPT submission while preserving the existing apify/ developer distribution. The candidate uses 29 individually named tools on the existing root MCP endpoint, includes Web Search/Web Fetch, and packages exactly the portable plugin manifest, generated MCP configuration, and PNG logo. An explicit archive allowlist prevents skills, hooks, private bindings, and review notes from entering the ZIP.

The package includes five positive and three negative review cases, a thirteen-Actor/private-development test matrix, and explicit readiness gaps. It is not ready to submit: the server aliases are not deployed, curated builds are unapproved, live review cases and OAuth remain untested, and a fresh demo, commerce/legal review, and written OpenAI clearance are still required. The publisher selected all portal-supported countries, encoded as an explicit empty country restriction list; verify its import in the portal. The repository metadata retains the current verified URL until an administrator performs the rename.

The manual developer-release workflow now accepts the old/new repository names only for the same immutable repository ID. Coordinate the upstream sync guard first, then rename the existing repository rather than creating a replacement. No rename, release, portal upload, or submission is performed by this PR.

Validation: nine packaging tests pass, including symlink/tampered-archive and accidental skill/hook exclusion cases. The deterministic ZIP was built and inspected; its 29 selectors match the MCP server candidate. Local structure checks do not establish portal acceptance or runtime behavior.

AI assistance: Codex implemented and tested the candidate. Submitted from a fork because the connected account has read-only access to the upstream repository.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant