Repository navigation
Make the ChatGPT/Codex package submittable without hand-edits - #33
Merged
Merged
Conversation
OpenAI submission needs .mcp.json, a short description of at most 30 characters, and a version greater than the published 1.16.2. Stamp the zip from server.json so Codex stays aligned with Jam MCP, and ship the five MCP-only skills (jam, jam-fix, jam-to-e2e, jam-to-tasks, jam-to-ticket). Co-authored-by: Tomasz Cichocinski <baransu@users.noreply.github.com>
Stamp description and longDescription with the five-skill ChatGPT text. Leave the 30-character short description unchanged. Co-authored-by: Tomasz Cichocinski <baransu@users.noreply.github.com>
Keep the ChatGPT packager work and take upstream canonical docs URLs plus the jam-setup changelog wording. Co-authored-by: Tomasz Cichocinski <baransu@users.noreply.github.com>
jam-to-tasks and jam-to-ticket now use Jam MCP when it is connected, with CLI setup in references/cli.md, so ChatGPT does not stop for a missing jam binary. Release notes list the packaged skills and version instead of claiming every rebuild adds those skills. Co-authored-by: Tomasz Cichocinski <baransu@users.noreply.github.com>
Cursor mcp.json stays {url}. .mcp.json and the ChatGPT zip add
type http, which CI's plugin validate requires for remote servers.
Co-authored-by: Tomasz Cichocinski <baransu@users.noreply.github.com>
If mcp.json has no Jam URL, keep listing the other broken rules instead of aborting the rest of scripts/check.mjs. Co-authored-by: Tomasz Cichocinski <baransu@users.noreply.github.com>
Keep scanning .mcp.json and Markdown links when the Cursor MCP file is absent, so every broken rule still prints. Co-authored-by: Tomasz Cichocinski <baransu@users.noreply.github.com>
JSON null/false skipped the Jam URL check and the .mcp.json compare, so packaging would still fail. Record those as check failures. Co-authored-by: Tomasz Cichocinski <baransu@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The ChatGPT directory zip from this repo was not submittable as an update. Packaging from master produced
mcp.jsoninstead of.mcp.json, a short description over OpenAI’s 30-character limit, and version2.0.0(never published; the live listing is1.16.2). This change makesnode scripts/package-chatgpt.mjsemit a zip that matches OpenAI’s plugin submission rules: Codex MCP config at./.mcp.json,interface.shortDescriptionof at most 30 characters, semantic version, andextensions.com.openai.publication.release_notes.Version.
1.36.3is the currentdev.jam/jamversion in the MCP registry and inserver.json. That is greater than the published1.16.2, so the platform will take it as an update. The packager stamps the zip fromserver.json..codex-plugin/plugin.jsonmust match; CI fails if it drifts. Claude, Cursor, and Gemini stay on plugin2.0.0so those listings are not rolled back.Skills. The zip now ships five MCP-oriented skills:
jam,jam-fix,jam-to-e2e,jam-to-tasks,jam-to-ticket. All five use Jam MCP when it is connected. CLI setup forjam-fix,jam-to-e2e,jam-to-tasksandjam-to-ticketlives inreferences/(rewritten to GitHub links in the zip). CLI/shell skills stay out of the zip (jam-proof,jam-annotate,jam-setup,jam-proof-table,video-to-jam,record-demo,record-terminal-proof,add-voiceover).Caveats:
jamrouter still names skills that are not in the zip (jam-proof,jam-annotate, and the rest). ChatGPT cannot load those.jam-to-ticketstill uses a connected tracker MCP first, thengh, then paste-in-chat. Thatghpath is GitHub’s CLI, not the Jam CLI.MCP URL remains
https://mcp.jam.dev/mcp..mcp.jsonadds"type": "http"for Claude Code plugin validate; Cursormcp.jsonstays{url}. Listing copy: short descriptionDebug and test from Jam links; description / longDescription name the five packaged jobs.Do not merge from this PR; upload the zip as an update to the existing app, not Upload New.