Distribution: how git-into-gsoc reaches each assistant

This page is for maintainers. People who want to install the tool should read use git-into-gsoc in your AI assistant.

One repository, every native format

Several assistants read another assistant's plugin format, so a few files cover many tools:

All plugin manifests, server.json, the install buttons in README.md and docs/assistants.md, and the one-click links on the project site (site/index.html) are written from one definition, src/git_into_gsoc/install/distribution.py. The server reads its own description and icons from there too, so assistants and directories show the same name, text, and logo. After changing it:

python scripts/sync_integrations.py           # rewrite the files
python scripts/sync_integrations.py --check   # what the tests run

Launch commands

• Plugins and extensions run the server from their own installed copy: uvx --from ${CLAUDE_PLUGIN_ROOT}, uvx --from ${extensionPath}, or, for Codex, uvx --from . with cwd: ".". The server then always matches the skill next to it, updates arrive with the plugin, and nothing is cloned when it starts.
• One-click buttons and copied configs run the newest PyPI release: uvx git-into-gsoc@latest mcp. They need only uv, and uv checks PyPI for a newer release at every start. Before the package was on PyPI they ran main from GitHub, which also needed Git.
• git-into-gsoc setup writes the absolute path of the installed command, which works offline and starts fastest.

What happens at release

Release Please bumps version in pyproject.toml, src/git_into_gsoc/__init__.py, the three plugin manifests, gemini-extension.json, and server.json. After the release:

• release.yml uploads the wheel and source archive to PyPI, and dispatches mcp-registry.yml, which attaches the wheel, source archive, and git-into-gsoc.mcpb to the release and publishes the registry entry. The committed server.json lists only the PyPI package, with no version, which means the newest release. The workflow keeps every other field and replaces the package list with that release's bundle and its PyPI version. The registry accepts a PyPI package only after PyPI serves that version, so the workflow waits up to 10 minutes for it, and retries for up to 10 more when the registry still answers that the version was not found. If it never does, the entry lists only the bundle and the run shows a warning.
• Claude Code, Codex, and Copilot see the new version and offer the update. Gemini CLI compares release tags, so --auto-update installs pick it up at the next start.

Compatibility checks

scripts/check_agents.py installs the plugin, and with --setup runs git-into-gsoc setup, for every agent command it finds. Each agent gets a throwaway home folder, with token variables removed and no model calls. It then asks the agent what it registered and checks that the server answers. Before installing from a checkout, it also runs each format's own validator: claude plugin validate --profile directory (the checks Anthropic's plugin directory runs on a submission), gemini extensions validate, and, when Node.js is installed, the MCP bundle validator @anthropic-ai/mcpb validate. tests/unit/test_manifests.py checks server.json against a copy of the registry's schema in tests/fixtures/. scripts/mcp_smoke.py is the MCP client the script uses; it works against any launch command:

python scripts/check_agents.py --setup              # this checkout, every agent installed here
python scripts/check_agents.py --remote --only codex  # what people get from GitHub
python scripts/mcp_smoke.py -- uvx --from . git-into-gsoc mcp

.github/workflows/agents.yml runs it on Linux with pinned versions of Claude Code, Codex, Gemini CLI, and Copilot CLI, plus the current Antigravity CLI, Cursor agent CLI, and VS Code from their vendors' installers, whenever the files they read change. It also checks the one-click button configs and the Claude Desktop bundle. Every Monday it also runs with their newest releases and installs from GitHub, because agents change their formats often. Bump the pinned versions in that workflow from time to time.

Where people can find it

Checked on 2026-10-22. Listings change without notice, so re-check before relying on a row.

Listed, nothing to do

Waiting on someone else

Needs the owner

Each needs the repository owner's account or decision, and most are reviewed by a person. The files they need are already in the repository unless noted.

Where GSoC applicants look

Checked on 2026-11-01. Directories above reach people who already use an assistant. The people this tool is for search for "how to prepare for GSoC" and read community lists, so these matter more, and each needs the owner's account or voice.

Looked at, not adopted

Details most forms ask for

Source: docs/distribution.md on GitHub. Corrections are welcome.