Wondering if this should be leveragingcli/go-gh like it is or potentially instances of the MCP server being their own OAuth applications i.e. having their own client ID which could be implemented usingthis

@pauldthomson Definitely agree, there should be some tooling provided bygithub-mcp-server to acquire the token so users aren't stuck generating PATs.

There is a broader discussion to be had about how fine-grained authorization could be handled by the server, given many users want to grant varying levels of access to different resources (e.g. read-write access to current repo, but read-only access to other repos). It could go a long way to addressing the perennialclaims of github-mcp-server being "exploited" by poisoned prompts to extract private data.