Connect GitHub to AI — your repos in the Brain (beta)
Connecting GitHub to Zylx Studio through a GitHub App installation reads your repositories, pull requests, issues, commits, CI status, deployments, and releases into your workspace's Business Brain. Authorized AI clients — Claude, ChatGPT, or any MCP-compatible assistant — then see engineering context next to business context: what shipped, what's in review, and how it relates to the site and store the rest of the Brain describes.
Write support is in beta and approval-gated: an assistant can propose a branch, commit, or pull request, and merging goes through the same human approval queue as every other Zylx write. This is different from GitHub's own official MCP server, which gives an assistant direct developer access to GitHub — Zylx's angle is business context plus controlled engineering actions.
How the connection is wired
GitHub's official MCP server is a developer tool for direct repo access. Zylx connects GitHub into a broader business context and keeps write actions behind approvals — different jobs, often complementary.
What Zylx reads
Through the GitHub App connection, Zylx reads:
- Repositories and file contents
- Pull requests and reviews
- Issues
- Commits and CI status
- Deployments and releases
How fresh is the data?
GitHub is queried when an assistant asks, and refreshed in the background on the same schedule as other providers.
What enters the Business Brain
GitHub gives the Brain engineering context: what the codebase is, what changed recently, and how engineering activity lines up with the business the rest of the Brain models.
The Business Brain is the persistent, structured context layer that Zylx Studio builds from every connection and keeps current automatically.
What AI assistants can do
Through Zylx's MCP server, an authorized assistant can:
Read & analyze
- Inspect repos, PRs, issues, and CI status
- Relate code changes to site and business behavior
- Search code and read files for context
Propose (never apply)
- Create a branch and commit changes (beta)
- Open a draft pull request (beta)
- Request a merge — which waits in the approval queue
All GitHub writes are BETA and approval-gated: proposals only, a human decides, and actions are verified after execution. There is no autonomous code deployment. Access happens over MCP — an authorized, workspace-scoped connection for Claude, ChatGPT, and other compatible clients. Setup differs by product: connect Claude or connect ChatGPT.
You stay in control
The GitHub App is installed on repos you choose; writes route through Zylx's approval queue, and branch/PR-based changes are revertible by design.
What disconnecting does
Uninstall the GitHub App or disconnect in Zylx and repo context stops flowing; no further actions are possible.
GitHub + AI FAQ
Is this the same as GitHub's official MCP server?
No. GitHub's MCP server gives assistants direct developer access to GitHub itself. Zylx reads GitHub into a business-wide context — alongside your store, analytics, and revenue — and keeps engineering write actions behind human approval. Developers may well use both.
Can AI merge code without me?
No. Branch, commit, and PR creation are beta actions that produce reviewable artifacts; merges wait in the approval queue for a human decision.
Which plan includes it?
GitHub connects on paid plans with MCP access (Pro and above). Write actions additionally follow the beta gating in your workspace settings.
Put your codebase in context
Engineering activity next to business reality — with approvals on every write.
Related: The Business Brain · Zylx Studio · Knowledge Management · Decision Engine