Skip to content

feat(mcp): add direct makeitwork-gcp server - #17

Closed
xnoto wants to merge 3 commits into
mainfrom
docs/makeitwork-gcp-aggregate-routing
Closed

xnoto wants to merge 3 commits into
mainfrom
docs/makeitwork-gcp-aggregate-routing

Conversation

@xnoto

@xnoto xnoto commented Sep 9, 2026

Copy link
Copy Markdown
Owner

Repository has no pull-request template.

Summary

  • add a dedicated makeitwork-gcp remote MCP server pointing at https://mcp-makeitwork-gcp.makeitwork.cloud/mcp;
  • pass the existing MCP Gateway Cloudflare Access headers from CF_ACCESS_CLIENT_ID / CF_ACCESS_CLIENT_SECRET;
  • allow only the read-only makeitwork-gcp_run_gcloud_command tool by name;
  • update MCP routing guidance to select makeitwork-gcp for Make IT Work Cloud GCP operations.

Validation

  • Required pull-request checks pass — lint run 34326354359 succeeded on head 7bafb5c.
  • Reviewed the JSON diff for schema compatibility with the existing remote-server entries; no pre-commit pins changed.

Merge gate and impact

Do not merge until makeitworkcloud/tfroot-cloudflare#44 has merged, its environment-gated apply has created the Access application, and the held kustomize-cluster TunnelBinding route for mcp-makeitwork-gcp.makeitwork.cloud is live. Reload OpenCode after merge. No credentials are committed; rollback is a normal revert plus client reload.

@xnoto xnoto changed the title docs: route GCP through aggregate MCP feat(mcp): add direct makeitwork-gcp server Sep 9, 2026
@xnoto xnoto closed this Sep 11, 2026
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