Repository navigation
Add organization member and repository discovery tools #1911
Description
Activity
I believe repositories within an org can be discovered with search_repositories with an org parameter. Not the best experience though-- agree it would be nice to have a dedicated tool.
Org members, org teams, and team members would be really nice though!
good catch @KevinPartingtonTR — and after looking more closely, i want to correct my own scope here.
already shipped:
get_teams+get_team_membersare in the defaultcontexttoolset (read:orgscope) — these cover the teams/team-members part of this requestsearch_repositorieswithorg:qualifier handles repo discovery, as you noted
the real remaining gap is list_org_members (GET /orgs/{org}/members) — there's no way to enumerate org members today.
this is also tracked in #1331, and @cointem already has an open PR in #1508 (adds get_org_members + list_outside_collaborators) — but it's been waiting on maintainer review since nov 2025.
consolidating demand here: what would it take to get #1508 across the finish line?
Describe the feature or problem you'd like to solve
There's no way to list organization members or enumerate repos within an org. Agents working in enterprise contexts can't answer basic questions like "who's on this team?" or "which repos does this org have?"
I hit this when building an onboarding assistant. My agent could create issues and PRs, but couldn't discover which repos existed in the org or who to assign as reviewers.
Proposed solution
Add organization discovery operations:
list_org_membersGET /orgs/{org}/memberslist_org_reposGET /orgs/{org}/reposOptionally also:
list_org_teams→GET /orgs/{org}/teamslist_team_members→GET /orgs/{org}/teams/{team_slug}/membersExample prompts or workflows
Additional context
Organization-level discovery is essential for enterprise workflows. The user's token permissions already gate access — this just exposes what the API already allows. Happy to submit a PR if this feature is accepted.