Versionly MCP¶
Hosted MCP server (GitHub App integration) - Versionly watches the third-party APIs used in the GitHub repos an operator connects, maps breaking changes back to the calling files, and opens a pull request for a human to review rather than merging anything itself.
Server type: Hosted (GitHub App plus MCP surface)
Auth: GitHub App installation
Endpoint: versionly.dev (docs at versionly.dev/understand)
Tools: scan, findings and pull-request operations
Pricing: Versionly account required
Category: DevOps
Built by: Versionly (versionly.dev)
Why This Matters for Operators¶
Third-party APIs change underneath running products, and the break is usually discovered when something fails in production. Versionly reads the vendor changelog and OpenAPI alongside the repo, produces findings with a file path and line rather than a generic "something changed" banner, and proposes a patch as a pull request that keeps the team's review rules intact.
Nothing merges itself. Patches land on a deterministic branch, and CODEOWNERS, CI and the merge button stay with the human team, which is what makes it usable in a real product org rather than a demo.
Tools & Capabilities¶
| Capability | Purpose |
|---|---|
| Connect repos | Install the GitHub App and select the repos that call tracked vendors |
| Scan against live vendor docs | Read the repo and the vendor changelog or OpenAPI to find real changes |
| Findings | Report each change with a file path and line |
| Pull requests | Open a reviewable fix PR on a deterministic branch |
Three moves, one human still ships: connect selected repos, scan against live vendor docs, review the pull request.
Installation¶
Install the Versionly GitHub App, tick the projects that call the tracked vendors (Stripe, OpenAI, Twilio or anything else configured), then connect the MCP surface to the agent client. Repos that are not selected never enter the workspace.
Configuration¶
The server runs as a hosted service driven by the GitHub App installation. Point the MCP client at the Versionly MCP endpoint from the workspace settings; the vendor publishes the current endpoint in the app.
Business Relevance¶
- Engineering leads learn about a breaking vendor change before it reaches production.
- Product owners see blast radius described in plain language, not a raw dependency diff.
- Platform teams keep review and CI rules exactly as they are while the fix is proposed.
- Companies running on Stripe, OpenAI or Twilio get an early-warning layer over those integrations.
Integration with CorpusIQ¶
Versionly protects the integrations that feed CorpusIQ. If an agent's Stripe, HubSpot or GA4 connector is called from a repo Versionly watches, a vendor API change is caught and patched before it silently breaks the data flowing into CorpusIQ. Versionly is the early-warning layer on the code side; CorpusIQ is the business-data side, and together a change becomes a reviewable patch rather than a production incident.
Limitations¶
- Brand new, no track record yet.
- Requires a Versionly account and a GitHub App installation.
- Coverage is limited to the vendors and repos configured.
- It proposes patches; it does not merge them, so human review remains in the loop.
- Hosted service, so there is no self-hosted option.
FAQ¶
Does Versionly merge changes automatically?¶
No. It opens a pull request on a deterministic branch and leaves CODEOWNERS, CI and the merge button with the team.
How does it know which APIs to watch?¶
It reads the selected repos and compares them against the vendor changelog and OpenAPI for the vendors configured in the workspace.
Will it touch repos I have not selected?¶
No. Only the projects ticked during installation enter the workspace.