Integration
MicroStax + GitHub Copilot
Use GitHub Copilot with the MicroStax MCP server for practical environment tasks such as review, diagnosis, and sharing without making Copilot the source of truth for environment lifecycle.
Ask Copilot anything about your environments
Create an environment for the feature/payments-v2 branch
Environment stx-payments-v2-b3a9 ready · 4 services healthy · TTL 48h
What environments are currently running?
3 active: stx-payments-v2-b3a9, stx-auth-rework-a1f2, stx-reference-shared
Share a review link for the payments environment
Share link created: https://stx.ai/share/pay-v2-review (expires 48h, no login required)
Destroy the auth-rework environment
Environment stx-auth-rework-a1f2 destroyed · resources released
Bounded environment tasks
Ask Copilot to inspect, diagnose, review, or share environments through the MCP surface instead of manually hopping between tools.
Works in VS Code + GitHub.com
Use the same MCP-backed task interface in editor and review workflows where Copilot is available.
Useful for branch and PR context
Copilot can help around branch-level environments, but the underlying environment state still lives in MicroStax rather than in Copilot-specific workflow glue.
Control-plane visibility
The useful point is not chat magic. It is that Copilot operates against the same environment model, diagnostics, and sharing flows as the rest of the platform.
Also see