Repo Fleet MCP

Multi-repository inventory and coordinated operations

Repo Fleet MCP gives organizations a consistent inventory and operating surface across many repositories.

Included with an active usage plan

Available through the hosted catalog. Calls count against the shared allowance on the account plan.

Compare usage plans

Why it exists

Inventory repositories and coordinate bounded operations across the fleet.

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

Connect from an MCP-aware client with an account-scoped Monarchic key. The hosted route checks access, runs the named product contract, and records the operation on the account receipt.

The product-specific schema defines the inputs and outputs used by clients and downstream automation.

Current limits

Clone, sync, and other mutating fleet operations have separate policy and approval requirements.

Requires an authenticated, entitled account. This listing call uses the hosted read-only fleet profile.

What you get

Inventory repositories and their state
Coordinate bounded fleet-wide operations
Return machine-readable results and failures

Core use case

Inventory repositories and coordinate bounded operations across the fleet.

Outcomes

See repository state in one consistent inventory
Coordinate repeatable fleet-wide operations
Receive structured results when an operation fails

Primary workflows

Fleet inventory Repository sync Batch checks Failure reporting

Concrete workflow / priced call

List the repositories in a governed fleet manifest

The request, exact tool-call payload, returned output, and usage receipt are shown below.

Request

“Show the repositories this fleet configuration manages.”

Execution

Tool call payload

{
  "tool": "repo_fleet_list",
  "arguments": {}
}

Reads the configured fleet manifest and returns normalized repository identifiers and paths without syncing or mutating them.

Output

Representative contract excerpt

{
  "contract": "repo-fleet.catalog-list.v1",
  "status": "ok",
  "repositories": [
    {
      "id": "example-service",
      "defaultBranch": "main"
    }
  ],
  "mutationPerformed": false
}

Usage rating

At runtime

Recorded on the operation receipt

The listing receives a measured receipt. Allowance quantities remain unpublished until the fully allocated rate card is frozen.