Configuration for organization repository indexing

[andrewdwooten]

Hey there! We're working on extending our agent a bit via configuration/mcp, and I'm wondering if there's a way to configure the agent to also have context on other repos in the organization. We've had good results improving our AI dev workflow with such extension and are hoping to apply it to our agent configs.

I've updated the github MCP for the agent with a token with Content read permissions for the org, but this only results in being able to read metadata via the api and our hope is to add configuration such that other repos can be indexed for reference. Copilot chat made referene to a MCP_INDEXED_REPOSITORIES env var which we set in the copilot environment to no apparent effect. Is this something that's possible or that is roadmapped yet? Much obliged for the help!

[nhu-do]

Hi @andrewdwooten! The route you've taken with creating a more permissive token for the GitHub MCP server is what I'd also recommend here. If the token is configured properly, it should enable you to read other repositories within the organization.

As far as MCP_INDEXED_REPOSITORIES goes, we don't have immediate plans to support this yet on our roadmap.

We are working on a feature that would enable the agent to work across repositories, which may help your scenario in the future as well.

[andrewdwooten]

@nhu-do Too cool! Appreciate the confirmation there. Is there a common method to confirm the token has been configured/attached correctly? I used a fine-grained token with Contents read access, but prompting to inquire about accessibility results in a message about private repositories. Much obliged for your assistance!

I'm getting 404 errors when trying to access both repositories. This indicates they're either private repositories (which I can't access), don't exist yet, or have different names.