Skip to content

Expose read-only deployment history and deployment statuses #3876

Backlog

Description

@willmot

Describe the feature or problem you’d like to solve

Expose read-only repository deployment history and deployment statuses through the native GitHub MCP server, so an agent can verify which commit reached an environment and whether deployment succeeded.

In a real release-audit workflow, the hosted read-only MCP catalogue could retrieve merged PRs, commits, checks and Actions runs, but could not retrieve GitHub Deployment objects. The same authenticated account could read the deployment records and their successful statuses through REST. The successful deployment's SHA exactly matched the release PR's merge commit. Without those records, the agent could only report what merged and leave actual deployment unverified.

The hosted catalogue was checked on 17 November 2026 with X-MCP-Toolsets: all. It returned 74 read-only tools. I also inspected the public source at 67d4dc489700ec955ad255d098396dd86c729523. I found no deployment-history reader. The deployment and deployment_status event filters on actions_list select workflow triggers; they do not retrieve Deployment objects or statuses created by an external deployment service.

Proposed solution

Add native read operations corresponding to:

  • GET /repos/{owner}/{repo}/deployments, including the existing SHA, ref, environment and task filters.
  • GET /repos/{owner}/{repo}/deployments/{deployment_id}.
  • GET /repos/{owner}/{repo}/deployments/{deployment_id}/statuses.

Please expose the deployment identity, commit SHA/ref, environment, timestamps, creator and native status details, with pagination and the caller's existing GitHub authorization. These should be available in read-only mode. The exact tool names and grouping can follow the project's preferred design.

This would let agents bind release contents to a successful deployment while preserving uncertainty when records are missing, pending or failed.

Example prompts or workflows (for tools/toolsets only)

  1. “Which commit was last successfully deployed to production?”
  2. “Did the release PR reach production, or was it only merged?”
  3. “Compare the commits currently deployed to staging and production.”
  4. “List production deployments in the last 30 days and identify failures or rollbacks.”

Additional context

This is a capability request supported by a verified permission comparison. It requires no new deployment service integration: the records already exist in GitHub's Deployments API.

The private repository, account details and deployment records are omitted. No write operations are requested.

AI disclosure: Codex investigated the capability gap and drafted and opened this feature request under Tom's direction.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions