MCP Coming soon
Organization-wide repository inventory and governed sync
Org Fleet MCP inventories repositories across a GitHub organization and coordinates governed clone and sync operations from the management plane. Hosted deployment is planned.
Category
Organization Operations
Best for
Platform teams responsible for repository hygiene and coordinated work across a GitHub organization.
Access and usage
Hosted deployment is planned. Read-only inventory and governed repository operations will use different operation classes when access opens.
Why it exists
Inventory organization repositories and run governed clone or sync operations from a management-plane service.
Generic terminals, provider APIs, and custom prompts can cover parts of the work, but the caller must supply permission limits, output requirements, failure handling, and usage accounting.
Connection and contract
The intended MCP contract is documented for evaluation, but no public hosted endpoint is available yet.
The product-specific schema defines the inputs and outputs used by clients and downstream automation.
Current limits
The page describes planned product scope. Tool availability, runtime behavior, and performance should not be inferred before the production gate passes.
What you get
- Inspect organization repository state in one inventory
- Keep read-only checks separate from clone and sync operations
- Record structured results for fleet-wide work
Core use case
Inventory organization repositories and run governed clone or sync operations from a management-plane service.
Outcomes
- See repository state across the organization
- Separate read-only checks from mutating fleet operations
- Keep a machine-readable record of each fleet action
Primary workflows
Inventory organization Check drift Approve sync Review results