Why only accept PAT in local github mcp server

[zhoufenqin]

Thanks for work, I see the doc that when using local github mcp server, it only accepts PAT and configure it into the environment.

I also see the MCP Authentication doc says
"Implementations using an STDIO transport SHOULD NOT follow this specification, and instead retrieve credentials from the environment."

Just want to know why cannot support oauth for local mcp tool. we have an edit agent tool that need to do some comment in github issue, when migrating to local mcp tool, it's hard to process the oauth in the tool, using PAT is not good experience for us

TAHNKS SO MUCH

[SamMorrowDrums]

Is remote server support planned for your edit agent tool? Oauth is a better experience, one option in the short term could be to use the gh cli, which has a method for this use-case gh auth token which you could use to automate the experience?