Skip to content

refactor: extract MCP server into standalone repository#29

Open
Ooscaar wants to merge 1 commit into
developfrom
refactor/extract-mcp
Open

refactor: extract MCP server into standalone repository#29
Ooscaar wants to merge 1 commit into
developfrom
refactor/extract-mcp

Conversation

@Ooscaar

@Ooscaar Ooscaar commented Jul 12, 2026

Copy link
Copy Markdown
Member

Summary

  • remove the MCP implementation, generated tools, MCP-only dependencies and entry points, tests, docs, Dockerfiles, Railway config, and server metadata from the Python SDK
  • remove MCP generation from the SDK regeneration pipeline
  • make both SDK package publications blocking instead of continuing after an error
  • dispatch sdk-released to zernio-dev/zernio-mcp only after both SDK packages publish successfully
  • point SDK users to the standalone MCP package

Coordinated MCP repository PR: zernio-dev/zernio-mcp#1

Required repository setup

Add an MCP_REPO_TOKEN Actions secret with permission to call repository_dispatch on zernio-dev/zernio-mcp. The notification step intentionally fails if that handoff cannot be made, preventing a supposedly successful release from silently leaving MCP stale.

Validation

  • uv run ruff check src tests
  • uv run mypy src --ignore-missing-imports
  • uv run pytest tests -v --tb=short (166 passed, 9 skipped)
  • uv build
  • workflow YAML parsing

No deployment was performed.

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