refactor(opencode): route MCP integrations through gateway aggregate - #97
Merged
Conversation
…nal gateway aggregate Replace the per-integration direct service entries (apify, argocd, aws, aws-docs, cloudflare, context7, grafana, kubernetes, parallel-search, playwright, slidespeak, terraform-docs) and the direct twilio-docs URL in files/opencode.json with one makeitwork entry pointing at the in-cluster vmcp-gateway aggregate endpoint (http://vmcp-gateway.mcp.svc:4483/mcp); aggregate tools surface as makeitwork_<integration>_<tool>. Keep agent-pipe, github, hero-ssh, and codebase-memory as direct per-backend entries (chart-local or intentionally non-aggregated). Update exact tool and member references in the s3-presigned-file-delivery, career-external-documents, and twilio-docs-troubleshooting skills, revise the README MCP routing/Cloudflare/Twilio/SlideSpeak/prerequisite guidance, and bump the chart version to 0.1.75 for the changed packaged content.
…ated Cloudflare/Twilio/SlideSpeak delivery Add an MCP routing section documenting the single internal makeitwork aggregate entry (makeitwork_<integration>_<tool> tool naming) and the four remaining direct per-backend entries; rewrite the Cloudflare and Twilio documentation MCP sections for aggregate delivery (read-only token boundary; public-docs-only proxy with no credentials); and update the prerequisites and SlideSpeak paragraphs to name the vmcp-gateway aggregate Service.
…ate MCP in AGENTS.md; record outage/rollback acceptance Correct the aggregate AWS tool example to makeitwork_aws_aws___get_presigned_url (the aws member's upstream tools already carry their own aws___ prefix) in the README MCP routing section and the s3-presigned-file-delivery skill. Update the charts root AGENTS.md session boundary to route aggregate tools through the single makeitwork gateway entry (makeitwork_<integration>_<tool>) while distinguishing the four direct integrations (agent-pipe, github, hero-ssh, codebase-memory). Record the 2026-09-11 owner acceptance of the temporary OpenCode integration outage and the paired rollback requirement for the 0.1.75 aggregate cutover in the README delivery lifecycle. Skill content is packaged chart content already covered by the unpublished 0.1.75 version bump; no additional bump required.
Chart CI passedRepository hygiene and Helm validation passed. View the workflow run. |
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
1 participant
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.
Summary
Routes OpenCode MCP integrations through one internal
makeitworkgateway aggregate entry, retaining only directagent-pipe, GitHub, hero-SSH, and codebase-memory connections. Documents aggregate tool naming, updates affected packaged skills, and bumps immutableopencode-serverfrom0.1.74to0.1.75.Fixes #
N/A — owner-approved MCP aggregate consolidation.
Type of change
Validation
opencode-serverpackaging..Files.Glob; no generated source was edited.0.1.74to0.1.75.Impact and rollout
Producer: immutable OCI package
ghcr.io/makeitworkcloud/charts/opencode-server:0.1.75; consumer: theopencodeGitOps Application selected by post-publish automation.Prerequisite: merge/reconcile
kustomize-clustergateway refactor first. It establishes clean aggregate member names and adds Cloudflare, Playwright, and Twilio documentation before this chart switches tovmcp-gateway.Owner-accepted cutover: the live 0.1.74 chart targets generated direct Services that the gateway refactor removes, so affected MCP integrations are temporarily unavailable between the GitOps reconciliation and this chart rollout. After a separately confirmed merge, the main workflow publishes 0.1.75 and opens/updates the GitOps pin PR; that PR, Argo reconciliation, pod health, aggregate tool discovery, and representative agent calls remain separate gates.
Rollback is paired with the gateway refactor: reselect/publish a chart compatible with restored direct Service names and revert the gateway change together; do not roll back either side in isolation.
Safety and secrets
AI-assisted change; reviewer scrutiny requested for aggregate tool naming and staged GitOps delivery.