메뉴
Use when cutting a new release of mcp-semantic-gateway — bumping the version in pyproject.toml, building the wheel, publishing to PyPI, or troubleshooting the publish step. Triggers on "release", "publish", "bump version", "new version", "PyPI".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when adding, removing, or troubleshooting upstream sources for the mcp-semantic-gateway — native MCP servers, OpenAPI / Swagger specs, or hand-authored skill libraries. Covers `~/.mcp_semantic_gateway/config.toml` syntax, auth wiring, and the `index` rebuild loop.
Use when the mcp-semantic-gateway is connected and the agent needs to find the right tool or workflow for a user request — refunding an order, onboarding a record, triaging an issue, etc. Establishes the search-before-guess pattern. Trigger on any task where the obvious tool name is not already in the agent's context.
Use when the user is setting up the mcp-semantic-gateway for the first time, asks how to install or initialize it, or wants to point a coding agent (Claude Desktop, Claude Code, Cursor, Codex, opencode, pi) at the gateway. Covers `init`, the data directory layout, and the MCP client connection block.
Use when the user wants to generate `SKILL.md` workflows from an OpenAPI / Swagger source via the mcp-semantic-gateway `synth` command, inspect the synth cache, debug rejections, or register the generated library so an agent can find it. Triggers on words like "synth", "generate skills", "skill synthesis", "use cases".
Use when adding a new upstream source type to mcp-semantic-gateway (alongside the existing `mcp`, `openapi`, and `skill` types) — e.g., GraphQL, gRPC reflection, a proprietary catalog API. Walks the config model, ingestion collector, registry surface, and router branches that need to be extended.
Use when contributing to the mcp-semantic-gateway repository — cloning, installing dev dependencies with uv, navigating the source tree, or running the Makefile targets. Triggers on tasks about local development environment for this codebase.
| name | mcp-gateway-release-publish |
| description | Use when cutting a new release of mcp-semantic-gateway — bumping the version in pyproject.toml, building the wheel, publishing to PyPI, or troubleshooting the publish step. Triggers on "release", "publish", "bump version", "new version", "PyPI". |
mcp-semantic-gateway is published to PyPI. The build backend is uv_build; releases are cut via uv build + uv publish.
Single source of truth: pyproject.toml [project] version = "...". SemVer.
0.2.x) — bug fixes, additions to bundled skills, internal refactors.0.x.0) — new CLI commands, new source types, new public APIs.x.0.0) — breaking changes to config.toml schema, MCP tool surface, or on-disk layout.The __version__ in src/mcp_semantic_gateway/__init__.py is read by the --version flag — keep it in sync if it is hard-coded there.
# 1. Bump version
$EDITOR pyproject.toml # bump [project] version
# 2. Lockfile + sanity
uv sync
uv run pytest
uv run ruff check .
# 3. Commit, tag
git commit -am "bump"
git tag v$(grep '^version' pyproject.toml | head -1 | cut -d'"' -f2)
git push origin main --tags
# 4. Build + publish
make build-and-publish
make build-and-publish runs:
rm -rf dist/ && uv build && uv publish
uv publish reads credentials from UV_PUBLISH_TOKEN (a PyPI API token) or ~/.pypirc. Never commit either.
# In a clean venv:
pip install --upgrade mcp-semantic-gateway
mcp-semantic-gateway --version # confirms new version
mcp-semantic-gateway init # smoke test
uv_build bundles everything under src/mcp_semantic_gateway/ automatically, including:
py.typed marker.skills/ tree (consumer + development skills) shipped to onboard targets.Confirm before pushing:
uv build
unzip -l dist/mcp_semantic_gateway-*.whl | grep SKILL.md
uv_build bundles every file under src/mcp_semantic_gateway/ automatically, including non-Python data files like SKILL.md. No __init__.py is needed in skill directories — they ship as resource trees and are read at runtime via importlib.resources. Still, verify the wheel listing on every release; an accidental .gitignore entry or stray exclude rule has cost teams a release before.
uv publish --dry-run # validate tokens + metadata without uploading
PyPI doesn't allow re-using a version. If a release ships broken:
Never republish the same version with edits — yank and bump.