Skip to content

[mcp-tools] Update GitHub MCP toolsets mapping: add list_repository_collaborators to repos #34423

Description

@github-actions

Summary

This PR adds the missing list_repository_collaborators tool to the repos toolset in pkg/workflow/data/github_toolsets_permissions.json, and updates the corresponding documentation in .github/aw/github-mcp-server.md.

Discrepancy Detected

While auditing the GitHub MCP remote server tools against the JSON mapping, the daily MCP tools report agent discovered that list_repository_collaborators is available on the actual MCP server but was not present in the toolsets/permissions mapping. As a result, when the compiler routes tool allowlists, this tool would not be properly associated with the repos toolset or its required contents read permission.

Notably, list_repository_collaborators is already referenced in .github/workflows/daily-doc-healer.md at line 98, where the workflow agent inspects repository collaborators to determine whether closures are intentional rejections. This means consumers of the mapping already depend on the tool being correctly classified.

Changes

  • pkg/workflow/data/github_toolsets_permissions.json — adds "list_repository_collaborators" to the repos toolset's tools array (alphabetically positioned between list_releases and list_tags).
  • .github/aw/github-mcp-server.md — adds a row to the repos toolset table documenting the tool's purpose and key parameters (owner, repo, affiliation, page, per_page), and bumps Last Updated to 2026-05-24.

Toolset Choice Rationale

The repos toolset is correct because:

  • The tool operates on a specific repository (owner/repo are required).
  • The MCP server source places collaborator listing alongside other repository metadata operations.
  • It requires the contents read permission, which matches the rest of the repos toolset.

Test plan

  • CI lint/build passes
  • gh aw compile still resolves toolsets correctly
  • Existing workflow daily-doc-healer.md (which already uses this tool) compiles cleanly

🤖 Generated with [Claude Code]((claude.com/redacted)


Warning

Protected Files — Push Permission Denied

This was originally intended as a pull request, but the patch modifies protected files. A human must create the pull request manually.

Protected files

The push was rejected because GitHub Actions does not have workflows permission to push these changes, and is never allowed to make such changes, or other authorization being used does not have this permission.

Create the pull request manually
# Download the patch from the workflow run
gh run download 26361545579 -n agent -D /tmp/agent-26361545579

# Create a new branch
git checkout -b update-github-mcp-tools-mapping-1ad40683d09fd8a0 main

# Apply the patch (--3way handles cross-repo patches)
git am --3way /tmp/agent-26361545579/aw-update-github-mcp-tools-mapping.patch

# Push the branch and create the pull request
git push origin update-github-mcp-tools-mapping-1ad40683d09fd8a0
gh pr create --title '[mcp-tools] Update GitHub MCP toolsets mapping: add list_repository_collaborators to repos' --base main --head update-github-mcp-tools-mapping-1ad40683d09fd8a0 --repo github/gh-aw

Generated by 📊 GitHub MCP Remote Server Tools Report Generator · ● opu47 12.7M ·

  • expires on May 26, 2026, 12:50 PM UTC

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions