Problem Statement
The GitHub remote MCP connector (Claude Github MCP Connector app, used by claude.ai / Cowork via the GitHub-hosted official MCP server) exposes get_teams and get_team_members tools, but they always return empty/null results.
Root cause: the GitHub App only requests repository-level permissions (Read: actions, metadata; Read/write: code, discussions, issues, pull requests, repository projects). It does not request any Organization permissions, so the user-to-server token cannot read org team membership — even for org owners, and even when the app is installed on the org with "All repositories" access.
Repro: install the connector on a GitHub organisation, authenticate as an org owner in claude.ai, call get_teams → returns null. Repo-scoped tools (issues, PRs, code) all work correctly. The tools' own descriptions say "Limited to organisations accessible with current credentials," but no credential configuration on the user side can grant this — installation permissions are fixed by the app manifest.
Proposed Solution
Add Organization permissions → Members: Read-only to the Claude Github MCP Connector app manifest. Existing installations would then surface GitHub's standard permission-update request, which org owners can review and accept at Organization Settings → GitHub Apps → Configure.
This would make get_teams and get_team_members functional while remaining read-only and opt-in per organisation (owners who decline the update simply keep current behavior). Alternatively, if team queries are intentionally unsupported, remove or clearly mark these tools so clients don't suggest them.
Alternatives Considered
No response
Area
MCP Connector (adding/managing servers)
Priority
Critical - Blocking my MCP server development
Additional Context
No response
Problem Statement
The GitHub remote MCP connector (Claude Github MCP Connector app, used by claude.ai / Cowork via the GitHub-hosted official MCP server) exposes get_teams and get_team_members tools, but they always return empty/null results.
Root cause: the GitHub App only requests repository-level permissions (Read: actions, metadata; Read/write: code, discussions, issues, pull requests, repository projects). It does not request any Organization permissions, so the user-to-server token cannot read org team membership — even for org owners, and even when the app is installed on the org with "All repositories" access.
Repro: install the connector on a GitHub organisation, authenticate as an org owner in claude.ai, call get_teams → returns null. Repo-scoped tools (issues, PRs, code) all work correctly. The tools' own descriptions say "Limited to organisations accessible with current credentials," but no credential configuration on the user side can grant this — installation permissions are fixed by the app manifest.
Proposed Solution
Add Organization permissions → Members: Read-only to the Claude Github MCP Connector app manifest. Existing installations would then surface GitHub's standard permission-update request, which org owners can review and accept at Organization Settings → GitHub Apps → Configure.
This would make get_teams and get_team_members functional while remaining read-only and opt-in per organisation (owners who decline the update simply keep current behavior). Alternatively, if team queries are intentionally unsupported, remove or clearly mark these tools so clients don't suggest them.
Alternatives Considered
No response
Area
MCP Connector (adding/managing servers)
Priority
Critical - Blocking my MCP server development
Additional Context
No response